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: only merge token transfers when approval status matches #2655
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
fix: only merge token transfers when approval status matches #2655
Changes from all commits
e4208bbFile filter
Filter by extension
Conversations
Uh oh!
There was an error while loading. Please reload this page.
Jump to
Uh oh!
There was an error while loading. Please reload this page.
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🗄️ Data Integrity & Integration | 🟠 Major | ⚡ Quick win
Keep
expected_decimalstoken-scoped for approval-separated transfers.Proto field:
TokenTransferList.expected_decimals(field 4). Issue type: Asymmetric round-trip. The schema defines this value once per token transfer list, not once per account amount. (github.com)If a regular transfer without decimals is added first and an approved transfer with decimals is added second, Line 164 prevents a merge.
build_token_transfers()then serializes the first entry'sNonevalue and drops the caller's expected decimals. The transaction can skip the requested decimal validation.src/hiero_sdk_python/tokens/abstract_token_transfer_transaction.py#L164-L167: propagate an explicit decimal value to the token's existing entries, and inherit the token decimal value for a new entry when the caller passesNone.tests/unit/transfer_transaction_test.py#L548-L583: build a transaction with a normal no-decimal transfer followed by an approved decimal transfer, then asserttokenTransfers[0].expected_decimals.value.Proposed implementation direction
As per path instructions, protobuf fields must match their schema semantics and unit tests must cover edge cases.
📍 Affects 2 files
src/hiero_sdk_python/tokens/abstract_token_transfer_transaction.py#L164-L167(this comment)tests/unit/transfer_transaction_test.py#L548-L583Source: Path instructions