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
It seemed that auto fixing by require-jsdoc is incorrect.
This bug add jsdoc comment to incorrect position in arrow function case.
If you would like to check, running the command in bellow with the repository is reproduction the bug.
Seems essentially the same as #403, so closing. Feel free to subscribe there, or if you think the issue is different (beyond being about arrow vs. non-arrow expressions), feel free to comment further here.
gajus#403, gajus#502, gajus#522
Properly finds base node for affixing jsdoc block and uses to determine appropriate indent (finds base node in a manner sensitive to context, reusing existing and more accurate detection for this purpose, improving detection for function expressions, including arrow function expressions and method definitions).
As part of `getReducedASTNode` (used also within `getJSDocComment`), need to stop at `VariableDeclaration` or `ExpressionStatement` (where comments shouldl be checked). Needed for proper function expression documentation placement.
Also provides `getJSDocComment` as a named export
brettz9
added a commit
to dstaley/eslint-plugin-jsdoc
that referenced
this issue
May 3, 2020
It seemed that auto fixing by
require-jsdoc
is incorrect.This bug add jsdoc comment to incorrect position in arrow function case.
If you would like to check, running the command in bellow with the repository is reproduction the bug.
The text was updated successfully, but these errors were encountered: