v1.0.0

It's finally here! jsdoctypeparser has been updated to v9.0.0.

v0.9.1

• Dependency bumps for commander and markdown-it to address security vulnerabilities

v0.9.0

• Markdown is now generated using the markdown-it package, which conforms to Commonmark standards. Note, this may be a breaking change, as markdown output will change.
• Fix: Dox now recognizes ES6 template strings as strings and does not attempt to parse their contents.
  • Deps: added [email protected]
  • Deps: removed marked
• DevDeps: [email protected]
• DevDeps: [email protected]

v0.8.1

• Fix: Dox will no longer falsely enter or exit string blocks when encountering an escaped quote or double-quote
• Deps: [email protected]
• Deps: [email protected]

v0.8.0

• Fix: Tags with whitespace between the tag start and the previous line ending are now parsed correctly.
• Deps: [email protected]
• Deps: [email protected]
  • Better compatibility for type declarations, but may result in changes to output with invalid types.

0.7.1

• Context parsing has been re-factored into an array of functions that are iterated over until a match is found. This array is exposed as dox.contextPatternMatchers, allowing for extension with new contexts without needing to edit the dox source.
• Fix: ES6 classes extended from sub-properties (such as Backbone.View) are now properly matched

0.7.0

• Add context parsing for some ES6 syntax:
  • classes
  • class constructors
  • class methods
  • assignments via let or const
• Add support for @description tag
• Add context match for returned closure
• Add: Tags without descriptions now have an html property containing a markdown parse of the tag's contents
• Fix: more agnostic to code style when parsing contexts (eg, no longer ignores functions without spaces between function name and parenthesis)
• Fix: No longer incorrectly tries to parse strings inside comments, causing large chunks of a file to be ignored.
• Fix: No longer parses double slash in a string literal as being a comment start.
• Deps: [email protected]