Skip to content
Discussion options

You must be logged in to vote

Hey folks 👋, this was a bug on our side. We've just created a PR that addresses that issue here #1193. We'd love feedback on the rendering of these errors. Whether you feel like you can easily parse them visually etc

I'll mark the question as answered for now, the TLDR is that you'll be able to see the graphql api errors as soon as we merge the PR and it gets released 🙌

Replies: 2 comments 1 reply

Comment options

You must be logged in to vote
0 replies
Comment options

You must be logged in to vote
1 reply
@robertcoopercode
Comment options

Answer selected by Weakky
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
3 participants