Replace 'query error' with 'request error'

At a glance

• Identifier: #803
• Stage: RFC3: Accepted
• Champion: @benjie
• PR: Replace 'query error' with 'request error'

Timeline

• 2 commits pushed on 2021-04-07:
  • Also use consistent error verbs by @leebyron
  • Add sub-sections for 'request errors' and 'field errors' and update l… by @leebyron
• Added to 2021-03-04 WG agenda
• Mentioned in 2021-03-04 WG notes
• Commit pushed: Add details about request errors on 2021-02-08 by @benjie
• Added to 2021-01-07 WG agenda
• Mentioned in 2021-01-07 WG notes
• Spec PR created on 2020-11-28 by benjie
• Commit pushed: Replace 'query error' with 'request error' on 2020-11-28 by @benjie

---

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