On May 28, 11:13 am, Mislav Marohnić <[email protected]> wrote: > I bumped Rails 2.3-stable branch in our app today and deployed, thinking I'm > being a good developer by getting all the bugfixes this way. > What I actually did is broke many aspects of our app because all `to_json` > calls now return "{}" (hardcoded). > > Both ways to solve this require changing my code: > > 1. follow the instructions in the > commit<http://github.com/rails/rails/commit/d052e9fb5868a10df33a84bf61f40a32...>; > or > 2. change all `to_json` calls to `rails_to_json`. > > Now, I've been following the talk about ActiveSupport incompatibility with > the JSON gem. I'm not interesting in raising those issues again. I want to > know why was such thing backported — without warning — breaking backwards > compatibility?
I think this was fixed in a commit a few days ago. --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
