-
Notifications
You must be signed in to change notification settings - Fork 192
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
feat: Transaction
component - add calls
support
#1220
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
if (!transactions) { | ||
return; | ||
} | ||
if (walletCapabilities.hasAtomicBatch) { |
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.
should this use batchedTransactions even only one transaction?
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.
yep - batch of 1 is valid as well
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.
Masterpiece!
Love the way you are growing into a Michelin Star chef.
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.
amazing
What changed? Why?
calls
prop toTransaction
calls
vscontracts
option toTransaction
component in Playgroundcontracts
with atransactions
state inTransactionProvider
that is set based on the provided propsNew hooks
useSendWalletTransactions
useWriteContract
,useWriteContracts
,useSendCall
, anduseSendCalls
)useTransactionType
calls
orcontracts
)Notes to reviewers
How has it been tested?
In Playground with
calls
andcontracts
optionsexample userop with batched calls - https://base.blockscout.com/op/0xa1a33c1f8466a40350ee8558da4f3cfbd0762bbd77f56cd85c91c81669cacdb7