-
Notifications
You must be signed in to change notification settings - Fork 116
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
Unable to pass "Some None" to contract call #2344
Comments
The solutions in the subsequent release column look great :) |
hui-an-yang
added a commit
that referenced
this issue
Apr 17, 2023
hui-an-yang
added a commit
that referenced
this issue
Apr 19, 2023
9 tasks
hui-an-yang
added a commit
that referenced
this issue
Apr 19, 2023
dsawali
pushed a commit
that referenced
this issue
Apr 19, 2023
* fix: current work to support nested option re #2344 * simplify option encode * feat: supporting nested option of some(none) in encodeObject and encode(limitation) re #2344 * revert: implementation and test of nested options with encode (due to limitation) re #2344 * test: added integration tests and documentation re #2344 --------- Co-authored-by: Alireza Haghshenas <[email protected]>
6 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
With the current implementation for contract call parameters, it is impossible to pass the value
Some None
to an entrypoint that requires a value of typeoption (option timestamp)
, for example.Although this is an edge case, Taquito should provide a more intuitive way to pass options and nested options as contract call parameters, as the current way becomes inefficient or even broken with nested options.
The text was updated successfully, but these errors were encountered: