Fix: Replace jsonBigint with lossless-json #2006
Merged
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
DJSaunders1997
changed the title
|
Merged! Thank you @DJSaunders1997 ! This will go out in the |
|
Great, thanks @helloanoop :) |
slowjoe007
pushed a commit
to slowjoe007/bruno
that referenced
this pull request
Apr 10, 2024
Its-treason
pushed a commit
to Its-treason/bruno
that referenced
this pull request
Apr 13, 2024
lizziemac
pushed a commit
to lizziemac/bruno
that referenced
this pull request
May 4, 2024
2 tasks
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.
#1933 Description
Changes to address issue #1996
Replace usage of jsonBigint with lossless-json for the Prettify json functionality.
Behaviour after Prettify is as expected, with all data preserved:
Contribution Checklist:
Note: Keeping the PR small and focused helps make it easier to review and merge. If you have multiple changes you want to make, please consider submitting them as separate pull requests.
Publishing to New Package Managers
Please see here for more information.