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.

Sign up for GitHub

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

Jump to bottom

ExecutionOutcome ValueOrReceiptId::Value should have convenient methods for parsing outcome #201

Closed
ChaoticTempest opened this issue Sep 21, 2022 · 0 comments · Fixed by #208
Closed

ExecutionOutcome ValueOrReceiptId::Value should have convenient methods for parsing outcome #201

ChaoticTempest opened this issue Sep 21, 2022 · 0 comments · Fixed by #208

Comments

@ChaoticTempest
Copy link
Member

Currently, ExecutionOutcome internal returned value is just being exposed purely as a ValueOrReceiptId::Value(String), which does not offer all the convenience methods of json, borsh, or raw_bytes which makes it feel inconsistent with the other APIs. Ideally should add in a new Value type that offers these convenient methods.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

chore: Made ValueOrReceiptId::Value object consistent near/near-workspaces-rs
1 participant
@ChaoticTempest