Possibility to mark options as required #1
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
pholser
added a commit
that referenced
this pull request
Apr 27, 2011
Possibility to mark options as required
|
Merged. Should options which are marked as required cause the help screen entries for those options to look any different from the others? If so, what would you propose? |
|
Well I suppose they should, since the exception is thrown @ parse time. Didn't think of that initially, sorry for that I guess... I think something along the lines of "" before the "default" spec should do just fine. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hey, so I added the "required" flag we talked about, changes are minimal and I added a test-case for the required flag in the OptionParser unit test. Anyway, You can see the changes clearly in the changed files section I guess...