Tom MacWright

The more general problem is a fair bit tricker than this example lets on: - If you do want to mark something as optional, do you have to repeat the...

The first place is [parse.js](https://github.com/documentationjs/documentation/blob/master/lib/parse.js), which currently has a `todo` for enum. And then implementing output and any effect on hierarchy (I don't think enum affects hierarchy). Unfortunately the more...

✔️ Merged `@deprecated` tag support

Hi Philipp! With this input on current `master`, beta.19, and rc.0, I get the documentation: ``` documentation.js build -f html foo.js -o /tmp/out ```  Could you try upgrading to...

You can see the recent PR that removed position in #1369. position information was bloating test fixtures (to the tune of 14k LoC) and didn't have any clear purpose in...

Mind specifying the complete source code of that file? The thing with 'unexpected token' errors is that it's "unexpected" because of context. It's not that there's a specific 'bad' token,...

Looks like this is an error thrown by doctrine, the underlying JSDoc parser, so it's a JSDoc syntax error rather than a JavaScript one, and it appears to be triggered...

Please don't bump issues - I'll post back on something if I've made progress on it.

Could you do ``` documentation serve packages/*/index.mjs --require-extension mjs --parse-extension mjs ``` The gist of the answer is that documentation.js - at least so far - just uses the glob...

documentation.js doesn't use or support jsdoc configuration files - if you want to use them, you should use the jsdoc tool instead.