Update tutorials

Author: robertrossmann

tutorial/README.md

@@ -3,23 +3,24 @@
 When configuring js-coding-standards, please keep the following in mind:
 
 - Prefer _.eslintrc.js_ format over YAML/JSON
-  > JSON cannot contain comments or other simple code, and YAML requires custom parser. Using standard node.js module format speeds the whole process up.
+  > JSON cannot contain comments or other simple code, and YAML requires custom parser. Using standard node.js module format speeds the whole linting process up.
 
 - Always extend only from **one environment configuration** per _.eslintrc.js_
-  > Some environments have conflicting configurations - you **will** experience weird issues if you include ie. both nodejs and react environments into a single _.eslintrc.js_ file.
-  > If your project consists of both React and node.js code, put them into separate folders and create _.eslintrc.js_ file for each of those folders.
+  > Some environment configuration files in this ruleset have conflicting rule configurations - you **will** experience weird issues if you include ie. both nodejs and react environments into a single _.eslintrc.js_ file.
+  >
+  > If your project consists of both React and Node.js code, put them into separate folders and create _.eslintrc.js_ file for each of those folders.
 
 - Do not include extensions when extending
   > You should not include the file extension in your `extends:` properties - the format in which this ruleset is written should be an implementation detail for ESLint to figure out.
   >
-  > - Good: `@strv/javascript/environments/nodejs/v6`
-  > - Bad: `@strv/javascript/environments/nodejs/v6.js`
+  > - Good: `@strv/javascript/environments/nodejs/v8`
+  > - Bad: `@strv/javascript/environments/nodejs/v8.js`
 
 - Extend from the `optional` rulesets after you extend from the main, version-specific environment ruleset
-  > In other words, if you decide to include ie. `@strv/javascript/environments/nodejs/optional`, include it **after** you have included `@strv/javascript/environments/nodejs/v6`.
+  > In other words, if you decide to include ie. `@strv/javascript/environments/nodejs/optional`, include it **after** you have included `@strv/javascript/environments/nodejs/v8`.
 
 - Some rules are **meant** to be disabled, but only for some folders/files
-  > For example, the rule `no-process-env` is enabled by default because accessing any property on `process.env` object causes an expensive C-level function call. However, using `process.env` is the recommended way to manage application configuration. Therefore, it is OK to turn this rule off for a single folder/file where you gather all the required configuration options from `process.env` and export them in a module. The rest of your application no longer needs to access `process.env` directly and instead reads the configuration from the module.
+  > For example, the rule `no-process-env` is enabled by default because accessing any any property on `process.env` object causes an expensive C-level function call. However, using `process.env` is the recommended way to manage application configuration. Therefore, some configuration files disable this rule for all files located in a directory named _config_ or _configuration_. Here, you gather all the required configuration options from `process.env` and export them in a module. The rest of your application no longer needs to access `process.env` directly and instead reads the configuration from that module.
 
 - Always consider re-configuring a rule rather than disabling it completely
   > If a rule does not quite fit your exiting codebase and fixing the issues would take considerable amount of time/energy, please consider first if the rule could be re-configured to suit your project's current style, rather than disabling it right away.

tutorial/editor-integrations.md

@@ -1,3 +1,14 @@
+[atom-linter]: https://atom.io/packages/linter
+[atom-linter-eslint]: https://atom.io/packages/linter-eslint
+[vscode-eslint]: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
+[subl-packagecontrol]: https://packagecontrol.io
+[subl-linter]: https://packagecontrol.io/packages/SublimeLinter
+[subl-linter-eslint]: https://packagecontrol.io/packages/SublimeLinter-contrib-eslint
+[subl-eslint-formatter]: https://packagecontrol.io/packages/ESLint-Formatter
+[webstorm-eslint]: https://www.jetbrains.com/help/webstorm/2016.3/using-javascript-code-quality-tools.html#ESLint
+[webstorm-eslint-autofix]: https://blog.jetbrains.com/webstorm/2016/09/webstorm-2016-3-eap-163-3983
+
+
 # ESLint integrations with your IDE/editors
 
 To make the whole developer experience more pleasant and convenient, it is important to configure your code editor of choice integrate with ESLint. The following can be achieved with most editors:
@@ -73,23 +84,14 @@ WebStorm has built-in support for ESLint issue reporting. Auto fixing is only su
 To enable ESLint reporter, [follow the guide][webstorm-eslint] on WebStorm's support page.
 To use the new autofix feature, [read their blog post][webstorm-eslint-autofix] on the topic.
 
-To use autofix on save feature
-1. Go to `Preferences` -> `Tools` -> `File watchers`
-2. Click to add (plus) button and choose custom template
-3. Name it for example `eslint`
-4. File type `javascript`
-5. Program will be your path to eslint binary for example `/Users/[yourusername]/git/[yourproject]/node_modules/.bin/eslint`
-6. Arguments `--fix $FilePath$`
-7. Working directory `$ProjectFileDir$`
-8. Show console `never` (if you don't want to see console when --fix command find eslint errors)
-9. Check `Trigger watcher regardless of syntax errors` and uncheck `Immediate file synchronization`
+To use autofix on save feature:
 
-[atom-linter]: https://atom.io/packages/linter
-[atom-linter-eslint]: https://atom.io/packages/linter-eslint
-[vscode-eslint]: https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint
-[subl-packagecontrol]: https://packagecontrol.io
-[subl-linter]: https://packagecontrol.io/packages/SublimeLinter
-[subl-linter-eslint]: https://packagecontrol.io/packages/SublimeLinter-contrib-eslint
-[subl-eslint-formatter]: https://packagecontrol.io/packages/ESLint-Formatter
-[webstorm-eslint]: https://www.jetbrains.com/help/webstorm/2016.3/using-javascript-code-quality-tools.html#ESLint
-[webstorm-eslint-autofix]: https://blog.jetbrains.com/webstorm/2016/09/webstorm-2016-3-eap-163-3983
+1. Go to `Preferences` -> `Tools` -> `File watchers`
+1. Click the `Add` (+) button and choose custom template
+1. Name it for example `eslint`
+1. Set file type to `javascript`
+1. Program will be your path to eslint binary for example `/Users/[yourusername]/git/[yourproject]/node_modules/.bin/eslint`
+1. Arguments `--fix $FilePath$`
+1. Working directory `$ProjectFileDir$`
+1. Show console `never` (if you don't want to see the console when `--fix` command finds errors)
+1. Check `Trigger watcher regardless of syntax errors` and uncheck `Immediate file synchronization`

tutorial/mocha-eslintrc.js

@@ -4,8 +4,26 @@
 // directory, or a subdirectory if your project consists of both node.js and browser code.
 module.exports = {
   extends: [
-    '@strv/javascript/environments/nodejs/v6',
+    '@strv/javascript/environments/nodejs/v8',
     '@strv/javascript/environments/nodejs/optional',
     '@strv/javascript/coding-styles/recommended',
   ],
+
+  // As of ESLint 4.1, you no longer need to use separate, per-directory .eslintrc.js files and
+  // instead control per-folder overrides from your central .eslintrc.js file using the overrides
+  // array.
+  // See the original blog post on the feature:
+  // https://eslint.org/blog/2017/06/eslint-v4.1.0-released
+  overrides: [{
+    files: [
+      'test/**',
+    ],
+    env: {
+      mocha: true,
+    },
+
+    rules: {
+      'func-names': 0,
+    },
+  }],
 }