Skip to content
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

Make it clear the location of the flags matter #61

Open
TimoGlastra opened this issue Feb 22, 2022 · 3 comments
Open

Make it clear the location of the flags matter #61

TimoGlastra opened this issue Feb 22, 2022 · 3 comments

Comments

@TimoGlastra
Copy link
Member

I always find this quite annoying about the docker cli, where it matters in which place the flags are passed (docker --flag run --other-flag is not the same as docker --other-flag run --other-flag). This makes sense for command specific arguments (e.g. --qr) but feels quite confusing for other flags.

Maybe the error message ("Error: No endpoint supplied. Supply an endpoint either via `--endpoint` or via `--config`") can be extended to make this more clear.

❯ aries-cli connections get-all
Error: No endpoint supplied. Supply an endpoint either via `--endpoint` or via `--config`

~
❯ aries-cli connections get-all --endpoint https://agent.community.animo.id
error: Found argument '--endpoint' which wasn't expected, or isn't valid in this context

	If you tried to supply `--endpoint` as a value rather than a flag, use `-- --endpoint`

USAGE:
    aries-cli connections get-all

For more information try --help
@berendsliedrecht
Copy link
Member

Yeah it is quite annoying. I think it is possible to have some global flags, but for right now I will expand the error message.

@berendsliedrecht berendsliedrecht added the Release V1 These issues should be resolved for a first open release label Feb 24, 2022
@berendsliedrecht
Copy link
Member

@jl-animo is this something you can pick up with the help messages?

gitbook-com bot pushed a commit that referenced this issue Apr 5, 2022
@berendsliedrecht berendsliedrecht removed the Release V1 These issues should be resolved for a first open release label Jul 18, 2022
@berendsliedrecht
Copy link
Member

I took a look at this again today, and I came to the same conclusion that I think its technically possible to add but there will be a lot of collision.

siera -a connection invite -a -> first -a is --api-key and second a is ---auto-accept

Do you think that some documentation at the siera -h command would suffice?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants