Description
Is your feature request related to a problem? Please describe.
🚀 feature request
Description
Currently the VS Code plugin doesn't seem to take into account the tsconfig.lib.json file for a library.
I'm working on an Angular workspace that contains libraries and applications. The plugin seems to be "using" only the workspace's tsconfig.json file.
For example, if I add "useDefineForClassFields": false in tsconfig.lib.json for a library, that library builds correctly, but while editing files VS Code underlines some stuff as errors:
If I move that "useDefineForClassFields": false to the tsconfig.json file for the whole workspace that error disappears (and the library still builds the same).
In this workspace we have several libraries: some are older code we are updating; some are templates we are bundling for our reuse. We have a few of these settings that we apply specifically to one library or another (e.g. "paths"), and that we don't want to apply at workspace level. Again, the libraries build correctly, but having the editor report errors differently from the compiler is a big pain, especially for our junior developers.
Feature Type
This is a user-experience bug, for the most part.
- Angular Language Service VSCode extension
- Angular Language Service server
Describe the solution you'd like
I guess, since the tsconfig.lib.json contains information on the json file it extends, I would like the VS Code plugin to be loading and merging the files, just like invoking ng build does, so that we'd have correct "intellisense" and highlighting.