microsoft / microsoft/TypeScript
Attempt to more-frequently use local aliases when printing out types
Open
Nobody has claimed this yet.
Domain: LS: Type Display
Needs Proposal
Suggestion
- Dominant language
- Go
- Stars
- 111k
- Forks
- 14.3k
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 132
Description
When a user imports a type alias like
// ./a.ts
export type Foo = number | string | symbol;
We should try to print out Foo in error messages like in
// ./b.ts
import { Foo } from "./a.js"
let x: Foo = true;
and in declaration emit like in
// ./c.ts
import { Foo } from "./a.js"
function f(x: Foo) {
return x;
}
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
Reproduce the examples in a.ts, b.ts, and c.ts, checking both the error message and declaration emit behavior. Trace the compiler's type-printing and declaration-emit entry points; done means imported local aliases such as Foo are used where appropriate in both outputs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100