Allow for bigint values in JSON.stringify #550
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This change is as the result of a CI failure where `bigint` values are in-use - https://github.com/LedgerHQ/ledger-live-desktop/runs/4325584600?check_suite_focus=true#step:13:92
Allow for bigint values in JSON.stringify
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is as the result of a CI failure where bigint values are in-use -
https://github.com/LedgerHQ/ledger-live-desktop/runs/4325584600?check_suite_focus=true#step:13:92
Some background reading here - https://dev.to/benlesh/bigint-and-json-stringify-json-parse-2m8p
In this approach instead of adding a replacer, the typeof is just checked and then toString() is used on the value if found to be a bigint.