Investigate showing partial results for failed GraphQL queries #2

When a query fails in a template, it can be difficult to figure out exactly why it failed; a single error will hide the entire result that we'd have gotten for the query otherwise, showing only an error message and a stacktrace.

We should figure out whether there's a way to show the part of the query result that succeeded, so that it's easier to debug the source of an issue - eg. by looking at the other data for an item to see if there's anything obviously strange (unexpected null, mis-parsed data, ...), that might mess up code elsewhere that relies on it.

When a query fails in a template, it can be difficult to figure out exactly why it failed; a single error will hide the entire result that we'd have gotten for the query otherwise, showing only an error message and a stacktrace. We should figure out whether there's a way to show the part of the query result that succeeded, so that it's easier to debug the source of an issue - eg. by looking at the other data for an item to see if there's anything obviously strange (unexpected `null`, mis-parsed data, ...), that might mess up code elsewhere that relies on it.

Labels Milestones

Investigate showing partial results for failed GraphQL queries #2