GraphQL - extremely popular but notoriously time consuming to debug:
Every GraphQL request returns the same 200 “OK”, so developers have to look through every single request to find if one has errors.
Every GraphQL request reuses the same endpoint (“/graphql”), which makes it tedious to find the request you’re looking for when debugging.
But not anymore! As GraphQL users ourselves, we spent some time thinking about what would make debugging GraphQL a lot faster…
Next time you check out a Jam, you’ll see two features to make debugging faster for apps built with GraphQL:
⚡️ Automatic Error Detection
Jam auto-detects GraphQL and flags when GraphQL responses contain errors, even though they technically return a 200 success.
(Whereas in Chrome dev tools, they are all shown as status: 200 OK, and you need to click into every request to see if it has errors)
⚡️ Mutation Name Visibility
Jam now auto-detects and shows the GraphQL mutation name in Jam dev tools, so it’s easier to skim and find the important request for debugging.
(Whereas in Chrome dev tools, you need to click into each request to see which mutation it’s for)
Happy faster GraphQL debugging! 🚀
As users of GraphQL ourselves, we’re so excited about this one and we’ve seen our own debugging speed up.
We hope you never have to use it because you’ll never have bugs, but if a bug or two does appear, we hope this saves you tons of time!