How about adding a config file, such as linter? about water.css HOT 3 CLOSED

I thought about this too for a while, so thanks for starting that discussion!

My thought was to go with a combination of ESLint, Stylelint and prettier (integrated through eslint-plugin-prettier and stylelint-prettier respectively) to catch mistakes (ESLint, Stylelint) and enforce common formatting guidelines (prettier).
We would integrate this through husky and lint-staged with out Git setup. This way, whenever a Contributor commits something, all the files that are selected for the commit will be linted & fixed automatically, so we can be sure that everything in the repo will adhere to our code guidelines, but contributors don't have to configure linting and the respective Editor integrations themselves (if they don't want to). They can format code they write however they want, but once they check it in, it will be formatted to match our rules.

I like prettier because it's very opinionated (so you don't have to discuss style preferences) and because it can format pretty much anything: CSS, JS, Markdown, JSON...
But only if everyone here can live with prettier's formatting rules, of course.

from water.css.

I'm on board for this. I like the idea of an opinionated default configuration that we don't customize.

Having it work with editors and during commits is a great idea and we should make sure that's supported.

I'm curious what @kognise thinks. You can propose a pull request but I'll want @kognise to approve.

from water.css.

Sounds like a great idea! Sorry for taking so long - I'll make a PR. I love Standard, but @JanSchneider1 mentioned that forcing semicolons might be more beginner friendly. I don't agree or disagree, but we should consider this.

from water.css.