You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If you get a GraphQL error in the response, the data might have some missing fields. The missing fields are represented by null. However, null is also a valid response for any part of a GraphQL query when there is a nullable reference. So it's not possible to reliably determine which parts of the response are missing because of the server error, and which parts actually are not there, and would be null even if there were no error.
This seems like an oversight in GraphQL-JS, and perhaps the GraphQL error spec itself. @helfer have you encountered this? Any ways of getting around it?
The text was updated successfully, but these errors were encountered:
Per conversation with @martijnwalraven:
If you get a GraphQL error in the response, the data might have some missing fields. The missing fields are represented by
null
. However,null
is also a valid response for any part of a GraphQL query when there is a nullable reference. So it's not possible to reliably determine which parts of the response are missing because of the server error, and which parts actually are not there, and would benull
even if there were no error.This seems like an oversight in GraphQL-JS, and perhaps the GraphQL error spec itself. @helfer have you encountered this? Any ways of getting around it?
The text was updated successfully, but these errors were encountered: