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
@calvincestari correct, depends what your behaviour is right now but typically you should throw an error if HTTP code != 200. With the advent of graphql-response+json, these responses can be parsed and exposed to the user instead of throwing.
This introduces a new media type that would be used for GraphQL responses, see the draft GraphQL over HTTP spec.
It looks like the work should generally be simply:
accept
header to include the new media type signalling to the server that the client can accept responses of that type.application/graphql-response+json
to anycontent-type
validation we do before parsing a server response.The text was updated successfully, but these errors were encountered: