-
Notifications
You must be signed in to change notification settings - Fork 58
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
Feature Request: Proper Error Handling for Near.Call #79
Comments
You can get the |
Seems to me also #83 could solve this |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is no way to know weather a function call (Near.call) was successful or not. This ends up with bad UX when the TX fails and we are unable to provide users with a clear next step e.g (fill account with balance, add access key, e.t.c)
It would be nice to be have and be able to await the
Near.asyncCall
so it waits until the tx is processed and has a status. This will let us create flows when the function calls errors out and retry logic.Side note:
Also, at the moment, the
<CommitButton>
does not do any sort of error handling or take in anonError callback
handler to deal with errors. That would be pretty helpful too. This has nothing to do with Near.call error handling.The text was updated successfully, but these errors were encountered: