-
Notifications
You must be signed in to change notification settings - Fork 69
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
optional
parameters and cleos
#1959
Comments
@heifner I think this one needs a quick look to determine if this is expected behavior or a bug, and what the implications are if it is a bug. |
@bhazzard this is a bug. I was able to reproduce with the provided contract. |
I'm not so sure I'd consider this a bug. If it is to be considered a bug, it's nothing specific to an For some other examples, consider
Also this applies to API endpoints as well,
Again, |
Noticed something weird.
If I have an action with optional parameter(s):
Then I can pass into cleos whatever I want as action parameters and it will accept it:
I thought it's supposed to validate against ABI.
Caught me by surprise after I changed action signature in my contract but my test script continued to work fine without producing an error.
The text was updated successfully, but these errors were encountered: