feat: stringify bigint, addresses issue #648 #672
Closed
Conversation
This file contains 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
jonball4
force-pushed
the
ft/stringify-bigint
branch
from
3ae27da
to
7642f45
Compare
jonball4
force-pushed
the
ft/stringify-bigint
branch
from
7642f45
to
ec8c7ba
Compare
jonball4
force-pushed
the
ft/stringify-bigint
branch
from
ec8c7ba
to
841f81b
Compare
jonball4
force-pushed
the
ft/stringify-bigint
branch
from
841f81b
to
5ee57b4
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Addresses #648 by adding a JSON.stringify replacer for bigint.