You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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
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) commitThe text was updated successfully, but these errors were encountered: