Arg parsing is now split into common options (in bin/documentation.js)
and command-specific options (in each command module, exported as
parseArgs).
This includes moving `--private` and `--github` to the common args
instead of having them under the build/serve commands. Reason: these
two args are options understood by the main module, as opposed to args
like `--format` which are only understood by the actual output piece
in build/serve.
Also removes `args.js`, which had previously exported the argument
parsing for use in situations like documentation-readme. The need
for this, I think, is largely made irrelevant in the face of slightly
generalizing the CLI to use commands.
* Compare strings as lowercase, to permit for v4+ compatibility
* Fix bad reference to loc.name
* Update README badge and fixture
* Remove brfs dependency
* Remove traverse
* Remove browser transform support
This new option change the previous behavior of parsing every input files
from module-deps except json. But if one use browserify to require json file
they may require other file types that cant be supported by documentationjs,
the new behaviour is to parse files whose extension match one in a whitelist
Some params cannot be identified with only param.name. This
changes the algorithm to transform parameters into doc objects
first, and then using the value of doc.name, which is defined
even for parameters with default values.
Given the `type` tag introduced with Flow, this can infer
a typedef statement, as well as infer its potentially
nested properties and their types.
This also includes
* Refactor of Markdown AST generation that fixes#228
* Refactor of nest.js to handle multi-level nesting
Fixes#191
This a specific exception for the case identified in 191: we could,
instead, include only cases of clear proximity, like var foo = function,
or function foo.
