That joy feeling when you are finally rewriting the backend and frontend with GraphQL instead using the fuckin old undocumented REST API who was written by fuckin amateur ex-coworker.

@groxx if it doesn’t use the proper methods it’s not rest. If all your routes are post routes you didn’t build a restful api, you built a waste of space. I’ve seen comments here of people doing that, they suck the big one

Looked up GraphQL.
Seems like horrible thing.
I want all my API be auto generated for client. No need to write “queries”.
I want auto complete and strong typing.

I do not see the point of using grpahQL.

Right now you have a building with weak basis, and you wanna repair it with some extra paint

@groxx I’ve never seen a batch done that way thankfully, hopefully never will

Is graphql good?

Until a bug pop up

GraphQL makes stuff easy for very specific use cases; Extremely generic UI, with large, and highly connected data sets, and lots of cyclic refs are a great use case for graphQL. It removes the complexity of managing the various connections without bloating your API implementation.
ReST API, if done right, are actually the best solution for small, to medium sized data sets, and offer extremely satisfying codebases, as well as flexibility.

@groxx you need to research your basics; You're confusing bad ReST designs with the strict ReST definition. Representational State Transfer is a predefined set of stateless operations that your service offers. It tells the consumer *exactly* what can be done, and how to do it.
If you're trying to build a general API that can manipulate everything in an arbitrary, and flexible way, graphQL is the way to go.