connect
connect copied to clipboard
Propagate transaction broadcast errors to openContractCall
Right now there is now way to know if a transaction has been rejected by the API.
It would be useful if calls such as openContractCall
would include an onFailure
callback or similar that gets fired whenever there is an issue.
Relaying a comment from @aulneau in Discord:
yeah, this is something i've run into in the past, it's so hard to debug
onFailure
seems like it might make sense, was thinking about how it'd be nice to have these three:
onSuccess
- meaning it's a correct transaction, and it's been broadcastonFailure
- failed for some reasononCancel
- user ends session before completing any actioni'm not sure this would make sense for message signing though, but it could
I think this makes a lot of sense too, it'd be nice to be able to target each state with a specific strategy on the UI/UX side.