- create `jsdoc/tag/inline` module, a generalized parser for inline tags
- use the new module to look for an inline `{@type}` tag in tag text;
for tags that can have a type, the inline tag overrides the type
expression
- update submodule
introduces a real parser for Closure Compiler types, and uses the
parser to interpret type expressions in JSDoc tags.
TODO:
- provide a way to override the type expression
- update templateHelper to generate the correct links in type
applications
future enhancement (to be filed as a new issue): create pseudo-tags for
members that are described in the type expression (e.g., if the type
expression for the parameter `foo` is `{bar: string}`, add a tag for
`foo.bar` with no description)
Technically, JSHint is only a dev dependency. But if you run `npm
install --dev git://github.com/jsdoc3/jsdoc.git`, npm tries to install
approximately every npm package that has ever existed, including many
that require gcc compilation.
This approach seems like the sanest workaround.
