-
Notifications
You must be signed in to change notification settings - Fork 22
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
enhancement ocm --help
misleading synopsis of [<options>]
and flags
#1189
Labels
area/ipcei
Important Project of Common European Interest
component/ocm-cli
OCM Command Line Interface
kind/feature
new feature, enhancement, improvement, extension
Comments
This issue was marked as stale because it has not had recent activity. |
github-actions
bot
added
lifecycle/stale
Nobody worked on this for 6 months (will further age)
and removed
lifecycle/stale
Nobody worked on this for 6 months (will further age)
labels
Oct 24, 2024
github-actions
bot
added
the
area/ipcei
Important Project of Common European Interest
label
Dec 13, 2024
fabianburth
added a commit
that referenced
this issue
Dec 13, 2024
<!-- markdownlint-disable MD041 --> #### What this PR does / why we need it Renames the `Flags` section in `--help` to `Options`. The `Synopsis` currently shows `ocm [<options>] ...`, with <options> referring to the command line options listed under `Flags`. This might confuse users (or at least concern if something does not work). **Before:** ``` > ocm get component --help ocm get componentversions — Get Component Version Synopsis: ocm get componentversions [<options>] {<component-reference>} Aliases: componentversions, componentversion, cv, components, component, comps, comp, c Flags: -c, --constraints constraints version constraint -h, --help help for componentversions --latest restrict component versions to latest --lookup stringArray repository name or spec for closure lookup fallback -o, --output string output mode (JSON, json, tree, wide, yaml) -r, --recursive follow component reference nesting --repo string repository name or spec -S, --scheme string schema version -s, --sort stringArray sort fields ``` **Now:** ``` > ocm get component --help ocm get componentversions — Get Component Version Synopsis: ocm get componentversions [<options>] {<component-reference>} Aliases: componentversions, componentversion, cv, components, component, comps, comp, c Options: -c, --constraints constraints version constraint -h, --help help for componentversions --latest restrict component versions to latest --lookup stringArray repository name or spec for closure lookup fallback -o, --output string output mode (JSON, json, tree, wide, yaml) -r, --recursive follow component reference nesting --repo string repository name or spec -S, --scheme string schema version -s, --sort stringArray sort fields ``` #### Which issue(s) this PR fixes <!-- Usage: `Fixes #<issue number>`, or `Fixes (paste link of issue)`. --> #1189
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/ipcei
Important Project of Common European Interest
component/ocm-cli
OCM Command Line Interface
kind/feature
new feature, enhancement, improvement, extension
Context:
When using
--help
flag, it often displays a long, detailed and very well written text.During discovery of #1186, I tried to figure out via
--help
in which order to put theflags
executing anyocm
command.I tried to figure out, if I made any mistake and the flags that I tried to use were just ignored, because I placed them in the wrong order.
What would you like to be added:
Rename
[<options>]
to either[<flags>]
or renameflags
tooptions
.Why is this needed:
Avoid confusing
ocm
end users and make it 100% clear in which order to putflags
within the command synopsis.The text was updated successfully, but these errors were encountered: