Deprecated - use "Working as Intended" or "Design Limitation" instead
This issue contains a lengthy and complete description of a particular problem, solution, or design
The issue was declined as something which matches the TypeScript vision
Write-ups on the meeting every two weeks on docs topics
Relates to the ES2017 Spec
Relates to the ES2019 Spec
Relates to another program, environment, or user action which we cannot control.
Fix merged in https://github.com/Microsoft/TSJS-lib-generator, but not ported yet
Is in active investigation
I want the type system to leverage some sort of unification-based inference
This PR should be re-reviewed and merged ASAP for the next release.
This behavior is one of several equally-correct options
This idea sits outside of the TypeScript language design constraints
Poor Paths in import(...) types.
This is a new regression just found in the last major/minor version of TypeScript.
Indicates that we'd like a compiler backed repro for this issue: https://aka.ms/ts-repros
The issue relates to the telemetry in editors
Issues related to the TypeScript language specification
An issue which adding support for may be too complex for the value it adds
There isn't something we can do with this issue
Indicates that this PR affects docs
The severity and priority of this issue do not warrant the time or complexity needed to fix it