-
Notifications
You must be signed in to change notification settings - Fork 18
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
Update TransactionPreviewResponse
in Core API schema
#1043
base: develop
Are you sure you want to change the base?
Conversation
… in TransactionPreviewResponse
TransactionPreviewResponse
in Core API schema
A typical client of this API is not expected to use this receipt. The primary clients | ||
this receipt is intended for is the Radix wallet or any client that needs to perform | ||
A typical client of this API is not expected to use this receipt. The primary clients | ||
this receipt is intended for is the Radix wallet or any client that needs to perform | ||
execution summaries on their transactions. | ||
instruction_resource_changes: |
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.
Although this field is no longer required, it is currently always included in the TransactionPreviewResponse
within the transaction preview handler.
It might be more logical to introduce an instruction_resource_changes
flag in the TransactionPreviewResponseOptions
to control whether instruction_resource_changes
should be included in the TransactionPreviewResponse
.
@dhedey WDYT?
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.
Personally I'd rather not introduce a flag if we're deprecating it, because the flag would have to default to true
anyway for backwards compatibility, so we don't get any real use out of it, it will just be a pain because we'll have to have a deprecated flag for another protocol update after the feature is removed :)
Quality Gate passedIssues Measures |
Docker tags |
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.
Nice work, thanks
A typical client of this API is not expected to use this receipt. The primary clients | ||
this receipt is intended for is the Radix wallet or any client that needs to perform | ||
A typical client of this API is not expected to use this receipt. The primary clients | ||
this receipt is intended for is the Radix wallet or any client that needs to perform | ||
execution summaries on their transactions. | ||
instruction_resource_changes: |
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.
Personally I'd rather not introduce a flag if we're deprecating it, because the flag would have to default to true
anyway for backwards compatibility, so we don't get any real use out of it, it will just be a pain because we'll have to have a deprecated flag for another protocol update after the feature is removed :)
execution summaries on their transactions. | ||
instruction_resource_changes: | ||
type: array | ||
description: | | ||
This object holds changes in resource balances for all vaults within affected |
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.
It's probably worth saying it does not include recalls, and should not be relied on for a comprehensive view of balance changes. Instead, the receipt balance changes should be used.
@@ -28,10 +28,10 @@ pub(crate) async fn handle_mempool_transaction( | |||
)), | |||
); | |||
} else { | |||
payload_hashes.get(0).unwrap() | |||
payload_hashes.first().unwrap() |
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.
It looks like you must have run clippy
at a different (more recent?) version compared to the code base.
This isn't a problem, but in future, can we create a separate PR for reformatting changes, if we want to do them? This avoids too much noise in the PR :)
Benchmark summary 2024-12-23 10:26:26 |
Summary
Deprecate and mark as not-required
instruction_resource_changes
field inTransactionPreviewResponse
.