3 ms·
From the docs: > When you omit quotes the string ends at the newline. > Preceding and trailing whitespace is ignored as are escapes. > > A value that i
by PuerkitoBio 10y ago
From the docs:
> When you omit quotes the string ends at the newline.
> Preceding and trailing whitespace is ignored as are escapes.
>
> A value that is a number, true, false or null in JSON is
> parsed as a value. E.g. 3 is a valid number while 3 times is
> a string.
(edit: formatting)
- lumpypua 10y agoRight but the point is that you had to consult the docs. It's a problem of ambiguity on the part of the format.
- chris-at 10y agoOf course you have to get the information from somewhere the first time you learn something. What's the problem with that?
- dandelany 10y agoThe problem is that this is supposed to be a more-easily-readable form of JSON, but it requires consulting the docs to understand the meaning of something which is completely unambiguous in regular JSON.
- ssalazar 10y ago> Of course you have to get the information from somewhere the first time you learn something. What's the problem with that? The first time, and the second time if you haven't looked at it in a month, and a third time a month after that. And so on.
- PuerkitoBio 10y agoIt is ambiguous only if you think it can be a completely useless format. If you decide to use it, chances are you considered it useful, and the only useful way this can parse is as a number, otherwise it would't be able to represent numbers, booleans and null. I'd say it parses pretty much as expected, and as such, contrary to other comments, you don't have to go back to the docs every so often.
- bobbyi_settv 10y agoSo if you put "true" (without quotes) as a value, you get a boolean, but if you put "True", you get a string?
- cortesoft 10y agoSo would that be "4," that you end up with, then?