For me GraphQL adds a lot of complexity when setting up the API for only an incremental benefit when querying. Do others feel the same? Or am I missing something?
Errors from parsing the JSON should show up somewhere visible, as of now it looks like nothing happens unless you check the console.
Looks like a low friction way to bring on new team members to GraphQL.
However, the tools is either broken or not finished yet. I tried to change posts to books in the JSON tab and I get an error below: "Cannot extend type "Post" because it does not exist in the existing schema."
CSS is broken in Firefox.
i thought Graphql was confusing at first, merely because of their distinction of "Query" and "Mutation". It turns out (which I should've known), "Query" is just like GET requests where you are retrieving information and "Mutation" is like a POST/PUT/PATCH/DELETE requests that can modify the data.
After grasping this, Graphql was pretty similar to working with REST and a bit more flexible in how we want the data to be returned.
Graphql really does fix the whole "query multiple endpoints to construct a single data" dilemma.
Only thing I didn't like about it was the way Graphql schema is to be written in server side, thought it could be a bit more intuitive and simplified . Currently, it can get pretty verbose and breaks the DRY mantra. Would be nice if the Type system can be hooked up with the whatever ORM you are on (Mongoose, AR, Sequel) because you'll be re-mapping the fields to Graphql which can be an overhead for no reason.
Also schema is like working with SOAP's WSDL all over again. I used to hate it but it's back with Graphql so I'm trying hard to like it!