Code style: Charlike. Thin layer on top of the Standard JavaScript Style v9, for more readable code.
MIT License
Code style: Charlike. Thin layer on top of the Standard JavaScript Style v9, for more readable code.
(TOC generated by verb using markdown-toc)
This config extends standard v9 javascript style and just add few more rules to it, which leads to more readable code. Most of the rules here, are already suggested in the Standard repo, but they are just proposals, so they may or may not be included in the v9 or v10 version of the Standard. I just want one very stable place with all needed things included. Don't want separate CLI too, since we have ESLint CLI which works great.
Status: Locked
Most noticeable change is that we
foo[ 'bar' ]
is just too ugly - computed-property-spacing
eslint-plugin-standard
option called either
In addition we have few more rules
catch (er) {}
s() => { return { a: 1 } }
, when you can just () => ({ a: 1 })
() => { return 1 }
, when () => 1
is enoughInstall with npm
$ npm install eslint-config-charlint --save
or install using yarn
$ yarn add eslint-config-charlint
This config is designed to work with the extends
feature of eslint inside
the .eslintrc
files. You can learn more about Shareable Configs on the
official ESLint website.
Install it then add this to your .eslintrc
file:
{
"extends": "charlint"
}
Note: We omitted the eslint-config-
prefix since it is automatically assumed by ESLint.
You can override settings from the shareable config by adding them directly into your .eslintrc
file.
Pull requests and stars are always welcome. For bugs and feature requests, please create an issue. Please read the contributing guidelines for advice on opening issues, pull requests, and coding standards. If you need some help and can spent some cash, feel free to contact me at CodeMentor.io too.
In short: If you want to contribute to that project, please follow these things
npm run commit
to commit changes instead of git commit
, because it is interactive and user-friendly. It uses commitizen behind the scenes, which follows Conventional Changelog idealogy.npm run release
, which is standard-version and follows Conventional Changelog idealogy.Thanks a lot! :)
Documentation and that readme is generated using verb-generate-readme, which is a verb generator, so you need to install both of them and then run verb
command like that
$ npm install verbose/verb#dev verb-generate-readme --global && verb
Please don't edit the README directly. Any changes to the readme must be made in .verb.md.
Clone repository and run the following in that cloned directory
$ npm install && npm test
Charlike Mike Reagent
Copyright © 2016-2017, Charlike Mike Reagent. MIT
This file was generated by verb-generate-readme, v0.4.2, on February 28, 2017. Project scaffolded using charlike cli.