-
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 REQUIRED_ARGUMENT_MISSING_IN_SOME_SCHEMA
#101
base: main
Are you sure you want to change the base?
Adds REQUIRED_ARGUMENT_MISSING_IN_SOME_SCHEMA
#101
Conversation
Co-authored-by: Glen <[email protected]>
Co-authored-by: Glen <[email protected]>
Co-authored-by: Glen <[email protected]>
|
||
**Error Code:** | ||
|
||
`REQUIRED_ARGUMENT_MISSING_IN_SOME_SCHEMA` |
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.
Could we try to keep the error codes <~35 characters?
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.
Maybe REQUIRED_FIELD_ARGUMENT_MISSING
?
|
||
**Error Code:** | ||
|
||
`REQUIRED_ARGUMENT_MISSING_IN_SOME_SCHEMA` |
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.
Maybe REQUIRED_FIELD_ARGUMENT_MISSING
?
|
||
**Formal Specification:** | ||
|
||
- Let {typeNames} be the set of all object and interface types names from all |
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.
- Let {typeNames} be the set of all object and interface types names from all | |
- Let {typeNames} be the set of all object and interface type names from all |
|
||
When merging a field definition across multiple schemas, any argument that is | ||
non-null (i.e., “required”) in one schema must appear in all schemas that define | ||
that field . In other words, arguments are effectively merged by intersection: |
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.
that field . In other words, arguments are effectively merged by intersection: | |
that field. In other words, arguments are effectively merged by intersection: |
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.
Do you not mean by union?
if an argument is considered required in any schema, then that same argument | ||
must exist in every schema that contributes to the composite definition. If a | ||
required argument is missing in one schema, there is no consistent way to define | ||
that field or directive across schemas. |
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.
The spec doesn't mention directive arguments?
No description provided.