-
Notifications
You must be signed in to change notification settings - Fork 303
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
InputParameters' "default" value used when an invalid "options" value is provided #1531
Comments
Hi @jnapprogs, thank you for pointing this out. I don't have an immediate answer for you since this does not appear to be due to the |
@austinborn , thanks for the response! I should be fine on the debugging front, but will definitely reach out in the event I have to 🚀 |
@jnapprogs I believe this should resolve the issues you were seeing. With this change, an input that's not a part of the |
Awesome! Thanks for the info! |
Of course! Happy to get a quick turnaround on this one. |
Hi all! I was wondering if I can get some insight for the behavior of the
default
property for theInputParameters
type. I have an input parameter initialized as follows:If I do not provide a value for the
item
parameter, then it defaults tofirst
. If I specify any of the values in theoptions
property, then that value is used instead; however, if I was to provide a value that isn't part of theoptions
property, saythis should break
, it defaults tofirst
. Even though a default value has been specified, I assumed that the adapter would throw an error as a value has been provided that isn't part of theoptions
property. As an external user, if I wanted afourth
item, I would keep receiving back thefirst
item.With that, is the
default
value intended to be used in the event a user does not provide a value, or does it also play a dual role in being the default value if a wrongoptions
value is provided?The text was updated successfully, but these errors were encountered: