Merge pull request #3013 from Rnbsov/patch-49
⚡ placed missed break lines and remove extra
This commit is contained in:
commit
325ba6db42
1 changed files with 3 additions and 1 deletions
|
@ -64,6 +64,7 @@ let message = 'Hello';
|
|||
```
|
||||
|
||||
Some people also define multiple variables in this multiline style:
|
||||
|
||||
```js no-beautify
|
||||
let user = 'John',
|
||||
age = 25,
|
||||
|
@ -103,6 +104,7 @@ For instance, the variable `message` can be imagined as a box labeled `"message"
|
|||
We can put any value in the box.
|
||||
|
||||
We can also change it as many times as we want:
|
||||
|
||||
```js run
|
||||
let message;
|
||||
|
||||
|
@ -260,7 +262,6 @@ myBirthday = '01.01.2001'; // error, can't reassign the constant!
|
|||
|
||||
When a programmer is sure that a variable will never change, they can declare it with `const` to guarantee and clearly communicate that fact to everyone.
|
||||
|
||||
|
||||
### Uppercase constants
|
||||
|
||||
There is a widespread practice to use constants as aliases for difficult-to-remember values that are known prior to execution.
|
||||
|
@ -291,6 +292,7 @@ When should we use capitals for a constant and when should we name it normally?
|
|||
Being a "constant" just means that a variable's value never changes. But there are constants that are known prior to execution (like a hexadecimal value for red) and there are constants that are *calculated* in run-time, during the execution, but do not change after their initial assignment.
|
||||
|
||||
For instance:
|
||||
|
||||
```js
|
||||
const pageLoadTime = /* time taken by a webpage to load */;
|
||||
```
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue