Be strict about error paths format

At a glance

• Identifier: #1073
• Stage: RFC3: Accepted
• Champion: @martinbonnin
• PR: Be strict about error paths format
• Related:
  • #1065 (SemanticNonNull type (null only on error))
  • wg#1410 (Strict Semantic Nullability)

Timeline

• Added to 2024-04-04 WG agenda
• Mentioned in 2024-04 WG notes
• Added to 2024-03-07 WG agenda
• Mentioned in 2024-03 WG notes
• 2 commits pushed on 2024-02-01:
  • Update spec/Section 7 -- Response.md by @martinbonnin
  • format by @martinbonnin
• Added to 2024-02-01 WG agenda
• Mentioned in 2024-02 WG notes
• Spec PR created on 2024-01-25 by martinbonnin
• Commit pushed: Be strict about error paths on 2024-01-25 by @martinbonnin

---

Replace should with must in the description of error paths: This field must be a list of path segments starting...

    {
      "message": "Name for character with ID 1002 could not be fetched.",
      "locations": [{ "line": 6, "column": 7 }],
      "path": ["hero", "heroFriends", 1, "name"]
    }

Anything else will make it impossible to handle errors in error-aware clients. This is especially important for strict-nullability or semantic-non-nullability