lysdexic@programming.dev to Programming@programming.devEnglish · 4 months agoRFC 7493: The I-JSON Message Formatdatatracker.ietf.orgexternal-linkmessage-square17fedilinkarrow-up130arrow-down19
arrow-up121arrow-down1external-linkRFC 7493: The I-JSON Message Formatdatatracker.ietf.orglysdexic@programming.dev to Programming@programming.devEnglish · 4 months agomessage-square17fedilink
minus-squareGTG3000@programming.devlinkfedilinkarrow-up6·4 months agoPersonally, I prefer duplicate keys to be eaten by the parser but I can see how it’d be beneficial to prevent them.
minus-squaremasterspace@lemmy.calinkfedilinkEnglisharrow-up3·edit-24 months agoI’m honestly unsure if they intend the ‘must-ignore’ policy to mean to eat duplicate keys without erroring, or just to eat keys that are unexpected based on some contract or schema…
Personally, I prefer duplicate keys to be eaten by the parser but I can see how it’d be beneficial to prevent them.
I’m honestly unsure if they intend the ‘must-ignore’ policy to mean to eat duplicate keys without erroring, or just to eat keys that are unexpected based on some contract or schema…