Conversation
📝 WalkthroughWalkthroughThe pull request consolidates type checking into the linting phase by removing the separate Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
📝 Coding Plan
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.
🧹 Nitpick comments (1)
.oxlintrc.json (1)
10-17: Track disabled type-aware rules with explicit owners/issues.Temporarily disabling these rules is reasonable for rollout, but add an explicit tracking map (rule → issue/owner/target PR) to avoid permanent drift.
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed. In @.oxlintrc.json around lines 10 - 17, Add a tracking map for the disabled type-aware rules so they don't drift: create a JSON object (e.g., "disabledRuleTracking") next to the existing rules in .oxlintrc.json that maps each disabled rule name (typescript/unbound-method, typescript/no-floating-promises, typescript/no-implied-eval, typescript/await-thenable, typescript/restrict-template-expressions, typescript/no-base-to-string, typescript/no-redundant-type-constituents, typescript/no-misused-spread) to an owner, an issue or ticket ID, and a target PR or date; ensure the mapping keys match the exact rule strings and that maintainers update the map when flipping rules back on so the information remains current.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.
Nitpick comments:
In @.oxlintrc.json:
- Around line 10-17: Add a tracking map for the disabled type-aware rules so
they don't drift: create a JSON object (e.g., "disabledRuleTracking") next to
the existing rules in .oxlintrc.json that maps each disabled rule name
(typescript/unbound-method, typescript/no-floating-promises,
typescript/no-implied-eval, typescript/await-thenable,
typescript/restrict-template-expressions, typescript/no-base-to-string,
typescript/no-redundant-type-constituents, typescript/no-misused-spread) to an
owner, an issue or ticket ID, and a target PR or date; ensure the mapping keys
match the exact rule strings and that maintainers update the map when flipping
rules back on so the information remains current.
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
Run ID: c7dbbf6b-ca43-4ea6-9240-36122d08c807
⛔ Files ignored due to path filters (1)
pnpm-lock.yamlis excluded by!**/pnpm-lock.yaml
📒 Files selected for processing (4)
.github/workflows/ci.yml.oxlintrc.jsonAGENTS.mdpackage.json
💤 Files with no reviewable changes (1)
- .github/workflows/ci.yml
|
Very cool! I will check it locally before merge In the meantime if you had time would be cool to make a codeup |
|
Yes please feel free to make an issue or directly PR i can help on that! |
This PR enables type-aware linting using oxc's type-aware capabilities, allowing the project to leverage TypeScript type information for more sophisticated static analysis.
Some type-aware rules are currently disabled to avoid breaking the existing codebase. These can be gradually re-enabled through separate PRs that:
.oxlintrc.jsonThis incremental approach allows us to improve type safety systematically without blocking this initial setup.
When I enabled this, the following rules had to be added:
typescript/unbound-methodtypescript/no-floating-promisestypescript/no-implied-evaltypescript/await-thenabletypescript/restrict-template-expressionstypescript/no-base-to-stringtypescript/no-redundant-type-constituentstypescript/no-misused-spreadAfter approving / agreeing with this change I will create separate PR's to fix these errors/warnings myself.
Documentation
See oxc Type-Aware Linting docs for more information.
Summary by CodeRabbit