Closed RedCMD closed 6 months ago
Not complaining about -.nan
and +.nan
is indeed a bug.
The lack of errors for multiple NaN
keys is because NaN !== NaN
in JavaScript, and ===
is what's used by uniqueKeys: true
, the default. If this is important to you, it's possible to use e.g. a SameValueZero implementation as the uniqueKeys
option value.
Describe the bug
+.nan
and-.nan
are parsed as.nan
To Reproduce
(Github correctly ignores
[+-].nan
, but also seems to interpret-
asseq
)Expected behaviour
[+-].nan
should be parsed as typestr
tag-resolution
yaml
:2.4.2
Additional context also no error is given when multiple keys are given with the same value of type
.nan