Feature-Request: Support specifying alternative tsconfig.json in workspace settings

[fuminchao]

In our project, we have two tsconfig.json, one for development, one for production.
If we can specify which tsconfig.json to use in the workspace, that would be great

[unional]

Current workaround is to use extends:

// tsconfig.json
{
  // Assuming this is your dev setting and want to use it for workspace.
  "extends": "tsconfig.dev.json"
}

[waderyan]

@mhegazy I think we've seen this before... I've searched the TS repo and can't find a duplicate. Is this request familiar to you?

[mhegazy]

There is reference to it in microsoft/TypeScript#11827 and in microsoft/TypeScript#11224. The change would need to be done on the VSCode side as well. you need a gesture to let the user tell you which tsconfig.json to use when opening a folder. we have today an open command for these sorts of cases with OpenExternalProject. we might need to add some other options to make VSCode scenario simpler, but you will need to drive this design proposal.

in general, we believe simplifying the configuration story is better in the long run. Confgurtion inheritance, as noted by @unional erlier, would be the recommended course of action here.

[fuminchao]

hi all,
Could we just add a configuration like "typescript.tsconfig=xxxxx" in workspace-settings or user-settings?

[mjbvz]

I believe this is a duplicate of #12463