Lloyd Brookes

You can obtain the template data yourself (via [`getTemplateData()`](https://github.com/jsdoc2md/jsdoc-to-markdown/blob/master/docs/API.md#module_jsdoc-to-markdown--JsdocToMarkdown+getTemplateData)), sort it as desired then pass it as the `options.data` option into [`.render()`](https://github.com/jsdoc2md/jsdoc-to-markdown/blob/master/docs/API.md#jsdoc2mdrenderoptions--promise).

Does this comment block render correctly using [jsdoc](https://github.com/jsdoc/jsdoc)? Jsdoc2md sits downstream of jsdoc, so if it's broken in jsdoc it will be broken in jsdoc2md..

I've looked into a workaround but unfortunately there's nothing I can do to stop jsdoc parsing the `@` character in example blocks. It's a [known issue](https://github.com/jsdoc/jsdoc/issues/1521). Generally, you can use...

Unfortunately, that's as much information as we receive from the underlying jsdoc app. If jsdoc returned the full error stack jsdoc2md would print it. Follow the upstream issue [here](https://github.com/jsdoc3/jsdoc/issues/1345).

true, the fix has landed on master.. Once @hegemonic has finished the new release (3.5.0) i'll pull it into jsdoc2md.

Hi, does your inherited method document as expected using jsdoc directly? If not, it's likely an issue with jsdoc (which jsdoc2md uses internally).. Check their [issue log](https://github.com/jsdoc/jsdoc/issues)..

handbrake-js is a project with documented events - the event docs on this project generate fine.. this source ``` /** Fired at regular intervals passing a `progress` object. @event module:handbrake-js~Handbrake#progress...

yes, i agree the `@type` field is ignored.. because the event can pass more than 1 type to the event handler.. instead, define the args the the event fires with...

both the jsdoc and handbrake-js examples are correct.. they should both be supported (both the @type and @param) method.. the @type method isn't supported yet but it will be in...

hi, sorry - has been a busy weekend.. will look tomorrow..