Skip to content
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

Hard to pull error message from CallExecutionDetails #138

Closed
austinabell opened this issue May 11, 2022 · 0 comments
Closed

Hard to pull error message from CallExecutionDetails #138

austinabell opened this issue May 11, 2022 · 0 comments
Assignees

Comments

@austinabell
Copy link
Contributor

austinabell commented May 11, 2022

There are methods to view each failure outcome, but even then it's janky to get to a result that can be used. ExecutionOutcome is not exactly easy to pull information needed.

Likely goes in tandem with #100 since the types for a lot of these can be avoided to be obfuscated as they are, because it's unclear to distinguish between result types

Also related to #131 since the error from execution is from the result, so the pattern is just that you have to format that error and not be able to distinguish where the error came from

Some of these issues can be seen from near/near-sdk-rs@3490844 (#789) commit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants