This repository has been archived by the owner on Apr 26, 2021. It is now read-only.
Option parser trips up if -- present in description RHS
#34
Labels
Milestone
Comments
felixSchl
added a commit
that referenced
this issue
May 23, 2016
felixSchl
added a commit
that referenced
this issue
May 24, 2016
**NOTE**: These changes have a minor impact on how descriptions are
parsed, addressing issues outlined in #34
* Allow <positionals>, POSITIONALS and --options to be described in
description section. However, only --options actual extract meaningful
information such as [env] and [default] tags.
* Lift strict alignment rules of options in the description section.
A new option or positionals description is assumed if it is *less*
indented than the preceding text block of descriptions. This should
*hopefully* make for a intuitive and more lax way to author
description sections.
* Refactor from 'Option' newtype to 'OptionObj' - this is going to be an
incremental process across all modules to move away from unnecessary
newtypes.
* Update all git examples to print the `JSON.stringify`-ed version of
the parsed args and write tests against it (see './test-js')
* Add more tests to the compat spec test suite
* Write mocha tests against examples
|
Resolved: bfa9bd7 |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Refer to the comment in
./examples/git/clone.jsThe text was updated successfully, but these errors were encountered: