-
-
Notifications
You must be signed in to change notification settings - Fork 158
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
How to add Iterable type #280
Comments
How to add the |
Do you want to forbid it, recommend a new name, or what? |
I got the error: |
Assuming you have a type "eslintConfig": {
"rules": {
...
"jsdoc/no-undefined-types": ["error", {"definedTypes": ["Iterable"]}]
...
}
} The setting you have referenced would be useful in cases like where you were already calling for renaming some bad type names into a different preferred type name, the "eslintConfig": {
"rules": {
...
"jsdoc/no-undefined-types": ["error", {"preferredTypesDefined": true}]
...
},
"settings": {
"jsdoc": {
"preferredTypes": {
"BadlyNamedIterableType": "Iterable"
}
}
}
} |
That should answer it, so closing, though feel free to comment further or reopen as needed. |
Thanks 👏 |
wrt the mentioned issues with this rule: * gajus/eslint-plugin-jsdoc#559 is resolved * gajus/eslint-plugin-jsdoc#280 - this seems like we can [use this workaround](gajus/eslint-plugin-jsdoc#280 (comment)) including configuration for common builtin types here in hd-scripts
wrt the mentioned issues with this rule: * gajus/eslint-plugin-jsdoc#559 is resolved * gajus/eslint-plugin-jsdoc#280 - this seems like we can [use this workaround](gajus/eslint-plugin-jsdoc#280 (comment)) including configuration for common builtin types here in hd-scripts
My current settings is:
The text was updated successfully, but these errors were encountered: