-
-
Notifications
You must be signed in to change notification settings - Fork 235
Adds transactionBatches
into transaction controller state
#5793
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
Conversation
c3f8a6b
to
49e9a89
Compare
31069c4
to
e62592d
Compare
Co-authored-by: Matthew Walsh <[email protected]>
…:MetaMask/core into feat/add-batch-transaction-approval-type
transactionBatches
into transaction controller statetransactionBatches
into transaction controller state
@metamaskbot publish-preview |
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions.
|
@metamaskbot publish-preview |
Preview builds have been published. See these instructions for more information about preview builds. Expand for full list of packages and versions.
|
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.
Changes to controller-utils look good
Explanation
This PR introduces support for batch transactions in the Transaction Controller by adding a new
ApprovalType
and extending the state to handleTransactionBatches
. These changes enable enhanced metadata management for sequential batch flows, including UI updates for gas estimation and future automation capabilities.Changes
Controller Utils
ApprovalType
to the enum:TransactionBatch
, to support batch transactions.Transaction Controller
transactionBatches
, to store metadata for transaction batches.addBatchMetadata
, responsible for populating batch-specific metadata.TransactionBatchMeta
, to manage metadata for transaction batches.addBatchMetadata
to store batch metadata andwipeTransactionBatches
to clean up state after batch hook completion.Rationale
The introduction of
TransactionBatchMeta
allows for a clean separation of metadata for batch transactions, which conceptually differ from individual transactions. This ensures:TransactionMeta
for individual transactions may not yet exist.These changes lay the groundwork for improved handling of batch transactions and pave the way for future enhancements.
References
Changelog
Checklist