You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
each sub command could describe its own CLI - own options, own switches, own arguments - and own help pages of cause.
for example cyclonedx requirements requires an argument to the requirement-file - which defaults to requirements.txt,
while cyclonedx-py environment does not.
... to be continued ...
and if each of the sub commands would act autonomous, it could even become available as a public python module:
$ python -m cyclonedx_py.cli --help
$ python -m cyclonedx_py.cli.conda --help
# ... and so on
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
current CLI is described here: https://github.com/CycloneDX/cyclonedx-python#basic-usage
proposal: change the CLI to use proper sub-commands - one for each ecosystem:
benefits:
for example
cyclonedx requirements
requires an argument to the requirement-file - which defaults torequirements.txt
,while
cyclonedx-py environment
does not.and if each of the sub commands would act autonomous, it could even become available as a public python module:
$ python -m cyclonedx_py.cli --help $ python -m cyclonedx_py.cli.conda --help # ... and so on
Beta Was this translation helpful? Give feedback.
All reactions