Allow users to specify own options #92
Labels
feature
Feature request
Milestone
Comments
sbeyer
added a commit
that referenced
this issue
Mar 17, 2017
This is not the best solution to the problem that the users may want additional options and tackle them. But it is a solution to the fact that users may want usage information when they use invalid options or arguments. Hence it is merged as an intermediate solution. A better solution is described in #92.
|
Also let bandit be more helpful and show users which of their used options are unknown, etc. |
sbeyer
added a commit
that referenced
this issue
Mar 19, 2017
It could be helpful for the user to see when she used options that are unknown. However, bandit's usage is simple enough to assume that the usage screen is helpful enough. Also printing unknown options may be confusing if user code adds custom options (which is a hacky thing, so far...) Hence, this commit removes the TODO marker. As soon as there is a nice way to add custom options to bandit (see #92), one should add such output.
sbeyer
added a commit
that referenced
this issue
Mar 19, 2017
It could be helpful for the user to see when she used options that are unknown. However, bandit's usage is simple enough to assume that the usage screen is helpful enough. Also printing unknown options may be confusing if user code adds custom options (which is a hacky thing, so far...) Hence, this commit removes the TODO marker. As soon as there is a nice way to add custom options to bandit (see #92), one should add such output.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Users should be able to set up an array for the option parser
and provide it to
bandit::runto allow additional options (forexample --extended-tests or something might be a use-case).
Those options must be accessible within all tests.
The text was updated successfully, but these errors were encountered: