At a glance
- Identifier: #598
- Stage: RFC 3 / Accepted
- Champion: @leebyron
- Latest activity: Spec PR merged on 2021-04-08
- Spec PR: https://github.com/graphql/graphql-spec/pull/598
Spec PR description
Partial fix to #564, adds lookahead constraints to type system extensions to remove ambiguity or inefficiency from the grammar.
The GraphQL grammar should be parsed in linear type with at most one lookahead. Since extensions have an optional { } body, finding the token { should always attempt to parse the relevant portion of the type extension rather than completing the type extension and attempting to parse the query shorthand SelectionSet.
Timeline
April 2021
- Spec PR merged on 2021-04-08 by leebyron
- Advanced to RFC 3 on 2021-04-08 by leebyron
August 2019
- Added to WG agenda on 2019-08-01
July 2019
- Spec PR created on 2019-07-23 by leebyron
- @leebyron committed "Avoid parse ambiguity on type extensions" on 2019-07-23