> If the current core philosophy is that to_json should always generate > spec-valid JSON (as evidenced by > http://dev.rubyonrails.org/changeset/7697), then > http://dev.rubyonrails.org/changeset/6893, which caused this problem, > was contrary to that philosophy.
You're welcome to whatever philosophy you choose to hold to, but unless this change will also address the security issue identified, it's a complete non-starter ;) -- Cheers Koz --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/rubyonrails-core?hl=en -~----------~----~----~----~------~----~------~--~---
