chore(tsconfig) remove the version option as it has causes confusion. People expect it to be *used in a meaningful way* and we need to respect that 🌹

closes #617

Author: basarat

dist/main/tsconfig/tsconfig.js

@@ -71,7 +71,6 @@ var defaultFilesGlob = [
     "!./node_modules/**/*",
 ];
 var invisibleFilesGlob = ["./**/*.ts", "./**/*.tsx"];
-var typeScriptVersion = '1.5.0-beta';
 exports.defaults = {
     target: ts.ScriptTarget.ES5,
     module: ts.ModuleKind.CommonJS,
@@ -289,7 +288,6 @@ function createProjectRootSync(srcFile, defaultOptions) {
     if (fs.existsSync(projectFilePath))
         throw new Error(exports.errors.CREATE_PROJECT_ALREADY_EXISTS);
     var projectSpec = {};
-    projectSpec.version = typeScriptVersion;
     projectSpec.compilerOptions = tsToRawCompilerOptions(defaultOptions || exports.defaults);
     projectSpec.filesGlob = defaultFilesGlob;
     fs.writeFileSync(projectFilePath, prettyJSON(projectSpec));

docs/CHANGELOG.md

@@ -5,6 +5,9 @@ We only plan to *strictly* document the breaking changes. The rest is optional.
 # Planned
 (No breaking changes staged)
 
+# v7.0.0
+* Removed the (already ignored in any significant way) `version` option from tsconfig. [More](https://github.com/TypeStrong/atom-typescript/issues/617)
+
 # v6.0.0
 * Bring back `dts-generator` as using the other mechanism has a few gotchas that might surprise new users. We will remove this feature once [https://github.com/Microsoft/TypeScript/issues/2338] is officially supported.
 

docs/faq.md

@@ -7,13 +7,11 @@ This is probably because of us keeping `files` updated with the `filesGlob` opti
 Set `compileOnSave : false` in your tsconfig.json (https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#compileonsave).  Then you've got all the intellisense / refactoring goodness of atom-typescript but no generated JavaScript.  Why is this useful?  Well you might be using something else for your build such as [gulp-typescript](https://github.com/ivogabe/gulp-typescript) or [tsify](https://github.com/smrq/tsify).
 
 ## Which version of TypeScript does atom-typescript use?
-It uses [ntypescript](https://github.com/TypeStrong/ntypescript) which is just a build of Microsoft/Master.  This means it's the latest and greatest of the TypeScript goodness.  There is a possibility that in the future it will move to TypeScript nightlies which is something that the TypeScript team is planning.
+It uses [ntypescript](https://github.com/TypeStrong/ntypescript) which is just a build of Microsoft/Master.  This means it's the latest and greatest of the TypeScript goodness.  There is a possibility that in the future it will move to TypeScript nightlies but our current automation is working well.
 
 ## Can I use a custom TypeScript compiler?
 If it conforms the latest TypeScript services API then yes! Just set the path to `typescriptServices.js` in the package options.  
 
-However, please note that the [version](https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#version) in `tsconfig.json` does not indicate the compiler atom is using.  That's strictly an aide-mémoire - it's to remind you which version of the TypeScript this project is intended to work with.
-
 ## Can I use an alternate transpiler?
 Atom-typescript supports using Babel as an alternate ES5 transpiler in coordination with the TypeScript language service.  This may be useful if TypeScript does not yet support transpiling a certain feature correctly (for example [scope per for loop iteration with let](https://github.com/Microsoft/TypeScript/issues/3915)).
 

docs/tsconfig.md

@@ -19,7 +19,6 @@ i.e. an empty JSON file at the *root* of your project :heart: This will be suffi
 * [`compileOnSave`](https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#compileonsave) : Should AtomTS compile on save
 * [`buildOnSave`](https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#buildonsave) : Should AtomTS build on save
 * [`scripts`](https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#scripts) : Sometimes its useful to have post build scripts
-* [`version`](https://github.com/TypeStrong/atom-typescript/blob/master/docs/tsconfig.md#version) : The TypeScript version
 
 
 ## Examples
@@ -100,8 +99,5 @@ Build means *compile all files*. Useful if for some reason you are using `--out`
 }
 ```
 
-### version
-This exists simply to make it easier for the future you to know which TypeScript version was used when this project file was created. You can read more here [Microsoft/TypeScript#2113](https://github.com/Microsoft/TypeScript/issues/2133)
-
 ## Additional Notes
 FWIW [a json schema is also available](http://json.schemastore.org/tsconfig)

lib/main/tsconfig/tsconfig.ts

@@ -117,7 +117,6 @@ interface UsefulFromPackageJson {
  * This is the JSON.parse result of a tsconfig.json
  */
 interface TypeScriptProjectRawSpecification {
-    version?: string;
     compilerOptions?: CompilerOptions;
     files?: string[];                                   // optional: paths to files
     filesGlob?: string[];                               // optional: An array of 'glob / minimatch / RegExp' patterns to specify source files
@@ -211,7 +210,6 @@ var defaultFilesGlob = [
  * This is what we use when the user doens't specify a files / filesGlob
  */
 var invisibleFilesGlob = ["./**/*.ts", "./**/*.tsx"];
-var typeScriptVersion = '1.5.0-beta';
 
 export var defaults: ts.CompilerOptions = {
     target: ts.ScriptTarget.ES5,
@@ -491,7 +489,6 @@ export function createProjectRootSync(srcFile: string, defaultOptions?: ts.Compi
 
     // We need to write the raw spec
     var projectSpec: TypeScriptProjectRawSpecification = {};
-    projectSpec.version = typeScriptVersion;
     projectSpec.compilerOptions = tsToRawCompilerOptions(defaultOptions || defaults);
     projectSpec.filesGlob = defaultFilesGlob;