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
{{ message }}
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.
If the option is of type array, input is also of type array. Although the parameter of RegExp.test()should be of type string, it will somehow first convert other types to string and then perform regular expression match.
I want to extend the support for array. I offer to create a PR if this concept is okay.
The text was updated successfully, but these errors were encountered:
When I define an array-typed option with allowableValues, the validation doesn't seem to work properly.
Semantically I think this should be interpreted that this option accepts multiple values and each of the values should be allowable.
Currently, the validity is checked by this method:
imperative/packages/cmd/src/syntax/SyntaxValidator.ts
Lines 543 to 553 in ce314e1
If the option is of type array,
input
is also of type array. Although the parameter ofRegExp.test()
should be of type string, it will somehow first convert other types to string and then perform regular expression match.I want to extend the support for array. I offer to create a PR if this concept is okay.
The text was updated successfully, but these errors were encountered: