Better tsconfig.json generation

[isidorn]

The current generation of tsconfig.json is a manual and undiscoverable process inside VS Code. I suggest the following improvements:

• We should introduce a command "Create tsconfig.json", this command should try to autodetect as much as possible from the workspace, and if needed ask the user some questions via QuickPick API. This command would in the end generate tsconfig.json, similar to how VS Code tries to help with the creation of launch.json
• "Create tsconfig.json" should be contributed to the command palette and in the explorer context menu (if tsconfig.json is not present)
• if we want to market some attributes in tsconfig.json we should write them in those files even if they have a default value so users can discover them
• The commands should be contributed to the Explorer Context Menu - if tsconfig.json can not be found in the workspace.
• If there is a typescript file open, and there is no tsconfig.json in the repository we should offer the user to automatically to create a tsconfig.json. I think a notification in this case is acceptable.

Step 2: we can consider to make the Problems welcome view contributable. So we can add a button in the problems view to generate tsconfig.json if no errors have been detected in the workspace.

With these improvements I believe we will make it much easier for the users to create a new typescript workspace.

[MartinJohns]

The current generation of tsconfig.json is a manual and undiscoverable process.

https://www.typescriptlang.org/docs/handbook/compiler-options.html

[isidorn]

@MartinJohns thanks for pointing. I meant inside VS Code. There is no UI for this. I have clarified my initial comment.
Also the --init command does not take into account the current workspace content I believe. And we should make this smarter, based on what the workspace already has.