microsoft / microsoft/TypeScript
Provide a better display experience for unresolved values and types
Aperta
@sheetalkamat ci sta già lavorando.
Dal 24/6/2020.
In Discussion
Rescheduled
Suggestion
- Lingua principale
- Go
- Stelle
- 111k
- Fork
- 14.3k
- Merge medio
- 2g 4h
- PR unite (30g)
- 132
Descrizione
Today, an unresolved type, or the type of an unresolved variable will look something like any. Internally, these resolve to a well-known error type that semantically acts as any.
However, in https://github.com/microsoft/TypeScript/issues/37713, we may not have a full picture of the world because we're limited to a single file.
I think we should consider doing two things
- In the syntactic mode, the type of any unresolved symbol should be of a new
any-like type calledloading. - anywhere else, usage of an unresolved type should "stick around" and be recognized as a type reference to an extremely permissive type. This could be implemented through something similar to https://github.com/microsoft/TypeScript/issues/38836
According to @CyrusNajmabadi, Roslyn already does something really similar to this.
Guida per i contributori
Apri la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Valutazione
Questa issue non è ancora stata valutata.