3 ms·
Does it suffer from the Norway problem?
by pwdisswordfish9 5y ago
Does it suffer from the Norway problem?
- 0xbadcafebee 5y agoI think you're thinking of YAML; JSON doesn't interpret "no" as a boolean. Scroll down here to see the JSON grammar: https://www.crockford.com/mckeeman.html https://www.crockford.com/mckeeman.html I actually think the "Norway problem" is a PEBKAC from users not learning the data format. But this tool may confuse some people or applications who don't know what a boolean, integer, float or string are, and try to mix types when the program reading them wasn't designed to. Probably the issue will come up whenever people mix different kinds of versions ("1", "1.1", "1.1.1" should be parsed as an int, float, and string, respectively)
- motoboi 5y agojo a=12 Should “a” be number or a string in the resulting JSON? And if it’s number, how can I tell it to output a string?
- halostatue 5y agoIt does not. jo -- -b foo=no -s a=12 q=[1,2,3] {"foo":true,"a":"12","q":[1,2,3]}