feat(prettier): prettify on commit (#51)

Author: glebec

.editorconfig

@@ -2,7 +2,7 @@
 root = true
 
 [*]
-indent_style = tab
+indent_style = space
 indent_size = 4
 end_of_line = lf
 charset = utf-8

.eslintrc.js

@@ -1,3 +1,3 @@
-'use strict';
+'use strict'
 
-module.exports = require('./index');
+module.exports = require('./index')

.github/CONTRIBUTING.md

@@ -2,18 +2,18 @@
 
 Thank you for your interest. `eslint-config-fullstack` generally conforms to the following principles:
 
-* Configuring rules
-  * Maintain a list of every base ESLint rule & every `eslint-plugin-react` rule. This means tracking changes to those packages, which [Greenkeeper](https://greenkeeper.io/) helps with.
-    * When a new version of those deps is published, read the changelog and add / modify the relevant rules in the corresponding Greenkeeper branch. **Do not** simply merge the GK branch as-is.
-	* When simply turning rules off, set them to `0`, do not delete them
-	* Delete deprecated rules only
-    * Keep the rule summary, verbatim from the corresponding API reference, as a comment following the rule
-  * Activate rules whose pedagogical and/or stylistic value outweighs their annoyance
-    * If a rule *almost definitely* indicates broken code, set it to `2` (error)
-    * If a rule *quite possibly* flags code that could still work, set it to `1` (warning)
-* Code style
-  * This repo uses [Prettier](https://prettier.io/) and [lint-staged](https://github.com/okonet/lint-staged) to automatically maintain formatting.
-  * If you prefer, you can run Prettier yourself on the code to preview how it will be auto-formatted, using `npm run prettify` or activating an [editor plugin](https://prettier.io/docs/en/editors.html)
-* Respect [SEMVER](https://semver.org/) when publishing to npm
-  * Turning rules off will count as a minor change as nobody's code should break (in theory)
-  * Turning rules on or changing their options should count as a major change as linting may now result in nonzero exit codes where none existed before
+*   Configuring rules
+    *   Maintain a list of every base ESLint rule & every `eslint-plugin-react` rule. This means tracking changes to those packages, which [Greenkeeper](https://greenkeeper.io/) helps with.
+        *   When a new version of those deps is published, read the changelog and add / modify the relevant rules in the corresponding Greenkeeper branch. **Do not** simply merge the GK branch as-is.
+            _ When simply turning rules off, set them to `0`, do not delete them
+            _ Delete deprecated rules only
+        *   Keep the rule summary, verbatim from the corresponding API reference, as a comment following the rule
+    *   Activate rules whose pedagogical and/or stylistic value outweighs their annoyance
+        *   If a rule _almost definitely_ indicates broken code, set it to `2` (error)
+        *   If a rule _quite possibly_ flags code that could still work, set it to `1` (warning)
+*   Code style
+    *   This repo uses [Prettier](https://prettier.io/) and [lint-staged](https://github.com/okonet/lint-staged) to automatically maintain formatting.
+    *   If you prefer, you can run Prettier yourself on the code to preview how it will be auto-formatted, using `npm run prettify` or activating an [editor plugin](https://prettier.io/docs/en/editors.html)
+*   Respect [SEMVER](https://semver.org/) when publishing to npm
+    *   Turning rules off will count as a minor change as nobody's code should break (in theory)
+    *   Turning rules on or changing their options should count as a major change as linting may now result in nonzero exit codes where none existed before

.github/ISSUE_TEMPLATE.md

@@ -1,9 +1,9 @@
 For bugs, please include the following:
 
-* What is the expected behavior?
-* What is the actual behavior?
-* What steps reproduce the behavior?
+*   What is the expected behavior?
+*   What is the actual behavior?
+*   What steps reproduce the behavior?
 
 ---
 
-*Issue description here…*
+_Issue description here…_

.github/PULL_REQUEST_TEMPLATE.md

@@ -2,16 +2,16 @@
 
 Please check all that apply.
 
-- [ ] referenced any relevant issue(s)
-- [ ] Adding new rule(s)?
-  - [ ] Included rule summary verbatim from docs as a comment
-  - [ ] Placed in the right section (stylistic / node / etc.), in alphabetical order
-  - [ ] Set to `0` (off), `1` (warn), or `2` (error) as spec'd in contributing guidelines
-- [ ] Changing active rule(s) severity?
-  - [ ] Set to `1` (warn), or `2` (error) as spec'd in contributing guidelines
-- [ ] Removing rule(s)?
-  - [ ] Set to `0` if disabling, or delete _only if deprecated_
+*   [ ] referenced any relevant issue(s)
+*   [ ] Adding new rule(s)?
+    *   [ ] Included rule summary verbatim from docs as a comment
+    *   [ ] Placed in the right section (stylistic / node / etc.), in alphabetical order
+    *   [ ] Set to `0` (off), `1` (warn), or `2` (error) as spec'd in contributing guidelines
+*   [ ] Changing active rule(s) severity?
+    *   [ ] Set to `1` (warn), or `2` (error) as spec'd in contributing guidelines
+*   [ ] Removing rule(s)?
+    *   [ ] Set to `0` if disabling, or delete _only if deprecated_
 
 ---
 
-*Your PR Notes Here*
+_Your PR Notes Here_

.prettierignore

@@ -0,0 +1 @@
+package-lock.json

.prettierrc.yml

@@ -0,0 +1,9 @@
+# printWidth: 80 # 80
+# tabWidth: 4 # 2 -- redundant with .editorconfig
+# useTabs: false # false -- redundant with .editorconfig
+semi: false # true
+singleQuote: true # false
+trailingComma: all # none | es5 | all
+# bracketSpacing: true # true
+# jsxBracketSameLine: false # false
+# arrowParens: avoid # avoid | always

README.md

@@ -23,7 +23,7 @@ In your global `~/.eslintrc.json` file:
 
 ```json
 {
-  "extends": "fullstack"
+    "extends": "fullstack"
 }
 ```
 
@@ -35,37 +35,25 @@ A specific project can extend this definition by including `eslint eslint-config
 
 ```json
 {
-	"extends": "fullstack",
-	"root": true
+    "extends": "fullstack",
+    "root": true
 }
 ```
 
-### For Babel-Transpiled Projects
+### Note on Parsing
 
-This config's peer dependencies (eslint, eslint-plugin-react) enable linting relatively modern files including JSX components. If you find that the linter fails to understand some early-stage ES features, you can enable parsing using Babel instead of ESLint's default parser. Install `babel-eslint` and set the `parser` option of your config:
-
-```sh
-npm install babel-eslint --save-dev
-```
-
-```json
-{
-	"parser": "babel-eslint",
-	"extends": "fullstack",
-	"root": true
-}
-```
+This config now uses `babel-eslint` as the parser by default. This enables linting some relatively modern code which ESLint's default parser does not handle, and was necessary for this project to lint itself. You do not need to install `babel-eslint` manually as it is a dependency of this config.
 
 ## Extending
 
 Any [rules](http://eslint.org/docs/rules/) added to your global or local `.eslintrc.json` files will override the rules defined by this package. For example:
 
 ```json
 {
-  "extends": "fullstack",
-  "rules": {
-    "semi": [1, "always"]
-  }
+    "extends": "fullstack",
+    "rules": {
+        "semi": [1, "always"]
+    }
 }
 ```
 

index.js

@@ -1,4 +1,4 @@
-'use strict';
+'use strict'
 
 /**
  * Fullstack Education Group
@@ -8,27 +8,20 @@
  */
 
 module.exports = {
+    extends: ['./rules/base', './rules/react'].map(require.resolve),
 
-	extends: [
-		'./rules/base',
-		'./rules/react'
-	].map(require.resolve),
+    env: {
+        es6: true,
+        browser: true,
+        node: true,
+        mocha: true,
+        jasmine: true,
+        jquery: true,
+    },
 
-	env: {
-		es6: true,
-		browser: true,
-		node: true,
-		mocha: true,
-		jasmine: true,
-		jquery: true,
-	},
+    parser: 'babel-eslint',
 
-	parserOptions: {
-		ecmaVersion: 6
-	},
-
-	globals: {
-		angular: true
-	}
-
-};
+    globals: {
+        angular: true,
+    },
+}