3 ms·
That’s how GraphQL is doing when used over HTTP and it feels a bit wrong in the beginning but I also think it is better. And you don’t have to fit your errors i
by speedgoose 4y ago
That’s how GraphQL is doing when used over HTTP and it feels a bit wrong in the beginning but I also think it is better. And you don’t have to fit your errors into HTTP semantics.
- ElectricalUnion 4y agoGraphQL does that [everything status 200] because it is designed to work with Browser agents on-purpose self-inflicted technical limitations. Browsers don't return (in XHR/fetch requests) any response in the 400-599 status range.
- speedgoose 4y agoI think you are not correct on this.
- eadmund 4y ago> That’s how GraphQL is doing when used over HTTP and it feels a bit wrong in the beginning GraphQL is maldesigned; it is an abuse of HTTP and should not be emulated.
- speedgoose 4y agoWhy do you think so?