Configure ESLint no-unused-vars
rule and clean up unused code
#2613
+13
−421
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.
Why is this change needed?
The codebase had accumulated unused variables, imports, and functions that were not being detected by our existing tooling. While we use knip for detecting unused exports, it doesn't catch unused variables and imports within files. This change addresses that gap by:
Changes
ESLint Configuration
@typescript-eslint/no-unused-vars
rule to base ESLint configurationSchema$
pattern to support valibot/zod type inference variablesCode Cleanup
agentType
in Chat.tsxTimelineItemEntry
,v
,TablesInsert
,ErrorInfo
timelineUtils.ts
by removing 400+ lines of unused functions and constantsBenefits
Test plan
🤖 Generated with Claude Code