Skip to content

Commit

Permalink
Add link to linters chapter
Browse files Browse the repository at this point in the history
  • Loading branch information
sapegin committed May 1, 2024
1 parent 8130830 commit 9ab8f32
Show file tree
Hide file tree
Showing 3 changed files with 6 additions and 1 deletion.
1 change: 1 addition & 0 deletions .vscode/settings.json
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@
"longstringer",
"polizei",
"Roomba",
"sheltie",
"shortstringer",
"shortstringers",
"Tsiri",
Expand Down
4 changes: 3 additions & 1 deletion manuscript/Code_style.md
Original file line number Diff line number Diff line change
Expand Up @@ -165,7 +165,9 @@ test(() => {test2 = true})
expect(test2).toBe(true);
-->
Shorter isn’t always better. (I’m fine with `pizza?.()` though.)
Shorter isn’t always better. (I’m fine with `pizza?.()` though, sometimes.)
**Tip:** Use `curly` ESLint rule to make sure all conditions have braces. See more in the [Lint your code](#linting) chapter.
## Obsolete code styles
Expand Down
2 changes: 2 additions & 0 deletions manuscript/Linters.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,5 @@
{#linting}

## Lint your code

In this book, we talk a lot about _conventions_. For example, don’t mutate your code, and the next programmer will have less trouble understanding it, and you’ll avoid some nasty bugs. This is a convention, meaning we’re agreeing to do something but there’s no way to enforce it. Developers are still free to mutate any value accidentally or due to evil intent.
Expand Down

0 comments on commit 9ab8f32

Please sign in to comment.