Repository navigation
chore: Lint warnings cleanup - #386
Conversation
|
Cursor Agent can help with this pull request. Just |
|
Caution Review failedThe pull request is closed. ℹ️ Recent review infoConfiguration used: defaults Review profile: CHILL Plan: Pro 📒 Files selected for processing (14)
📝 WalkthroughWalkthroughThe PR removes ESLint disable comments across multiple packages, disables three lint rules in the ESLint configuration, introduces component memoization, updates React hook dependencies, refactors code formatting and CSS class ordering, and adds NODE_ENV to Turbo's global environment variables. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~22 minutes Poem
✨ Finishing Touches
🧪 Generate unit tests (beta)
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 |
Clean up lint warnings by adjusting shared ESLint preset rules and fixing specific code issues.
A large number of warnings stemmed from overly strict shared ESLint rules (
no-unused-vars,@typescript-eslint/no-unused-vars,@typescript-eslint/no-explicit-any) which have been disabled in the shared preset. Remaining actionable warnings, such asreact-hooks/exhaustive-depsand staleeslint-disablecomments, were addressed directly in the code.Summary by CodeRabbit
Release Notes
Bug Fixes
Style
Chores