Fix metadata parsing for large numbers in XML responses #1381
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.
Fix metadata parsing for large numbers in XML responses
Description
Fixed an issue with metadata parsing where large numbers in XML responses were being incorrectly handled due to BigInt conversion. Updated XMLParser configuration to properly handle leading zeros and maintain string representation of large numbers.
Changes
numberParseOptions
to XMLParser configurationleadingZeros: true
to preserve leading zeros in numeric stringseNotation: false
to prevent scientific notation conversionhex: true
to properly handle hexadecimal valuesProblem
Previously, large numbers in metadata could be incorrectly parsed or lose precision when converted to JavaScript numbers, especially when dealing with BigInt values.
Solution
Updated XMLParser initialization with proper number parsing options to maintain string representation of numeric values and preserve leading zeros.
Testing