Beefy Boxes and Bandwidth Generously Provided by pair Networks
Think about Loose Coupling

Re^2: make duplicate JSON keys an error

by McA (Priest)
on Oct 24, 2013 at 12:16 UTC ( #1059444=note: print w/ replies, xml ) Need Help??

in reply to Re: make duplicate JSON keys an error
in thread make duplicate JSON keys an error

This must have been a very short idle moment... ;-)

The above json snippet gets parsed without errors. The problem is, that the resulting hash does only have one key 'op' and the value seems to be the last parsed value. So the resulting hash does have only three distinct keys. You can't see at the parsing result whether the delivered json snippet was not valid according to the mentioned RFC.

UPDATE: Looking at the documentation of the JSON module showed that the behaviour can be influenced by several variables. But non of them is targeting your problem. The possibility of incremental parsing seems also not solve your problem. So, my conclusion: Make a feature request to add a behaviour config variable disallowing multiple equal keys. Knowing that won't help you at the moment.

Best regards

Comment on Re^2: make duplicate JSON keys an error

Log In?

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://1059444]
and the web crawler heard nothing...

How do I use this? | Other CB clients
Other Users?
Others making s'mores by the fire in the courtyard of the Monastery: (7)
As of 2015-07-03 22:06 GMT
Find Nodes?
    Voting Booth?

    The top three priorities of my open tasks are (in descending order of likelihood to be worked on) ...

    Results (56 votes), past polls