chore(lint): enforce zero warnings and cleanup syntax restrictions#22902
chore(lint): enforce zero warnings and cleanup syntax restrictions#22902alisa-alisa merged 5 commits intomainfrom
Conversation
|
Hi @alisa-alisa, thank you so much for your contribution to Gemini CLI! We really appreciate the time and effort you've put into this. We're making some updates to our contribution process to improve how we track and review changes. Please take a moment to review our recent discussion post: Improving Our Contribution Process & Introducing New Guidelines. Key Update: Starting January 26, 2026, the Gemini CLI project will require all pull requests to be associated with an existing issue. Any pull requests not linked to an issue by that date will be automatically closed. Thank you for your understanding and for being a part of our community! |
Summary of ChangesHello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed! This pull request focuses on a significant project-wide cleanup by systematically removing redundant Highlights
Using Gemini Code AssistThe full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips. Invoking Gemini You can request assistance from Gemini at any point by creating a comment using either
Customization To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a Limitations & Feedback Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here. Footnotes
|
There was a problem hiding this comment.
Code Review
This pull request removes a significant number of unused eslint-disable directives across multiple packages. This cleanup is intended to improve code hygiene and prevent unintended modifications by pre-commit hooks. My review of the changes confirms that they are limited to the removal of these now-obsolete linting comments. I have not identified any issues or regressions resulting from this cleanup.
Note: Security Review did not run due to the size of the PR.
|
Size Change: +138 B (0%) Total Size: 26.1 MB
ℹ️ View Unchanged
|
c1939bc to
2b854fe
Compare
| if ( | ||
| part.kind !== 'data' || | ||
| !part.data || | ||
| // eslint-disable-next-line no-restricted-syntax |
There was a problem hiding this comment.
I just added a linter rule a few days back that should be flagging these. Is there something that is causing it to not work anymore?
Here's the PR for context: #21485
gundermanc
left a comment
There was a problem hiding this comment.
Instead of deleting these, can we fix the linter rule so it's correctly flagging these issues?
|
|
2b854fe to
66f91e4
Compare
Thanks for the recommendation, we have an issue filed for this, but we need to 'get to green' first: #22948 |
chore(lint): enforce zero warnings and cleanup syntax restrictions
Summary
This PR enforces zero warnings for the project's linting process and refactors ESLint rules to ensure syntax restrictions are consistently applied across the codebase. It also synchronizes lint directives with expanded rule coverage and removes redundant overrides.
Details
package.jsonto include--max-warnings 0in thelintscript to ensure a warning-free CI/CD pipeline.typeofproperty access check, intocommonRestrictedSyntaxRules. This ensures consistent application across all configuration blocks and prevents accidental rule overwriting in specialized package settings.Related Issues
N/A
How to Validate
@google/gemini-cliand@google/gemini-cli-coreto ensure no functional regressions:Pre-Merge Checklist