Jira (PUP-5744) Remove non-JSON safe default_literal objects from classes_per_environment response

[Henrik Lindberg (JIRA)]

Title: Message Title

Henrik Lindberg commented on PUP-5744   Re: Remove non-JSON safe default_literal objects from classes_per_environment response Jeremy Barlow What should we do about hashes? In JSON tthe keys must be strings (since JSON hashes are supposed to represent objects, not actual programming language hash maps). In Ruby, when a Ruby Hash is turned into JSON it stringifies all keys. Therefore, the Puppet Hash: { 1=>100, 42 => 200} is changed to JSON hash: { "1": 100, "42": 200 } Stringification takes place for all non String keys including arrays and hashes. So, in this API, when there is a Puppet Hash or Array as a Hash key, do you want that as a Ruby Hash? (To encode it correctly in JSON it should be an Array of objects with key and value attributes for each hash entry - i.e: [ { "key": [1, 2, 3], "value": 100 } ... ] But now, it is no longer "just json" I am working on an implementation that will only return a Hash if the keys are Strings. Add Comment   This message was sent by Atlassian JIRA (v6.4.12#64027-sha1:e3691cc) -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To unsubscribe from this group and stop receiving emails from it, send an email to puppet-bugs+unsubscr...@googlegroups.com. To post to this group, send email to puppet-bugs@googlegroups.com. Visit this group at https://groups.google.com/group/puppet-bugs. For more options, visit https://groups.google.com/d/optout.