Add oxlint Rule for no-any to Prevent Type Safety Regression in Frontend
Description
Multiple frontend files use �ny type for RPC response parsing (StatusPage, useAgreement, useAgreementEvents). No lint rule prevents new �ny usage from being introduced. Adding a lint rule prevents type safety regression.
Requirements & Context
Add @typescript-eslint/no-explicit-any rule to oxlint config. Configure as warning (not error) for migration period. Fix existing any usage.
Suggested Execution
Branch: eat/lint/no-explicit-any-rule
Implement Changes
(1) Add oxlint rule for no-explicit-any (2) Set as warning with allowlist for known needed cases (3) Document migration path (4) Track progress in issue
Test & Commit
Run oxlint, verify no-explicit-any warning is emitted on any usage.
Example Commit Message
eat(lint): add no-explicit-any rule to oxlint config to prevent type safety regression
Guidelines
- Set as warning initially to allow migration
- Document timeline for changing to error
Add oxlint Rule for no-any to Prevent Type Safety Regression in Frontend
Description
Multiple frontend files use �ny type for RPC response parsing (StatusPage, useAgreement, useAgreementEvents). No lint rule prevents new �ny usage from being introduced. Adding a lint rule prevents type safety regression.
Requirements & Context
Add @typescript-eslint/no-explicit-any rule to oxlint config. Configure as warning (not error) for migration period. Fix existing any usage.
Suggested Execution
Branch: eat/lint/no-explicit-any-rule
Implement Changes
(1) Add oxlint rule for no-explicit-any (2) Set as warning with allowlist for known needed cases (3) Document migration path (4) Track progress in issue
Test & Commit
Run oxlint, verify no-explicit-any warning is emitted on any usage.
Example Commit Message
eat(lint): add no-explicit-any rule to oxlint config to prevent type safety regression
Guidelines