You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I understand you guys want to make it more decomposable with each hook, but it is annoying to have to manually generate the hooks for useContractWrite and useWaitForTransaction to create a full flow for the UX on a button that is alternating its render based on the TX state. Forgive me if there is a easier way of creating this and I haven't found it
e.g.
tx click handler
tx submit
tx pending
tx confirmed
Is there any chance of adding in some of the props from useWaitForTransaction into useContractWrite so we can remove the necessity of useWaitForTransaction (wagmi) / waitForTransactionReceipt (viem)? It would make the code much cleaner for end-user developers
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi guys,
I understand you guys want to make it more decomposable with each hook, but it is annoying to have to manually generate the hooks for
useContractWriteanduseWaitForTransactionto create a full flow for the UX on a button that is alternating its render based on the TX state. Forgive me if there is a easier way of creating this and I haven't found ite.g.
Is there any chance of adding in some of the props from useWaitForTransaction into useContractWrite so we can remove the necessity of
useWaitForTransaction (wagmi)/waitForTransactionReceipt (viem)? It would make the code much cleaner for end-user developersThank you so much for your hard work guys 😊
Beta Was this translation helpful? Give feedback.
All reactions