Skip to content

fix: resolve no-explicit-any lint errors breaking CI#84

Merged
Empreiteiro merged 1 commit intomainfrom
claude/intelligent-blackwell
Mar 19, 2026
Merged

fix: resolve no-explicit-any lint errors breaking CI#84
Empreiteiro merged 1 commit intomainfrom
claude/intelligent-blackwell

Conversation

@Empreiteiro
Copy link
Copy Markdown
Owner

Summary

  • Widen createSource type parameter from restrictive union literal to string, eliminating the need for as any casts when adding new source types
  • Remove all as any type casts in 8 source form components (HubSpot, Jira, S3, MongoDB, Notion, Snowflake, Excel Online, REST API)
  • Replace error: any catch blocks with proper error instanceof Error handling
  • Replace (s: any) array callbacks with explicit { id: string; type: string } types
  • Replace any[] with Record<string, unknown>[] in RestApiSourceForm

Test plan

  • npm run lint passes with 0 errors (60 warnings, all pre-existing)
  • npm run typecheck passes
  • Frontend dev server starts without console errors
  • CI pipeline should now pass on this branch

🤖 Generated with Claude Code

Widen createSource type parameter from restrictive union to string,
remove unnecessary `as any` casts in source forms, replace `error: any`
with proper unknown error handling, and type array callbacks explicitly.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@Empreiteiro Empreiteiro merged commit cda15b1 into main Mar 19, 2026
1 of 4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant