We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Using the optional chaining proposal leads eslint-plugin-jsdoc to think that the constant being annotated is a function, while it’s not:
eslint-plugin-jsdoc
/** @const {boolean} test */ const test = something?.find(_ => _)
gives the following warnings:
jsdoc/require-description
jsdoc/require-param
jsdoc/require-returns
while this passes without warnings:
/** @const {boolean} test */ const test = something.find(_ => _)
The text was updated successfully, but these errors were encountered:
This is blocked by #189 . The function getJSDocComment that causes the false positive is in eslint core.
getJSDocComment
Sorry, something went wrong.
#189 is no longer blocking as it has been merged; feel free to take up the issue if you like...
🎉 This issue has been resolved in version 7.2.3 🎉
The release is available on:
Your semantic-release bot 📦🚀
Successfully merging a pull request may close this issue.
Using the optional chaining proposal leads
eslint-plugin-jsdoc
to think that the constant being annotated is a function, while it’s not:gives the following warnings:
jsdoc/require-description
)jsdoc/require-param
)jsdoc/require-returns
)while this passes without warnings:
The text was updated successfully, but these errors were encountered: