@@ -36,13 +36,13 @@ console.log(typeof value.amount); // => bigint
3636console .log (typeof value .debt , isNaN (value .debt )); // => number true
3737```
3838## Motivation
39- JSON format is good enough for everyday usage. There is some libraries trying to introduce syntax to make JSON closer
40- to modern JavaScript, some libraries trying to introduce functions serialization. All that is not important and do not
41- required for everyday usage. However, there is one thing annoing me always - date values.
39+ JSON format is good enough for everyday usage. There are some libraries trying to introduce syntax to make JSON closer
40+ to modern JavaScript, some libraries trying to introduce functions serialization. All that is not important and is not
41+ required for everyday usage. However, there is one thing annoying me always - date values.
4242
4343We are serializing dates a lot and each time we parse it back we are getting a string. As a result we have to deal with
4444the Date constructor manually each time. Even if we are no need date as an object, date formatter will have to make date
45- object in order to make user friendly text representation. Otherwords we are forced to care about dates additionally.
45+ object in order to make user- friendly text representation. Otherwords we are forced to care about dates additionally.
4646It produces bulky solutions or tons of inline type conversions.
4747
4848But I'm lazy developer, I'll do everything to get rid of any additional careness.
@@ -70,7 +70,7 @@ interface Json22StringifyOptions {
7070
7171### Numbers
7272
73- With JSON22 you can use ` NaN ` , ` Infinity ` , ` -Infinity ` values. It mean also this values will be stringified well
73+ With JSON22 you can use ` NaN ` , ` Infinity ` , ` -Infinity ` values. It means also this values will be stringified well
7474in case it nested at an array or an object.
7575``` javascript
7676JSON .stringify ([42 , NaN , Infinity , - Infinity ]); // => [42, null, null, null]
0 commit comments