Hacker News Reader

I'm not going to say that GraphQL is bad today, but

If it returns error messages with a 200 OK status, then it's not restful at all ( https://github.com/graphql/graphiql/issues/88 )

View on HN

Isn't that specific to graphiql rather than GraphQL itself? From reading the issue it seems graphiql is expecting it in that format, and the actual status code to return is down to the developer.

Isn't that easy to do with REST as well however?

An error with a 200 OK status code is pretty clearly not what you _should_ do in REST.

No doubt, that's bad design. However, if you try-catch the code and return a custom error message, many frameworks would return a 200 by default if you don't explicitly set the status code.

Reply on news.ycombinator.com