andre/30-seconds-of-code
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update formatting

Browse Source
This commit is contained in:
Isabelle Viktoria Maciohsek
2022-01-29 20:36:45 +02:00
parent 454c443e90
commit 703e2e2e9d
2 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
blog_posts/eslint-refactor-for-in.md
View File

@ -17,7 +17,7 @@ And here are three refactoring options to deal with it:
### Object.keys()
`Object.keys()` has the exact same behavior as a `for..in` loop, so it can be used as a drop-in replacement:
`Object.keys()` has the exact same behavior as a `for...in` loop, so it can be used as a drop-in replacement:
```js
const data = [3, 4];

4
blog_posts/javascript-sleep.md
View File

@ -9,11 +9,11 @@ firstSeen: 2020-08-04T20:08:54+03:00
lastUpdated: 2021-11-06T20:51:47+03:00
---
JavaScript does not come with a `sleep()` function out of the box. That's probably a good idea considering the environments where it runs and the trouble it could cause if used incorrectly. The closest equivalent is the `setTimeout` function, but there are other, less common ways to implement a function that will pause execution for a specified amount of time.
JavaScript does not come with a `sleep()` function out of the box. That's probably a good idea considering the environments where it runs and the trouble it could cause if used incorrectly. The closest equivalent is the `setTimeout()` function, but there are other, less common ways to implement a function that will pause execution for a specified amount of time.
### setTimeout
JavaScript's `setTimeout` sets a timer which executes some code once the timer expires. Only the code inside the `setTimeout` callback will execute after the timer expires. This can lead to nesting issues, as well as code executing out of order if you are not careful.
JavaScript's `setTimeout()` sets a timer which executes some code once the timer expires. Only the code inside the `setTimeout()` callback will execute after the timer expires. This can lead to nesting issues, as well as code executing out of order if you are not careful.
```js
const printNums = () => {