-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds Input Field Types mergeable validation rule #45
base: main
Are you sure you want to change the base?
Conversation
spec/Section 4 -- Composition.md
Outdated
} | ||
``` | ||
|
||
Fields are also consodered mergable if they have different nullability defined |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Fields are also consodered mergable if they have different nullability defined | |
Fields are also considered mergeable if they have different nullability defined. |
spec/Section 4 -- Composition.md
Outdated
``` | ||
|
||
Fields are also consodered mergable if they have different nullability defined | ||
across Here, the field `tags` in `Input1` is a list type with compatible inner |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
across Here, the field `tags` in `Input1` is a list type with compatible inner | |
Here, the field `tags` in `Input1` is a list type with compatible inner |
spec/Section 4 -- Composition.md
Outdated
``` | ||
|
||
In this counter-example, the field `field` in `Input1` has incompatible types | ||
(`String` and `DateTime`), making them not mergeable: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(`String` and `DateTime`), making them not mergeable: | |
(`String` and `DateTime`), making them non-mergeable: |
Co-authored-by: Glen <[email protected]>
Co-authored-by: Glen <[email protected]>
Co-authored-by: Glen <[email protected]>
We need to explain how the nullability merges ... |
- Given each pair of members {fieldA} and {fieldB} in {fields}: | ||
- Let {typeA} be the type of {fieldA}. | ||
- Let {typeB} be the type of {fieldB}. | ||
- {SameTypeShape(typeA, typeB)} must be true. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this is wrong
Co-authored-by: Glen <[email protected]>
No description provided.