Panasonic Youth

Rails 2.3, JSON, and lamentations

There is a nasty gotcha in Rails 2.3 involving rendering JSON from models and a surprising change in behavior. If you are familiar with how Rails renders xml for models, you may expect json to be very similar. You would probably expect a top level root node followed by the attributes:

{"person" => { "city=>nil, "name"=> "Foo Bar" } }

It appears somewhere on the road to 2.3, the JSON encoding changed so there is no longer a top level node:

{"city"=>nil, "name"=>"Foo Bar" }

The end result of this change means that if you have consumers expecting JSON in a typical “Rails” format, with a top level element denoting the class, there will be pain. We just hit this in a project when trying to use ActiveResource to consume some models exposed via standard restful actions.

The following demonstrates how this breaks down exactly:

# in the backend web app
Person.create! :name => "foo"

# meanwhile, in an active resource consumer
person = Person.find(1)  # finds a model okay, but...

# the below all raise NoMethodError
# they _should_ find the attribute from the attribute hash
# and quack like an ActiveRecord model

person.attributes # returns a hash in the format of { "person" => { "name" => "foo"...}, which is where the problem lies

It appears this issue is fixed or on the way to be fixed in the 2.3 stable branch, but for now be wary of JSON support in general on 2.3 until more of the below tickets get resolved.