Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Better CLI usage information output #196

Open
elyezer opened this issue Mar 30, 2020 · 0 comments
Open

Better CLI usage information output #196

elyezer opened this issue Mar 30, 2020 · 0 comments
Labels
bug Something isn't working

Comments

@elyezer
Copy link
Member

elyezer commented Mar 30, 2020

Running receptor with no subcommand raises the following:

$ receptor
ERROR 2020-03-30 16:33:45,492  __main__ main: an error occured while running receptor
Traceback (most recent call last):
  File "/home/elyezer/code/receptor/receptor/receptor/__main__.py", line 63, in main
    config.go()
  File "/home/elyezer/code/receptor/receptor/receptor/config.py", line 535, in go
    "you must specify a subcommand (%s)." % (", ".join(SUBCOMMAND_EXTRAS.keys()),)
receptor.exceptions.ReceptorRuntimeError: you must specify a subcommand (node, ping, send, status).

It would be better if receptor, as others CLI tools, provided the usage information if the minimum expected options/subcommands were not provided.

@ghjm ghjm added the bug Something isn't working label May 15, 2020
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants