You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Basically if a tsconfig.json uses a include/exclude instead of files to select input, tsserver will notify any change to a ts file in or below the directory containing the tsconfig even if not matched as input.
Expected behavior:
Don't fire the event for ts files that don't belong to the tsconfig.json file.
Actual behavior:
Any file ts file change emits this event.
This issue came to light due to a recent change in VS Code 1.13.0 which always opens the triggerFile for this event, causing the tsserver to create an implicit project for it since it doesn't belong to the actual project. Due to our build system staging files in tmp/ this causes tsserver to open a lot of files with the implicit project.
The text was updated successfully, but these errors were encountered:
krisselden
changed the title
ConfigFileDiagnosticEvent fires files not selected by tsconfig
ConfigFileDiagnosticEvent fires for files not selected by tsconfig
Jun 20, 2017
TypeScript Version: 2.4.0 / nightly (2.5.0-dev.201xxxxx)
Code
Reproduction:
https://github.com/krisselden/tsserver-config-file-diag-issue
Basically if a tsconfig.json uses a include/exclude instead of files to select input, tsserver will notify any change to a ts file in or below the directory containing the tsconfig even if not matched as input.
Expected behavior:
Don't fire the event for ts files that don't belong to the tsconfig.json file.
Actual behavior:
Any file ts file change emits this event.
This issue came to light due to a recent change in VS Code 1.13.0 which always opens the triggerFile for this event, causing the tsserver to create an implicit project for it since it doesn't belong to the actual project. Due to our build system staging files in tmp/ this causes tsserver to open a lot of files with the implicit project.
microsoft/vscode@0d5c9f4
The text was updated successfully, but these errors were encountered: