Repository navigation
Add Tools\option setting for --target and --noImplicitAny for loose files #1223
Description
as mentioned in #1066, users who want to opt out of VS project systems, need a way to specify some additional configuration options. currently you can control compile on save, module, but not target or --noImplicitAny, --declaration, --sourceMap.
Activity
johnnyreilly commentedon Dec 9, 2014
Thanks for opening this Mohamed Hegazy (@mhegazy).
I'd like to see the "TypeScript Build" project properties tab in VS expose another option which allowed the user to select between "project files" and "loose files". Something like this: (excuse the horrendous graphic - I'm no artist):
I'm aware that "loose files" aren't strictly project settings and so you could argue it's a bad fit having both on here.
I guess the alternative is continuing the current approach of splitting the loose file and project settings between the VS TypeScript options tab (below) and the project settings tab respectively. Perhaps that makes more logical sense.
Whether separated (as now) or brought together I think it'd be good if Visual Studio used some of the ideas that other IDE's with filewatchers have. Take the "Watcher Settings" of WebStorm for example:
I'm mindful of the new "command line first" ethos which appears to be coming out of ASP.Net vNext (a separate team I'm aware). I think it's generally a good idea to avoid "hiding the magic". So even if there is tooling building up the TSC compiler options (as at present) I think it would be good to present to the user what the TSC command line looks like anyway (even if only in a read-only state)
To take that a bit further, I wonder if it would be possible to allow the user to directly control the tsc arguments in Visual Studio? This would allow control to the user over how TSC was used. Not everyone would want this so maybe this would only become enabled for editing if the user opts in / checks a checkbox. There was discussion in #1232 about specific compiler flags and this could be useful if that situation arose.
I can imagine this being useful in both the "loose files" and the "project files" contexts.
Finally (and for bonus points) would it be possible to specify different TSC compilers for loose files in this way as well? I'm guess that would be analogous to the
TypeScriptToolsVersionproject option? (The fact my TypeScript 1.3 compiler is married to TypeScriptToolsVersion 1.1 makes me question this a little.)mhegazy commentedon Feb 22, 2016
Target and modules are already supported. the other ones should be supported using tsconfig.json.