fix(eslint): preserve TypeScript core-rule replacements - #43
Conversation
📝 WalkthroughWalkthroughThe core ESLint preset now applies ChangesESLint preset precedence
Estimated code review effort: 2 (Simple) | ~10 minutes Suggested reviewers: Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
✨ Simplify code
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.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@src/eslint/core.js`:
- Line 2: Update the preset-order comment in src/eslint/base.js to list quality
before typescript, matching the order exported by the preset. Keep the
documented ignores and testing entries unchanged.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 8b57f46f-e95b-4bf3-976b-e67686166cac
📒 Files selected for processing (2)
src/eslint/core.jstest/typescript-core-rule-replacements.test.mjs
Summary
typescript-eslintkeep overlapping core rules such asno-undefandno-unused-varsdisabled for TypeScriptProblem
The shared core preset currently applies
@eslint/jsrecommended rules aftertypescript-eslint. That ordering silently turns coreno-undefandno-unused-varsback on for TypeScript files, so consumers receive duplicate or incorrect diagnostics even though the TypeScript extension rules are enabled.Validation
pnpm testpasses all 39 testspnpm run format:checkpasses.tsand.jsfilesSummary by CodeRabbit
Bug Fixes
Documentation
Tests