Fixed JSDoc comments and optional params parsing

[3bl3gamer]

Closes #1804 and #567

[pkuczynski]

Any chance to get this merged anytime soon?

[ST-DDT]

This works very well for:

 * @param {string} [name] Some optional param.

but not for this syntax:

 * @param [name] Some optional param.

as used by tsdocs/typescript.

This is caused by consumeTypeData that erases all leading {} and [] blocks. But if it encounters both, then the cleanup of the {} does not remove the separating space and thus the [] won't be removed. If the [] is the first section, then it will get removed.

Can someone enlighten me why the [] is removed/what is it used for originally in jsdocs?

[pkuczynski]

Can someone enlighten me why the [] is removed/what is it used for originally in jsdocs?

Its to mark optional parameter: https://jsdoc.app/tags-param.html#optional-parameters-and-default-values

[ST-DDT]

Its to mark optional parameter: jsdoc.app/tags-param.html#optional-parameters-and-default-values

Currently these get removed completely, so any parameter name that might be in there will be lost, before it is analyzed.
Rendering it unusable. I thought there might be a different usecase where you don't need the thing inside the [].

[pkuczynski]

@Gerrit0 any plans to get this merged in any foreseeable future?

[Gerrit0]

I believe with 0.23, this is handled by the completely reworked comment parser, thanks for the PR though!