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
Author the user story for this feature
As a user, I want to be informed when I use sets of commands that can be mutually exclusive.
Is your feature request related to a problem? Please describe.
When I working about issue #1057 I saw we can have potential more conflicts on commands or unexpected/not clear behavior.
Describe the solution you'd like
I think we can investigate commands and add validation or document potential conflicts.
This only my small proposal, please team tell me what do you think? @bootstraponline @jan-gogo @pawelpasterz @piotradamczyk5 @Sloox Thanks!
The text was updated successfully, but these errors were encountered:
I love this idea!
Sorry, something went wrong.
Great idea, I think that should also be processed together with reviewing commands documentation
adamfilipow92
Successfully merging a pull request may close this issue.
Author the user story for this feature
As a user, I want to be informed when I use sets of commands that can be mutually exclusive.
Is your feature request related to a problem? Please describe.
When I working about issue #1057 I saw we can have potential more conflicts on commands or unexpected/not clear behavior.
Describe the solution you'd like
I think we can investigate commands and add validation or document potential conflicts.
This only my small proposal, please team tell me what do you think?
@bootstraponline @jan-gogo @pawelpasterz @piotradamczyk5 @Sloox
Thanks!
The text was updated successfully, but these errors were encountered: