-
Notifications
You must be signed in to change notification settings - Fork 2
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
p.kabir
committed
May 20, 2019
1 parent
5cc0374
commit 3d96b8c
Showing
3 changed files
with
523 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,2 +1,19 @@ | ||
# eslint-config-clean-code | ||
|
||
Linter rules for clean and fast TypeScript development | ||
|
||
# Why? | ||
|
||
Because every TypeScript developer deserves not to think about code style and minor approaches. | ||
|
||
# Installation | ||
|
||
1. `npm install --save-dev eslint-config-clean-code` | ||
1. In your `.eslintrc` file at the project root, add `extends: eslint-config-clean-code`. | ||
1. Customise the rules as required. | ||
|
||
# Choices | ||
|
||
## Single automatic code formatting | ||
|
||
We consciously disable rules related to whitespace, indents, etc. and recommend using [`Prettier`](https://prettier.io/docs/en/install.html) instead, as a complementary tool to your linter. Having wasted numerous workdays bickering about minor formatting issues, this is the only sane choice for all projects, in our opinion. |
Oops, something went wrong.