-
Notifications
You must be signed in to change notification settings - Fork 886
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
Pin using reason leads to wrong error message #3420
Comments
Is the example text on this page? For example:
To have Chocolatey CLI ignore unavailable options, enable the |
Is this still relevant? If so, what is blocking it? Is there anything you can do to help move it forward? |
This is still a valid issue. |
@tbeckenhauer this issue is waiting on a response to the last comment. Without that, it will be closed. |
@pauby Yes it is. I ran into this, too. The documentation page would certainly benefit from a note box highlighting that |
Checklist
What You Are Seeing?
A single pin command must be listed. Please see the help menu for those commands
What is Expected?
Adding the pin or an error why it did nor work.
How Did You Get This To Happen?
I wanted to add a pin for a package like the documentation said:
This did not work, but showed the following error:
A single pin command must be listed. Please see the help menu for those commands
Well the help menu is where I got the commands from, so it was very confusing.
After some experimentaion I realized its because of the reason option. Leaving only that part out and it worked.
Back to the help page I noticed the original reason said something like "reasons available in business editions only", which I did not even read. It seemed like an example text, so why bother reading. I replaced it without thinking twice with my own text. Its probably not just an example text, but the reason the command failed I assume. So maybe that would be a good error message when using it anyways.
System Details
Installed Packages
Output Log
Additional Context
I would also suggest to add a highlight to the wrong parameter in the help page and command help.
The text was updated successfully, but these errors were encountered: