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

Try to stringify message errors so socket errors keep their data. #386

Merged
merged 1 commit into from Jul 3, 2017

Conversation

SejH
Copy link
Contributor

@SejH SejH commented Jun 8, 2017

Socket errors are returned to the client as the string "[object Event]".

@Kashee-R Kashee-R added the ready label Jun 8, 2017
@jdmnd
Copy link
Contributor

jdmnd commented Jun 14, 2017

Hey @SejH
Thanks for the contribution!

  1. Would you be able to add a unit test that demonstrates the issue?
  2. The try/catch block here is not required, since JSON.stringify never throws exceptions.

edit: circular references will of course throw an exception

@yasserf
Copy link
Contributor

yasserf commented Jun 17, 2017

Would you be okay signing our CLA? I know its a pretty small change but its easier for us to get all PRs in. Thank you!

https://deepstream.typeform.com/to/PwwNd5

@yasserf
Copy link
Contributor

yasserf commented Jul 1, 2017

Small reminder, be awesome if you could sign the CLA, we can't merge anything in without it =(

https://deepstream.typeform.com/to/PwwNd5

@jdmnd
Copy link
Contributor

jdmnd commented Jul 3, 2017

CLA signature received, thanks!

@jdmnd jdmnd merged commit 0623cec into deepstreamIO:master Jul 3, 2017
SejH added a commit to SejH/deepstream.io-client-js that referenced this pull request Jul 27, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants