-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
ci: introduce jsdoc eslint plugin (warnings only) #11681
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
Conversation
WalkthroughAdds eslint-plugin-jsdoc to the project and integrates a jsdoc plugin block into the ESLint flat config, targeting Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches
🧪 Generate unit tests
📜 Recent review detailsConfiguration used: CodeRabbit UI Review profile: CHILL Plan: Pro ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (1)
🚧 Files skipped from review as they are similar to previous changes (1)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (15)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
eslint.config.mjs(4 hunks)package.json(1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
- GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (3)
eslint.config.mjs (3)
2-2: Correct import pattern for the jsdoc plugin.The import syntax aligns with the plugin's recommended flat config pattern and matches the dependency added in package.json.
31-31: ESLint configuration property access is correct.The property access
tseslint.configs.recommendedTypeCheckedis correctly used for extending the TypeScript ESLint recommended configuration.
86-89: JSDoc plugin configuration follows recommended pattern with appropriate severity level.The configuration uses the flat config pattern as recommended by the plugin documentation. The
flat/recommended-typescriptpreset is appropriate for TypeScript projects, and starting with warnings (instead of errors) is a sensible approach for initial rollout. The comment about switching toflat/recommended-typescript-errorlater provides clear next steps.The
filespattern correctly targets only source TypeScript files (src/**/*.ts), avoiding unnecessary linting of test files, build outputs, or configuration files.
gioboa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👏
Thanks @pkuczynski
|
Thanks for the contribution! Please fix the lockfile issues (needs to be generated using |
|
Both fixed. Would you mind giving it another look? |
commit: |
gioboa
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM 👍
* ci: introduce jsdoc eslint plugin (warnings only) * fixed * fixed
Description of change
There is quite a lot of inconsistency and missing jsdoc entries. I think it's worth to add eslint plugin now, so they will surface in the PRs and get fixed when new changes are introduced.
Longer run we could also generate docosaurus documentation out of it, like for example @faker/faker-js is doing...
Here is some documentation on the available rules: https://github.com/gajus/eslint-plugin-jsdoc#rules
Pull-Request Checklist
masterbranchFixes #00000Summary by CodeRabbit