-
Notifications
You must be signed in to change notification settings - Fork 328
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
Provide users useful feedback if the action hasn’t been accepted #1545
Comments
I think this work is for back-end. On the other hand, for iotexscan.io(wallet) when we send transaction, the error should be shown to users since currently we are showing just the transaction hash and don't let them know the error of sendAction api. (for the ioctl, it is returning from the api, so no need to change) |
@koseoyoung as long as there is some way to differentiate errors in the backend, we can throw error accordingly. |
please elaborate on the API that we can integrate with |
@puncsky In SendAction api, it's returning rpc error where code is 'internal' and message contains the error msg. Just like this
If it is too verbose, do we need to classify and redefine the error code like this ethereum/EIPs#136 ? |
I think we still need error code instead of error message |
because |
for example: https://github.com/googleapis/googleapis/blob/c372c656aef153931708c80ac1a8186060841cdf/google/api/expr/v1alpha1/conformance_service.proto#L145 |
Thanks for your helpful reference! so I'm thinking about defining error code as enum, is it fine?
|
@koseoyoung @puncsky pls help on this one
The text was updated successfully, but these errors were encountered: