Skip to content
This repository was archived by the owner on Mar 7, 2019. It is now read-only.

Commit 28a55cb

Browse files
docs: cosmetic tweaks to tutorials
1 parent eda4bd2 commit 28a55cb

File tree

3 files changed

+5
-5
lines changed

3 files changed

+5
-5
lines changed

tutorial/README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -20,11 +20,11 @@ When configuring js-coding-standards, please keep the following in mind:
2020
> 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`.
2121
2222
- Some rules are **meant** to be disabled, but only for some folders/files
23-
> 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.
23+
> 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, 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.
2424
2525
- Always consider re-configuring a rule rather than disabling it completely
2626
> 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.
2727
28-
# Example configuration files
28+
## Example configuration files
2929

3030
Some example configuration files have been prepared for you to look at / add to your project right away. Look for them in this directory!

tutorial/nodejs-eslintrc.js

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
// directory, or a subdirectory if your project consists of both node.js and browser code.
55
module.exports = {
66
extends: [
7-
'@strv/javascript/environments/nodejs/v8',
7+
'@strv/javascript/environments/nodejs/v10',
88
'@strv/javascript/environments/nodejs/optional',
99
'@strv/javascript/coding-styles/recommended',
1010
],
@@ -23,7 +23,7 @@ module.exports = {
2323
},
2424

2525
rules: {
26-
'func-names': 0,
26+
'func-names': 'off',
2727
},
2828
}],
2929
}

tutorial/react-eslintrc.js

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4,7 +4,7 @@
44
// directory, or a subdirectory if your project consists of both node.js and browser code.
55
module.exports = {
66
extends: [
7-
'@strv/javascript/environments/react/v15',
7+
'@strv/javascript/environments/react/v16',
88
'@strv/javascript/environments/react/optional',
99
'@strv/javascript/coding-styles/recommended',
1010
],

0 commit comments

Comments
 (0)