-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Allow union type begining pipe #323
Allow union type begining pipe #323
Conversation
This adds the type definition syntax to the GraphQL specification.
@robzhu @IvanGoncharov I update the PR here. |
Can you please post a screenshot of the rendered spec document? |
Also, please don't forget to update the language grammar appendix |
Thanks! As I expected it's not rendering correctly. Notice other optional tokens have an opt subtext after them. This appears to require the literal character |
Do you think this form is weird or challenging to read? (open to advice)
Otherwise a change to spec-md will be required to allow for optional terminals |
@leebyron I'm already working on a PR on |
4bacab6
to
4d63721
Compare
I've merged this into the RFC in #90 🥇 |
* [RFC] GraphQL IDL additions This adds the type definition syntax to the GraphQL specification. * Add directives to all schema definition forms * expose more in example directive * Include more directive locations * Include deprecated directive * Note on omission of schema definition * Explicit ObjectTypeExtension grammar to support extending without adding fields * Ensure directives cannot reference variables in SDL * grammar * Remove duplicate EnumValue * First class descriptions * Minor wording change about markdown and TSL -> SDL * Add validation rule that executable documents cannot include SDL * Move extend keyword * Order of sections * Move language definitions into Type System section * Fix type reference header and comments * Add more examples of descriptions * Grammar * Include optional leading bar for unions & directive locations. Merging and closing #323 * Allow partial definitions (as @OlegIlyenko suggests) while legitimizing the use case by allowing type extensions for all type kinds, allowing at least the addition of new directives to any existing type. * Consistent plural usage in grammar nt rules * Remove ambiguous "may not" and explicitly state objects may implement interfaces via extensions * Extract ExecutableDefinition into a separate gramatical rule * Address review from @vergenzt * Use `&` to separate implemented interfaces, simplify grammar definitions * Fix reference in grammar summary * Fix reference to UnionMemberTypes
Moved the PR onto this branch
#320