Improve GraphQL errors for Explain code
The following discussion from !118320 (merged) should be addressed:
-
@jerasmus started a discussion: (+4 comments) Note: we're using the generic error message here but down the line, we could implement more useful errors to help guide the user. Right now the structure of the error messages received from the backend is not easy to parse on the frontend:
Example response:
Right now we're displaying a generic error message when we receive a GraphQL error for explain code. This issue suggests displaying the error from the backend. Currently, the error from the backend is neither valid JSON or human readable so we need to make some changes on the backend before we can display it on the frontend.