Merge pull request #1950 from diegotc86/patch-2
Update phrasing on "Comparison with ||"
This commit is contained in:
commit
0e1cdaad24
1 changed files with 2 additions and 2 deletions
|
@ -60,9 +60,9 @@ alert(height || 100); // 100
|
||||||
alert(height ?? 100); // 0
|
alert(height ?? 100); // 0
|
||||||
```
|
```
|
||||||
|
|
||||||
Here, `height || 100` treats zero height as unset, same as `null`, `undefined` or any other falsy value. So zero becames `100`.
|
Here, `height || 100` treats zero height as unset, same as `null`, `undefined` or any other falsy value. So the alert shows `100`.
|
||||||
|
|
||||||
The `height ?? 100` returns `100` only if `height` is exactly `null` or `undefined`. So zero remains "as is".
|
The `height ?? 100` returns `100` only if `height` is exactly `null` or `undefined`. So the alert shows the height value `0` "as is".
|
||||||
|
|
||||||
Which behavior is better depends on a particular use case. When zero height is a valid value, that we shouldn't touch, then `??` is preferrable.
|
Which behavior is better depends on a particular use case. When zero height is a valid value, that we shouldn't touch, then `??` is preferrable.
|
||||||
|
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue