> Should I put in a ticket for that? This is exactly where feature requests go. So you kinda already did. ;)
> If you are trying to do a patch, then JSON in the request could be easily > converted to model representation in Rails. But just handling off the > implementation of a patch to the developer leaves a lot up in the air. Yep. I've been giving some though to declaring some sort of 'Rails flavored JSON' that would be able to address these kinds of issues, but it's not near the proposal stage yet. We don't know what every application needs, so currently, it's left up to each dev. > For example, when parsing a patch, it would seem that there would be some > way to differentiate between the incoming PATCH request specifying an > attribute as nil Again, this is the reason why PATCH requires a diff media type be sent to it. Then there's no question. -- 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.
