-
-
Notifications
You must be signed in to change notification settings - Fork 164
[Regression] jsdoc/no-undefined-types warning for module:stream.Readable #747
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
Comments
Thanks for reporting this! This should be fixed in jsdoc-type-pratt-parser/jsdoc-type-pratt-parser#60. |
Thanks for the fast response and fix @simonseyock! Much appreciated. I can confirm that I noticed a couple other potential issues. Would you prefer if I open them in this repo or simonseyock/jsdoc-type-pratt-parser? (Or as comments on this issue?) |
Feel free to report them on simonseyock/jsdoc-type-pratt-parser |
@kevinoid , if these are not very obscure issues (like the non-allowance of underscores as was just fixed in the parser), feel free to also file here so others can see here that it is being worked on and so that we can track our updating of the parser once it may include a fix/enhancement. |
🎉 This issue has been resolved in version 35.1.3 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Expected behavior
jsdoc/no-undefined-types
does not warn formodule:stream.Readable
.Actual behavior
ESLint Config
ESLint sample
Environment
eslint-plugin-jsdoc
version: v35.1.1 or v35.1.0Additional Info
The issue does not occur with
[email protected]
or earlier. I bisected the regression to e9f6a0a from #736.I'm still not entirely clear on what types JSDoc accepts. My apologies in advance if
module:stream.Readable
is not a valid type.Thanks,
Kevin
The text was updated successfully, but these errors were encountered: