microsoft / microsoft/typescript-analyze-trace
Consider stopping at the last getVariancesWorker frame
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 429
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
structuredTypeRelatedTo is confusing within a variance check - it would probably make more sense to just pretty-print the type being variance checked.
Contributor guide
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.
Research direction
Read the trace-handling paths for structuredTypeRelatedTo and getVariancesWorker first, then compare the current variance-check output with a generated trace. Done means variance checks stop at the last getVariancesWorker frame and present the type being checked in a clearer form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100