This change is required because since dox 0.5.0 a error will be thrown if "return" present but empty
This change also extends the message to say what gets returned

This change is required because since dox 0.5.0 a error will be thrown if "return" present but empty
This change also extends the message to say what gets returned

…Type.set"

This is because dox (jsdoctypeparser@1.2.0) does not seem to recognize "@callback" or "@typedef" with "@name"

…e.Collection"

… "QueryCursor.prototype[Symbol.asyncIterator]"

…stFunction"

…unction"

This also changes the description for the parameters to match "SchemaType.set" and not cause bad formatting
Also upates the return type to "void"

This also sometimes somehow messes-up the documentation styling

The things that were defined there are set via other things anyway, and many did not even have it set

This also changes the description for the parameters to match "SubdocumentPath.set" and not cause bad formatting
Also upates the return type to "void"

…y adding "()"

…unction" and "static"

This fixes static "Schematype" properties to be in a different case than instance properties

…pe for "connection" and "mongoose"

also warn if both a static and instance are found

…s loop

This will make setting "ctx.string" consistently and should make it independent of tag order
(Also thanks to the previous commit warns against both "instance" and "static")

…Map" to reflect actual name

…and add "@static"

…memberOf" handling

… result in a empty field

…ber all values

This makes use of https://www.typescriptlang.org/docs/handbook/jsdoc-supported-types.html and is still fully compatible with plain js

This currently does not add anything to the final documentation, because i dont know which style it should be

…stead of adding to "return"

This is changed because "return" property was never used, but the "description" was (in pug files)
but i am not familiar with pug to change that
Also updates the second "replace" call because "\n" is mostly added to the end which makes it ineffective

This is to change the style to be consistent and headers with ":" seem to be the most used, so it was changed to that