Closed
Description
- RFC; previously discussed
in September- Aim: merge this (mostly) editorial change
- Lee: this is a change in behavior but it does seem to align with the intent.
- Lee: lets check this with the implementations to make sure there's no issues
there. It may be that when printing the schema out there is an issue where the
old behavior was followed.- Benjie: I think the code block in the top comment can be used as a test case -
read the code in, generate the schema from it, and print it out - it should be
the same (i.e. nomutation
operation)- ACTION - Benjie - tag implementors and check that this won't cause issues.
Relates to graphql/graphql-spec#987
Retroactive; implementors were pinged in graphql/graphql-spec#987 (comment)
- assignee(s): @benjie
- source: https://github.com/graphql/graphql-wg/blob/main/notes/2023/2023-02.md#fix-ambiguity-around-when-schema-definition-may-be-omitted-10m-benjie
Note: Action Item issues are reviewed and closed during Working Group
meetings.