New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comment are not rendered when brackets are around an optional parameter #567
Comments
Hi @krenor, TypeDoc does not completely follow the JSDoc syntax but I think this is something that should be supported. PRs are welcome. |
I've got the same problem. |
jeremymeng
added a commit
to jeremymeng/azure-sdk-for-js
that referenced
this issue
Apr 23, 2019
where comments are not rendered when there are brackets around optional parameter name (TypeStrong/typedoc#567).
jeremymeng
added a commit
to Azure/azure-sdk-for-js
that referenced
this issue
Apr 23, 2019
* Add high level functions that takes string url parameters * Use intersection types for options parameter * Add documentation * Add type alias for the intersection types * Add docs for alias types * Work around typedoc issue where comments are not rendered when there are brackets around optional parameter name (TypeStrong/typedoc#567).
jeremymeng
added a commit
to jeremymeng/azure-sdk-for-js
that referenced
this issue
May 10, 2019
* Add high level functions that takes string url parameters * Use intersection types for options parameter * Add documentation * Add type alias for the intersection types * Add docs for alias types * Work around typedoc issue where comments are not rendered when there are brackets around optional parameter name (TypeStrong/typedoc#567).
Linking to the PR with a proposed fix for better visibility: |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Using JSDoc Syntax
@param {string} [key] An optional but fancy key
@param {string} key An optional but fancy key
The text was updated successfully, but these errors were encountered: