We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When using a specification like:
<basedn:string regexp:"(((CN|cn)=([^,]*)),)?((((CN|cn|OU|ou)=[^,]+,?)+),)?(((DC|dc)=[^,]+,?)+)">
a failure to match this generates the following diagnostic:
tnsr1 tnsr(config-ldap)# basedn "wrong" Feb 15 12:41:31: clicon_parse result:0 command: "basedn "wrong"" CLI syntax error: "basedn "wrong"": "wrong" is invalid input for cli command: basedn tnsr1 tnsr(config-ldap)#
which is generic enough to be of little help.
Recommending an additional field called error-message:<string> that would allow CLI writers to customize error messages.
error-message:<string>
The string could optionally contain a %s field.
string
%s
The text was updated successfully, but these errors were encountered:
error-message
No branches or pull requests
When using a specification like:
a failure to match this generates the following diagnostic:
which is generic enough to be of little help.
Recommending an additional field called
error-message:<string>
that would allow CLI writers to customize error messages.The
string
could optionally contain a%s
field.The text was updated successfully, but these errors were encountered: