REST and GraphQL really aren't that different

Re:REST and GraphQL really aren't that different by SideburnsOfDoom on Thursday January 31, 2019 @06:40AM (#19044083)

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 )

[ Parent | on HN ]

Re:REST and GraphQL really aren't that different by Garvey on Thursday January 31, 2019 @10:19AM (#19045302)

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.

[ Parent | on HN ]

Re:REST and GraphQL really aren't that different by bdcravens on Thursday January 31, 2019 @11:40AM (#19046080)

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

[ Parent | on HN ]

Re:REST and GraphQL really aren't that different by SideburnsOfDoom on Friday February 01, 2019 @08:10AM (#19053763)

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

[ Parent | on HN ]

Re:REST and GraphQL really aren't that different by bdcravens on Friday February 01, 2019 @01:23PM (#19056849)

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.

[ Parent | on HN ]