Making it easy to follow best practices

Why?

Faster development

More useful code reviews

Higher quality code

Great recruiting tool!

 

Replace (some) training with doc PRs

"gitHooks": {
  "pre-commit": "cross-env PRE_COMMIT=true lint-staged"
},

package.json

module.exports = {
  '*.js': [
    'yarn lint:eslint',
    'yarn lint:prettier',
    'git add',
    'yarn test:unit:file'
  ]
}

lint-staged.config.js

Reduce friction

Enforce best practices

Custom snippets

Same advantages as generators

{
  "script": {
    "scope": "vue",
    "prefix": "script",
    "body": [
      "<script>", 
      "export default {", 
      "\t${0}", 
      "}", 
      "</script>"
    ],
    "description": "<script>"
  }
}

Can be combined with generators for automatic basic tests for components, views, utils, etc.

The 3 month rule

Thanks!

 

@chrisvfritz

 

slides.com/chrisvfritz/

best-practices-kingston

 

Questions?

Making it easy to follow best practices (Kingston)

By Chris Fritz

Making it easy to follow best practices (Kingston)

The MIT License (MIT) Copyright (c) 2018-present Chris Fritz Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions: The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

  • 370

More from Chris Fritz