At a glance
- Identifier: #803
- Stage: RFC 3 / Accepted
- Champion: @benjie
- Latest activity: Spec PR merged on 2021-04-07
- Spec PR: https://github.com/graphql/graphql-spec/pull/803
- Related:
Spec PR description
This is a specific change from #777 applied throughout the spec.
The term "query error" feels limited to GraphQL query operations; however the error could be raised from mutations or subscriptions too, in fact it can also be raised when it's not clear what operation is to be executed (e.g. when there's a document with multiple operations, but no operationName was provided). As such, the error does not relate specifically to "query", or even "operation", but to the entire GraphQL request.
Relates to https://github.com/graphql/graphql-wg/issues/546
Timeline
April 2021
- Spec PR merged on 2021-04-07 by leebyron
- 2 commits pushed on 2021-04-07
- @leebyron committed "Also use consistent error verbs"
- @leebyron committed "Add sub-sections for 'request errors' and 'field errors' and update l…"
March 2021
- Advanced to RFC 3 on 2021-03-04 by leebyron
- Added to WG agenda on 2021-03-04
- Mentioned in WG notes on 2021-03-04
February 2021
- @benjie committed "Add details about request errors" on 2021-02-08
January 2021
- Advanced to RFC 1 on 2021-01-07 by leebyron
- Added to WG agenda on 2021-01-07
- Mentioned in WG notes on 2021-01-07
- Top comment edited on 2021-01-05 by benjie
November 2020
- Spec PR created on 2020-11-28 by benjie
- Top comment edited on 2020-11-28 by benjie
- @benjie committed "Replace 'query error' with 'request error'" on 2020-11-28