Skip to content

fix: converts string to bigint in specific cases when parsing v2 traces#4

Merged
aorumbayev merged 1 commit intomainfrom
fix/v2-spec-parser
Oct 23, 2025
Merged

fix: converts string to bigint in specific cases when parsing v2 traces#4
aorumbayev merged 1 commit intomainfrom
fix/v2-spec-parser

Conversation

@aorumbayev
Copy link
Copy Markdown
Collaborator

@aorumbayev aorumbayev commented Oct 2, 2025

Fixes algorandfoundation/algokit-avm-vscode-debugger#98

The objectToMapRecursive function now converts string values to bigint
when the key is 'uint' and the value is a numeric string.

This is required for some numeric string values that exceed the safe
integer range when users are working with legacy simulation traces emitted from v2 of algosdk

The objectToMapRecursive function now converts string values to bigint
when the key is 'uint' and the value is a numeric string.

This is required for some numeric string values that exceed the safe
integer range when users are working with legacy simulation traces emitted from v2 of algosdk
@aorumbayev aorumbayev merged commit a56058a into main Oct 23, 2025
4 checks passed
@aorumbayev aorumbayev deleted the fix/v2-spec-parser branch October 23, 2025 13:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Refine v2 to v3 simulation trace parser to account for edge cases when bigints are represented as strings

2 participants