-
Notifications
You must be signed in to change notification settings - Fork 98
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
test if errors work in voyager #1192
Comments
What does this mean? |
Updated the description. |
So is this a spike proposal? |
How did it end up in Scrumptious with no one assigned? |
This was a follow up for @fedekunze ticket on the SDK. I forgot the assign someone as it wasn't created in process. I will get to it if I find time. |
Plan:
|
using 0.24.2-fd8c1e52 there is no change visible. I still get the same error structure. Case sent too many tokens I don't have. @fedekunze |
As of cosmos/cosmos-sdk#2119 errors returned by the LCD are not longer plain text (with a lot of additional noise) but a JSON object. This should deprecate the need to parse out the error message from this plain text error.
The question is, is there an additional need to adjust Voyagers error parsing (to show the correct error to the user) or do we still need to parse the error from the JSON object.
The text was updated successfully, but these errors were encountered: