Mark command parameter required if there is no fallback #20

Merged
merged 1 commit into from Jul 12, 2012

Conversation

Projects
None yet
2 participants
Contributor

calmh commented Jul 12, 2012

This change results in:

  • The "command" parameter being shown as <required> rather than
    [optional] when there is no fallback set with .nocommand()
  • It being an error (thus showing help) if no command is passed when
    one is expected, and there is no fallback set with .nocommand()
Mark command parameter required if there is no fallback
This change results in:

 - The "command" parameter being shown as <required> rather than
   [optional] when there is no fallback set with .nocommand()

 - It being an error (thus showing help) if no command is passed when
   one is expected, and there is no fallback set with .nocommand()

harthur added a commit that referenced this pull request Jul 12, 2012

Merge pull request #20 from calmh/command-required
Mark command parameter required if there is no fallback

@harthur harthur merged commit 89c0b2c into harthur:master Jul 12, 2012

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment