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
Is there a syntax to specify a valid command regardless of the order the command is entered?
For example, I want the following commands to be valid:
cli> aa bb cc dd cli> aa bb dd cc cli> aa cc bb dd cli> aa cc dd bb cli> aa dd cc bb cli> aa dd bb cc
Right now I believe you would have to explicitly state each command in the syntax like so:
aa { bb { cc dd; dd cc; } cc { bb dd; dd bb; } dd { bb cc; cc bb; } }
It is fine implementing this when there are only a few commands which you want like this. (i.e here we have 3 keyword, so only 3! (6) to consider)
However, if you have lots of commands like this. then the amount of permutations that you need to consider grows quickly!
Any solution to this?
The text was updated successfully, but these errors were encountered:
See #22 (and #23). This is a sufficiently common request so I will try to look into it.
Sorry, something went wrong.
New "sets" feature added, see: ed1997a
Example: aa @{ bb; cc; dd; }
Great! This seems to be working! Thanks for adding it in!
No branches or pull requests
Is there a syntax to specify a valid command regardless of the order the command is entered?
For example, I want the following commands to be valid:
Right now I believe you would have to explicitly state each command in the syntax like so:
It is fine implementing this when there are only a few commands which you want like this. (i.e here we have 3 keyword, so only 3! (6) to consider)
However, if you have lots of commands like this. then the amount of permutations that you need to consider grows quickly!
Any solution to this?
The text was updated successfully, but these errors were encountered: