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

fix(transports): Switch to @bugsnag/safe-json-stringify for serialization #338

Merged
merged 2 commits into from
Apr 18, 2018

Conversation

bengourley
Copy link
Contributor

fast-safe-stringify did not fully protect us against circular data structures or objects of arbitrarily large depth. This commit implements our own forked version of a serialization library with some extra features required by us.

Fixes #337.

…tion

fast-safe-stringify did not fully protect us against circular data structures or objects of
arbitrarily large depth. This commit implements our own forked version of a serialization library
with some extra features required by us.

Fixes #337
kattrali
kattrali previously approved these changes Apr 16, 2018
Copy link
Contributor

@kattrali kattrali left a comment

Choose a reason for hiding this comment

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

Approved pending changes to safe-json-stringify to simplify truncation messages.

@bengourley
Copy link
Contributor Author

The travis fail is a flake. It is a different browser and a different test that fails each time I trigger a new build. The tests pass when I run them on BrowserStack from my local machine.

@bengourley bengourley merged commit 00a24f1 into master Apr 18, 2018
@bengourley bengourley deleted the improved-json-serialization branch April 18, 2018 14:25
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

2 participants