Feature Request: TransactionButton behaviour optionality

[PDiTO]

Describe the solution you'd like

More flexibility on how the transaction button behaves, particularly on transaction success.

We're trying to make our apps as suitable as possible for a non-crypto native audience. As a developer, current implementation is useful behaviour for debugging, but feels like a technical direction when most users likely won't care about transaction receipts and being able to reconcile them on a block explorer.

The button is also effectively dead post successful transaction. Say I want to mint multiple NFTs (as a very simple example) - how can I return the button back to its original state to allow this after a successful mint. I can think of many use cases where i'd want to be able to submit the same transaction multiple times.

Describe alternatives you've considered.

Hard view re-render onSuccess.

[fakepixels]

Great feedback! We're working on it.