Writing code is hard. It is however much harder to write code that conforms to standards that are already in the project. Fortunately for us there is ESLint with all the bells and whistles that help in that tedious task. And believe it or not there are ready-made presets and plugins that make the configuration really simple.
Installation
First, as usual, we need some packages added to our project:
$ npm install --save-dev eslint poi-preset-eslint eslint-plugin-vue babel-eslint
Then create or update your existing poi.config.js
with as follows:
module.exports = {
presets: [
require('poi-preset-eslint')({ mode: '*' }),
]
}
Configuration
All that is left is to configure ESLint. I prefer to have a set of rules that don't get in the way while developing but hold the forth when building final version. That is why some of my settings are environment-dependant:
// This defines the mode of operation for checks depending on the environment
const mode = process.env.NODE_ENV === 'production' ? 'error' : 'warn'
module.exports = {
parserOptions: {
'parser': 'babel-eslint',
'sourceType': 'module'
},
extends: [ 'eslint:recommended', 'plugin:vue/recommended' ],
rules: {
'camelcase': [ 'error', { 'properties': 'always' } ],
'func-name-matching': 'error',
'func-names': [ 'error', 'never' ],
'object-shorthand': [ 'error', 'always' ],
'prefer-const': 'error',
'prefer-template': 'error',
'template-curly-spacing': [ 'error', 'never' ],
'no-useless-rename': 'error',
'no-useless-constructor': 'error',
'arrow-spacing': [ 'error', {
'before': true,
'after': true,
} ],
'arrow-parens': [ 'error', 'as-needed' ],
'arrow-body-style': [ 'error', 'as-needed' ],
'no-const-assign': 'error',
'prefer-numeric-literals': 'error',
'indent': [ 'error', 2, {
'SwitchCase': 1,
} ],
'semi': [ 'error', 'never' ],
'quotes': [ 'error', 'single' ],
'comma-dangle': [ 'error', 'always-multiline' ],
'no-console': mode,
'no-debugger': mode,
'no-alert': mode,
'no-var': 'error',
'one-var': [ 'error', 'never' ],
'space-before-function-paren': [ 'error', {
'anonymous': 'never',
'named': 'always',
'asyncArrow': 'always',
}],
'object-curly-spacing': [ 'error', 'always' ],
'array-bracket-spacing': [ 'error', 'always' ],
'computed-property-spacing': [ 'error', 'never' ],
'key-spacing': [ 'error', {
'beforeColon': false,
'afterColon': true,
} ],
'keyword-spacing': 'error',
'space-infix-ops': 'error',
'space-unary-ops': 'error',
'space-in-parens': [ 'error', 'never' ],
'comma-spacing': [ 'error', { 'before': false, 'after': true } ],
'no-whitespace-before-property': 'error',
'no-multi-spaces': 'error',
'no-multiple-empty-lines': [ 'error', { 'max': 1 } ],
'dot-location': [ 'error', 'property' ],
'getter-return': 'error',
'consistent-return': [ 'error', { 'treatUndefinedAsUnspecified': true } ],
'valid-jsdoc': 'error',
'eqeqeq': 'error',
'no-return-assign': [ 'error', 'always' ],
'vue/max-attributes-per-line': [ 'error', {
singleline: 5,
multiline: { max: 5, 'allowFirstLine': true },
} ],
'vue/html-indent': [ 'none' ],
'vue/attribute-hyphenation': [ 'error', 'never' ],
},
}
As for the rules (and remember this is a personal preference), I don't like the fact of being forced to write every single attribute for a component in a separate line. I think this looks awful. Sure, if there are more than X attributes then it should be in a separate line. That's why the number is so high (5). Also, I found that the hyphenation of attributes that are bound, like :selection-mode
causes compilation errors so this one is (at least currently) broken.
Practice
A hint for transitioning projects from non-eslint to eslint: when you'll start with the project there will be a massive number of violations. I mean like hundrets of them. Before you commit to fixing them all consider selectively disabling ESLint in all files by means of the following directive:
/* eslint-disable */
Then, when you will get the time remove that directive from 1 file and fix warnings. Then move to the next until ESLint is enabled in all the files. That will make the job much more approachable!
And that is it! Of course you can add or change more rules as you see fit. Whatever works for you.
Happy coding!
No comments:
Post a Comment