Deal with the json gem’s deprecation of silently handling duplicate keys when parsing #30
Description
#27 is a workaround for the voluminous warnings issued by json 2.13.x about duplicate keys when parsing. What is the best longer term solution? Is it to add allow_duplicates to the parser options where needed to silence the warnings and allow json v3 to continue to handle duplicate keys when parsing?
Is it valid that there are duplicate keys when parsing json in the tests? Does this also happen in real world usage?