nodejs/nodebestpractices
1
0
Fork 0
mirror of https://github.com/goldbergyoni/nodebestpractices.git synced 2025-10-27 02:44:28 +08:00
Code Issues Packages Projects Releases Wiki Activity

fix code sample for example 3.3

Browse Source
This commit is contained in:
muratcan
2023-07-26 20:16:56 +03:00
parent c72f74aa3e
commit 4c632f59f4
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
README.md
View File

@ -30,7 +30,6 @@ Read in a different language: [![CN](./assets/flags/CN.png)**CN**](./README.chin
- **🔖 Curious to see examples? We have a starter**: Visit [Practica.js](https://github.com/practicajs/practica), our application example and boilerplate (beta) to see some practices in action
<br/><br/>
# Welcome! 3 Things You Ought To Know First
@ -516,7 +515,8 @@ function someFunction() {
}
// Avoid
function someFunction() {
function someFunction()
{
// code block
}
```
@ -742,7 +742,7 @@ b. [Node.js testing - beyond the basics](https://github.com/testjavascript/nodej
## ![✔] 4.2 Include 3 parts in each test name
### `🌟 #new`
### `🌟 #new`
**TL;DR:** Make the test speak at the requirements level so it's self-explanatory also to QA engineers and developers who are not familiar with the code internals. State in the test name what is being tested (unit under test), under what circumstances, and what is the expected result