Fix: handle lossy max int64 #40
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
|
|
Signed-off-by: Thomas Lacroix <[email protected]>
lacroixthomas
force-pushed
the
bugfixes/fix-lossy-in64
branch
from
1471c89 to
4c723fc
Compare
This was referenced Jan 20, 2025
|
(Sorry to ping, just copying from previous PRs) |
tamalsaha
approved these changes
Mar 9, 2025
|
Thanks for the contribution. Tagged v2.5.0 |
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.
#39
Use the json Decoder with the
json.Numbertype to handle max int64 values as int64 instead of float64 with scientific format.