fix(core/cbor): handle exponent notation when serializing NumericValue containers - #2243
Merged
Conversation
kuhe
force-pushed
the
kuhe/fix/cbor
branch
2 times, most recently
from
August 19, 2026 14:45
22c3932 to
124c362
Compare
siddsriv
approved these changes
Aug 19, 2026
smilkuri
reviewed
Aug 19, 2026
smilkuri
approved these changes
Aug 19, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
fixes CBOR serialization to handle when the NumericValue string container has a value like
1.23E100(exponential).It also fixes precision handling when the exponent is itself a bigInteger (for excessively large numbers).