We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Following on from discussions in the GraphQL Composite Schemas Working Group: https://github.com/graphql/composite-schemas-wg it would be good to align terminology.
Current working glossary: graphql/composite-schemas-wg#34
Terms agreed in the inaugural meeting in 14th July 2022:
Subschema
TODO:
Potential places to look in/look out for:
WIP
For anyone interested in helping contribute, feel free to identify and explore :)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Following on from discussions in the GraphQL Composite Schemas Working Group: https://github.com/graphql/composite-schemas-wg it would be good to align terminology.
Current working glossary: graphql/composite-schemas-wg#34
Terms agreed in the inaugural meeting in 14th July 2022:
Subschema
- essentially the schema of a federated service (definition TBD)Exploration
TODO:
Potential places to look in/look out for:
WIP
Proposed Solution
WIP
For anyone interested in helping contribute, feel free to identify and explore :)
The text was updated successfully, but these errors were encountered: