New "Solution Style" tsconfig.json file breaks the unused files in most Editors

[destus90]

If we have an unused service, we will run into some Typescript errors in Editors since the unused file isn't really a part of any TypeScript compilation.
VS code

Webstorm

Shall we revert the changes for tsconfig.file?

[kyliau]

Please make sure you are using the workspace version of Typescript.
Solution-style tsconfig is not supported by typescript < v3.9.
In vscode, you can select typescript version like so:

[destus90]

@kyliau
Thanks for your suggestion. However, my TypeScript version is set as a workspace version. The real problem here has been described by @alan-agius4 angular/angular#37781 (comment). I have created a repo https://github.com/destus90/angular-v10-issues. It would be nice if you could investigate it (file src/app/foo.service.ts). I found out that adding unused files into tsconfig.app.json files array solves the issue, but it would pain us to manually put all unused files into it. Any further assistance would be appreciated.

[alan-agius4]

We are aware that “unused” files safe are effected as described above.

This is because we have a strict file Inclusion policy in our tsconfig, which results in un-referenced files not being part of correct program.

We’ll be discussing this issue during our meeting this week.

[cyrilletuzi]

Hi @alan-agius4, what is the status about this issue? I just discovered it while animating an Angular training and it's a real pain. Any time you create a service, as shown in the screenshot of the initial message, there is an error telling that experimentalDecorators should be set to true.

If it was solved by just using the service somewhere, that would be confusing but quite OK. But to use it, you need to inject the service in some constructor. Before, the service would be part of the IDE suggestions so the import is done automatically, but now the service is not suggested at all so you have to do the import manually, for each service you create.

[alan-agius4]

@cyrilletuzi, we are still evaluating the best course of action to fix this.

I’ll update the issue when we have more details.

[LayZeeDK]

If it was solved by just using the service somewhere

Is this a problem in libraries where the exposed services are not used anywhere?