@[email protected] to Programmer [email protected]English • 1 year agoShow me a better text format for serializingimgur.commessage-square56fedilinkarrow-up1133file-text
arrow-up1106external-linkShow me a better text format for serializingimgur.com@[email protected] to Programmer [email protected]English • 1 year agomessage-square56fedilinkfile-text
minus-square@[email protected]linkfedilink30•edit-21 year agoYes, but whoever decided that json can’t have trailing commas has my ire. { "a": 1, "b": 2, <-- nope } There was some other pitfall I can’t remember around missing keys and undefined, too, but I can’t remember it now.
minus-square@[email protected]linkfedilink12•1 year agoChange to Haskell formatted commas and the problem goes away :D { "a": 1 , "b": 2 , "c": [ 3 , 6 , 9 ] }
minus-square@[email protected]linkfedilink31•1 year agoWhere is the nearest fire to dump this comment in?
minus-square@[email protected]linkfedilink2•1 year agoYou can’t but some parser allow them. But those that do do not respect the standard.
minus-square@[email protected]linkfedilink1•1 year agoGood to know. Must be why I thought you could. Thanks.
Yes, but whoever decided that json can’t have trailing commas has my ire.
{ "a": 1, "b": 2, <-- nope }There was some other pitfall I can’t remember around missing keys and undefined, too, but I can’t remember it now.
Change to Haskell formatted commas and the problem goes away :D
{ "a": 1 , "b": 2 , "c": [ 3 , 6 , 9 ] }Where is the nearest fire to dump this comment in?
I’m pretty sure you can have trailing commas…
You can’t but some parser allow them. But those that do do not respect the standard.
Good to know. Must be why I thought you could. Thanks.