Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Stringify subscription errors elegantly to avoid [object Object] errors #722

Closed
wants to merge 3 commits into from
Closed

Stringify subscription errors elegantly to avoid [object Object] errors #722

wants to merge 3 commits into from

Conversation

wawhal
Copy link

@wawhal wawhal commented Oct 3, 2018

No description provided.

@facebook-github-bot
Copy link

Thank you for your pull request and welcome to our community. We require contributors to sign our Contributor License Agreement, and we don't seem to have you on file. In order for us to review and merge your code, please sign up at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need the corporate CLA signed.

If you have received this in error or have any questions, please contact us at cla@fb.com. Thanks!

@facebook-github-bot
Copy link

Thank you for signing our Contributor License Agreement. We can now accept your code for this (and any) Facebook open source project. Thanks!

@acao acao self-assigned this May 14, 2019
Copy link
Contributor

@Neitsch Neitsch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Other than that LGTM

@@ -574,7 +574,7 @@ export class GraphiQL extends React.Component {
error: error => {
this.setState({
isWaitingForResponse: false,
response: error && String(error.stack || error),
response: this.makeSubscriptionErrorResponse(error),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind keeping the original null check for error?

@acao
Copy link
Member

acao commented Jul 27, 2019

there are several issues regarding this, would be good to get this one released very soon

@benjie
Copy link
Member

benjie commented Aug 12, 2019

Ugh, I just accidentally added to this pile of error solutions:

#934

@benjie
Copy link
Member

benjie commented Aug 12, 2019

The idea of accessing originalError is an interesting one; but I'm going to leave it out of the default implementation in #934 - you can always override GraphiQL.formatError

@acao acao closed this in #934 Aug 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants