-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Get the module tag to work correctly when it's combined with other JSDoc comments #679
Comments
I'm guessing this was an unanticipated use case for the Right now, the AST node for I wouldn't be surprised if #678 is caused by the same problem as this bug. |
sounds like they are connected, if what you say is true.. obviously we can live without the concise version but it's a lot more user-friendly.. |
This change is going to be surprisingly difficult, if not impossible, to implement. Here's why. A JSDoc comment can define a symbol name by including:
If JSDoc is able to get a symbol name just by parsing the comment, it assumes that the comment is a "virtual comment" for a symbol that doesn't actually show up in the code. For example, if JSDoc parses the following source file, it correctly assumes that the JSDoc comment isn't related to the function declaration that follows it: /** @module foo */
function bar(baz, qux) {} To implement this change to the |
Updated the summary to match the actual issue more closely. |
i'm working on
master
with these files: https://gist.github.com/75lb/762bf8d94ba926492450here's an exported function written in the style documented at usejsdoc.com:
this file renders correctly in the generated documentation.
I re-wrote it to be more concise:
this did not render, is this the intended behaviour or a bug?
jsdoc2md/jsdoc-to-markdown#3
The text was updated successfully, but these errors were encountered: