You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is what happens... The binding for foo is a VariableDeclarator but the comment is attached to the VariableDeclaration. We need to find the comment on the parent path.
Patch is on its way.
arv
added a commit
to arv/documentation
that referenced
this issue
Oct 19, 2016
When we find the binding for an export we get the VariableDeclarator.
It is common for people to write their JSDoc comment on the parent
VariableDeclaration so we check that in case there is no comment on the
declarator.
Fixesdocumentationjs#570
When we find the binding for an export we get the VariableDeclarator.
It is common for people to write their JSDoc comment on the parent
VariableDeclaration so we check that in case there is no comment on the
declarator.
Fixes#570
In #544 support for patterns like
has been added. However, the comment is lost and does not appear in the generated documentation.
I've tried to add it by adjusting
addComments
withinlib/extractors/exported.js
to the following:which worked (in some cases) but also resulted in some duplicated documentation. Any hint on how to implement this?
The text was updated successfully, but these errors were encountered: