-1 PUT does not need to return the object because client would already know the object's attribute. If the client wants to refresh the object, they should issue another GET request.
POST returns the newly created object so that the client can cache the object with all of the attributes and id. Also, I think changing this would break all applications. If someone supporting this, it should go to Rails 4.0, not 3.2. - Prem On Oct 19, 2011, at 3:04 AM, Damien MATHIEU wrote: > Since this commit : > https://github.com/rails/rails/commit/0d3333257156544feba729ba28f6874d5a30d561 > PUT requests made on a controller using respond_with with the format json > render an empty hash. > José explains in the comments why it does so and it doesn't just renders the > modified document, like we do in POST. > > I would like to propose changing that default though, in the respond_with and > the scaffold to respond the modified object instead of an empty hash. > > -- > You received this message because you are subscribed to the Google Groups > "Ruby on Rails: Core" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/rubyonrails-core/-/u60P7OSRIh8J. > 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. -- 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.
