Skip to content
This repository has been archived by the owner on Mar 20, 2023. It is now read-only.

Revert "Allow custom handling of runtime query errors" #736

Merged
merged 1 commit into from Jan 17, 2021

Conversation

acao
Copy link
Member

@acao acao commented Jan 17, 2021

Reverts #696

we have to be following the transport spec error codes:

https://github.com/graphql/graphql-over-http/blob/master/spec/GraphQLOverHTTP.md#status-codes

@acao acao merged commit 20e3466 into master Jan 17, 2021
@acao acao deleted the revert-696-runtime-query-error-handling branch January 17, 2021 14:20
@MatthiasKunnen
Copy link
Contributor

How does #696 violate the linked spec?

@joshribakoff-sm
Copy link

joshribakoff-sm commented Jul 22, 2022

I believe the authors of the library are misreading the spec:

If the GraphQL response contains the {data} entry and it is {null}, then the server SHOULD reply with a 2xx status code and it is RECOMMENDED it replies with 200 status code.

My response contains a null data entry as described, and yet it still corrupts the status code.

Can we revert this? It's pretty annoying to see the community rally behind something with consensus, only for it to be reverted based seemingly on principle, and without addressing the practical concerns of the community.

@mihairadulescu
Copy link

Apollo-Client cannot be used with the 500 status code !!!!!!!!!! FIX THIS ASAP!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants