-
Notifications
You must be signed in to change notification settings - Fork 35.7k
Closed
Labels
*out-of-scopePosted issue is not in scope of VS CodePosted issue is not in scope of VS Codefeature-requestRequest for new features or functionalityRequest for new features or functionalityplan-itemVS Code - planned item for upcomingVS Code - planned item for upcomingtypescriptTypescript support issuesTypescript support issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)
Milestone
Description
Problem
Support the new external files option that TS plugins can provide: microsoft/TypeScript#15308
We currently allow TSServer plugin extensions to register themselves for custom language modes. The angular extension for example could register the angular plugin with support for the ng-html language. There were a few problems with the current implementation:
- We start automatically syncing all
ng-htmlfiles with TSServer. - If the angular plugin is not active, TS treats these
ng-htmlfiles as TypeScript code
Potential Fix
On potential fix we discussed previously: add a plugin property on open requests. TypeScript would look at the plugin property and only start validating the file if has the corresponding plugin.
Dassderdie
Metadata
Metadata
Assignees
Labels
*out-of-scopePosted issue is not in scope of VS CodePosted issue is not in scope of VS Codefeature-requestRequest for new features or functionalityRequest for new features or functionalityplan-itemVS Code - planned item for upcomingVS Code - planned item for upcomingtypescriptTypescript support issuesTypescript support issuesupstreamIssue identified as 'upstream' component related (exists outside of VS Code)Issue identified as 'upstream' component related (exists outside of VS Code)