Conversation
|
There was a problem hiding this comment.
Pull request overview
This PR adds a new Claude AI assistant command file that provides instructions for fixing TypeScript type errors in the project. The command file establishes a systematic workflow for identifying and resolving type errors using the project's existing type-checking and linting scripts.
Key changes:
- Added
.claude/commands/fix-types.mdwith a 4-step workflow for fixing TypeScript type errors
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| Steps: | ||
|
|
||
| 1. Run `pnpm run check-types:src` or `pnpm run check-types:src paths/to/files` to identify type errors |
There was a problem hiding this comment.
The command pnpm run check-types:src paths/to/files will not work as intended. The check-types:src script runs tsc --noEmit && tsc-strict, and TypeScript's compiler with the --noEmit flag does not accept file paths as command-line arguments in this way - it uses the configuration from tsconfig.json. Consider removing the path-specific command suggestion or documenting an alternative approach for checking specific files.
| 1. Run `pnpm run check-types:src` or `pnpm run check-types:src paths/to/files` to identify type errors | |
| 1. Run `pnpm run check-types:src` to identify type errors across the entire project. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #6215 +/- ##
========================================
Coverage 40.36% 40.36%
========================================
Files 2428 2428
Lines 40528 40528
Branches 8975 9309 +334
========================================
Hits 16360 16360
Misses 24140 24140
Partials 28 28 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
witoszekdev
left a comment
There was a problem hiding this comment.
I would suggest making it really obvious because Claude often just does as any or as unknown as ... and calls it a day 😆
|
|
||
| Steps: | ||
|
|
||
| 1. Run `pnpm run check-types:src` or `pnpm run check-types:src paths/to/files` to identify type errors |
There was a problem hiding this comment.
| 1. Run `pnpm run check-types:src` or `pnpm run check-types:src paths/to/files` to identify type errors | |
| 1. Run `pnpm run check-types:src` to check entire project or `pnpm run check-types:src paths/to/files` for specific file to identify type errors |
| Steps: | ||
|
|
||
| 1. Run `pnpm run check-types:src` or `pnpm run check-types:src paths/to/files` to identify type errors | ||
| 2. Analyze the errors and fix them systematically |
There was a problem hiding this comment.
| 2. Analyze the errors and fix them systematically | |
| 2. Analyze the errors and fix them systematically, DO NOT use `as any` |
No description provided.