Fix ESLint errors causing CI failure #1226
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CI failing with 34 ESLint errors across TypeScript strict rules and React hooks violations.
Changes
React Hooks Violations
react-hooks/refs: Removed ref forwarding inHidden.tsx(MuiHidden doesn't support refs), used existinganchorElstate inTypingFilterinstead of accessingref.currentduring renderreact-hooks/set-state-in-effect: ReplaceduseEffect+setStatepattern with derived state using nullish coalescing (userToggleValue ?? defaultValue) inChallengesSectionandLearningSectionreact-hooks/static-components: Moved component definitions (ClassIcon,SvgComponent,ResourceProgress) outside parent render functions to prevent recreation on each renderTypeScript Errors
as anywithas unknown as Typefor type assertionscondition && fn()expressions tocondition ? fn() : undefinedorif (condition) fn()to satisfy no-unused-expressionsCode Quality
finallyblock inPersistedStateProviderto eliminate duplicatesetLoading(false)callsResourceProgressWithChartPropsOriginal prompt
✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.