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
Defining a property or param named is should be allowed.
is
When defining a param or property named is, the linter reports an error for the rule jsdoc/valid-types.
jsdoc/valid-types
{ "env": { "es2021": true }, "extends": [ "eslint:recommended" ], "plugins": [ "jsdoc" ], "parserOptions": { "sourceType": "module", "ecmaVersion": "latest" }, "rules": { "jsdoc/valid-types": 2 } }
/** * @param {string} is * @param {string} foo * * @returns {string} */ export default function (is, foo) { return is + foo; }
I've also created a project that reproduces the issue on codesandbox.io:
https://codesandbox.io/p/devbox/festive-sun-g23dhw-y3vs47
eslint-plugin-jsdoc
The text was updated successfully, but these errors were encountered:
fix(valid-types): whitelist pratt parser keywords; fixes gajus#1221
valid-types
001900e
fix(valid-types): whitelist pratt parser keywords; fixes #1221
ab5624b
🎉 This issue has been resolved in version 48.2.3 🎉
The release is available on:
Your semantic-release bot 📦🚀
Sorry, something went wrong.
The fix in #1222 doesn't handle nested use of the keyword. For that, one has to escape with quotation marks.
Successfully merging a pull request may close this issue.
Expected behavior
Defining a property or param named
is
should be allowed.Actual behavior
When defining a param or property named
is
, the linter reports an error for the rulejsdoc/valid-types
.ESLint Config
ESLint sample
I've also created a project that reproduces the issue on codesandbox.io:
https://codesandbox.io/p/devbox/festive-sun-g23dhw-y3vs47
Environment
eslint-plugin-jsdoc
version: 48.2.2The text was updated successfully, but these errors were encountered: