Skip to main content

Be strict about error paths format

At a glance​

Timeline​


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