You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Under Rails 4.1.8, if I have a simple view defined like this:
object@foo=>'foo'attributes:data,:id
and the controller sets @foo to be a FooPresenter, then upgrading from rabl 0.11.5 to 0.11.6 changes the rendered JSON output from this: "foo" => {"data"=>"bar", "id"=>3250}
to this: "string" => {"data"=>"bar", "id"=>3250}
I've tracked it down to this change. I'm not really sure what's going on there, but it looks like it's causing class name of the last part of the object hash to be stringified? Changing the 'foo' to :foo in the view does not exhibit the problem.
The text was updated successfully, but these errors were encountered:
Under Rails 4.1.8, if I have a simple view defined like this:
and the controller sets
@foo
to be a FooPresenter, then upgrading from rabl 0.11.5 to 0.11.6 changes the rendered JSON output from this:"foo" => {"data"=>"bar", "id"=>3250}
to this:
"string" => {"data"=>"bar", "id"=>3250}
I've tracked it down to this change. I'm not really sure what's going on there, but it looks like it's causing class name of the last part of the
object
hash to be stringified? Changing the'foo'
to:foo
in the view does not exhibit the problem.The text was updated successfully, but these errors were encountered: