TypeScript May 2017 UX Issue Prioritization #25842
Labels
feature-request
Request for new features or functionality
typescript
Typescript support issues
upstream
Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Tracks upstream TypeScript issues that are either commonly reported or could significantly improve the JS/TS experience in VSCode. The initial list tracks issues that we would like to look into for May. This is not a commitment that these issues will be fixed in May or even in TS 2.4. Some of these items are also investigations.
Issues
Somewhat ordered by priority
Use correct quote style for
add missing import
quick fix make the quote symbol configurable for import codefix TypeScript#13270IntelliSense for inherited properties: Populate inheritied properties and methods in completion list inside a class TypeScript#7158
Improve IntelliSense for imports Import aliases have poor quick-info descriptions TypeScript#5515, Typescript doc visible for aliased imports, but not for single ones. TypeScript#11099
Correct error location for config file diagnostics - TSServer: config file diagnostics are missing start / end property TypeScript#10384
Go to implementation for JS implementations (investigation) - Enable Go to Implementation in Typescript Editors TypeScript#6209
Active PRs
https://github.com/Microsoft/TypeScript/pull/13921/files
// cc @kieferrm
The text was updated successfully, but these errors were encountered: