-
Notifications
You must be signed in to change notification settings - Fork 2
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
Simplify the spec to only include the ! nullability designator #13
base: clientControlledNullability
Are you sure you want to change the base?
Simplify the spec to only include the ! nullability designator #13
Conversation
spec/Section 2 -- Language.md
Outdated
in a query validation error. | ||
can either use the designator `!` to designate the nullability of the entire | ||
field, or they can use the list element nullability syntax displayed above. The | ||
number of dimensions indicated by list element nullability syntax cannot exceed the number of dimensions of the field. Anything else results in a query |
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.
You may want to have an example where the dimensions of the designator are less than the dimensions of the field type.
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.
I added some examples after this paragraph.
spec/Section 6 -- Execution.md
Outdated
nullability designator (`!`) can override it for the duration of an execution. | ||
In order to determine a field's true nullability, both are taken into account | ||
and a final type is produced. A field marked with a `!` is called a "required | ||
field". | ||
|
||
ApplyRequiredStatus(type, requiredStatus): |
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.
I think I got rid of ApplyRequiredStatus
from the execution PR. I think the new function that matters here is called simpleTypeTransfer
or something like that.
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.
I removed ApplyRequiredStatus
, defined simpleTypeTransfer
, and added references to simpleTypeTransfer
. Can you review the list
case of ComputeValue
?
I've made two changes in this PR:
?
nullability designator!
.