-
Notifications
You must be signed in to change notification settings - Fork 0
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
[WIP] Nonnull operator #5
Conversation
…graphql#3088) using this `find src -name "*.js" -exec sh -c 'git mv "$0" "${0%.js}.ts"' {} \;` shell command renamed all files in `src`
Find this pattern `(\$)FlowFixMe\[(.*?)\]` and replace all
Co-Authored-By: Kamil Kisiela <[email protected]>
Using this patttern`(\$)FlowExpectedError\[(.*?)\]`
// This is invalid since an object could potentially be both the Object | ||
// type IntBox and the interface type NonNullStringBox1. While that | ||
// condition does not exist in the current schema, the schema could | ||
// expand in the future to allow this. Thus it is invalid. |
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 this comment needs to be updated to describe the test. It looks like this test is expected to succeed, but the comment indicates that it should fail
// This is invalid since an object could potentially be both the Object | ||
// type IntBox and the interface type NonNullStringBox1. While that | ||
// condition does not exist in the current schema, the schema could | ||
// expand in the future to allow this. Thus it is invalid. |
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.
Same thing here
message: 'Cannot return null for non-nullable field Food.name.', | ||
path: ['food', 'theNameOfTheFood'], |
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.
In this case, we'd want the message to use the alias instead of the field name right?
Added a bunch of cases to |
No description provided.