From 3e7d33ad8d89a35355b7c8317851294ef71c77bc Mon Sep 17 00:00:00 2001 From: Hafez Date: Wed, 21 Aug 2019 08:58:29 +0200 Subject: [PATCH] Fix code style practices absolute link --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 3e65e020..ffe776d5 100644 --- a/README.md +++ b/README.md @@ -465,7 +465,7 @@ All statements above will return false if used with `===` ## ![✔] 4.4 Detect code issues with a linter -**TL;DR:** Use a code linter to check basic quality and detect anti-patterns early. Run it before any test and add it as a pre-commit git-hook to minimize the time needed to review and correct any issue. Also check [Section 3](https://github.com/i0natan/nodebestpractices#3-code-style-practices) on Code Style Practices +**TL;DR:** Use a code linter to check basic quality and detect anti-patterns early. Run it before any test and add it as a pre-commit git-hook to minimize the time needed to review and correct any issue. Also check [Section 3](#3-code-style-practices) on Code Style Practices **Otherwise:** You may let pass some anti-pattern and possible vulnerable code to your production environment.