Try to create minimal reproductions of new errors, possibly crashes
Maintainers usually reply within 1 day
@armanio123 is already working on this.
Since Jul 1, 2024.
Assessment
This issue has not been assessed yet.
Description
While it is helpful to have the error reporter give precise context on why TypeScript introduces an error (or what led up to its crash), it would be much easier for us if we could get a minimal repro of code to quickly understand what changed, and in the case of crashes, what's the number of commands to hit the crash.
We wouldn't necessarily want this on every run (this could take some time). @armanio123 has already mentioned maybe this can be toggled only for specific runs and done on our weekly runs.
- Dominant language
- TypeScript
- Stars
- 29
- Forks
- 14
- Avg merge
- 2h 23m
- Merged PRs (30d)
- 7
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from microsoft/typescript-error-deltas
-
Difficulty 5/5 Over a week Newbie friendliness 35/100
microsoft/typescript-error-deltas#171 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 38/100
microsoft/typescript-error-deltas#114 ·
Maintainers usually reply within 1 day
All issues in microsoft/typescript-error-deltas
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#611 ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
polka-codes/test#345 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 1-3 hours Newbie friendliness 92/100
GoogleChromeLabs/project-sesame#217 ·
Maintainers usually reply within 12 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
solana-foundation/solana-com#2202 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100