jfmengels/elm-review
1
1
Fork 0
mirror of https://github.com/jfmengels/elm-review.git synced 2024-12-23 17:53:35 +03:00
Code Issues Packages Projects Releases Wiki Activity

Update elm-lint-to-elm-review.md

Browse Source
This commit is contained in:
Jeroen Engels 2020-04-01 17:07:00 +02:00 committed by GitHub
parent 25daae31d9
commit a36dc9a15e
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
documentation/design/elm-lint-to-elm-review.md
View File

@ -1,5 +1,5 @@
# Why was the project renamed from elm-lint to elm-review?
"Linting"/"delinting" is etymologically something about cleaning dirty clothes. In programming terms, it's mostly about removing useless clutter and enforcing a coding style, and sometimes about simplifying the code. Since in the Elm community, we have `elm-format` to format the code, most stylistic rules that "linters" enforce are already solved. Therefore, the name "lint" doesn't match what this tool does.
"Linting"/"delinting" is etymologically something about cleaning dirty clothes. In programming terms, it's mostly about removing useless clutter and enforcing a coding style, and sometimes about simplifying the code. Since in the Elm community, we have `elm-format` to format the code, most stylistic issues that "linters" enforce are already solved. Therefore, the name "lint" doesn't match what this tool does.
Instead, this tool should be used more in order to add additional guarantees to your code or project structure, and not so much about enforcing a code style. In practice, this tool will report things that your colleagues would tell you during code reviews, so I thought it fit to rename it to `elm-review`.
Instead, this tool should be used more in order to catch problems, add additional guarantees to your code or project structure, and not so much about enforcing a code style. In practice, this tool will report things that your colleagues would tell you during code reviews, so I thought it fitting to rename it to `elm-review`.