|
Is there a smarter way to define the |
Answered by
rsteube
Mar 22, 2026
Replies: 1 comment 2 replies
|
The attached value is not enforced for the shorthand but should work ( flags:
-t, --threads=: use N threads
completion:
flag:
threads: ["1", n] |
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Yes, that is what I mean with it not being enforced. The attached variant works, so it is up to the user to set the flag value correctly.
I tend to define the flag as above even though passing it space-separated is allowed by the flag parser / the completions.
Enforcing the correct usage involves work in the flag parser which is something to tackle sometime in the future.