PATCH is the correct HTML verb to map to the #update action. The semantics for PATCH allows for partial updates, whereas PUT requires a complete replacement. Changes: * adds config.default_method_for_update you can set to :patch * optionally use PATCH instead of PUT in resource routes and forms * adds the #patch verb to routes to detect PATCH requests * adds #patch? to Request * changes documentation and comments to indicate support for PATCH This change maintains complete backwards compatibility by keeping :put as the default for config.default_method_for_update.
…nse body (as in the new scaffold)
…for api navigation Signed-off-by: José Valim <email@example.com>
… get or there are no errors Signed-off-by: José Valim <firstname.lastname@example.org>
…the default response status and error messages should be returned Signed-off-by: José Valim <email@example.com>
* resources is always an array; * Lazy retrieve request and formats; * Alias api_location and navigation_location to resource_location, making easier to change its behavior without affecting each other and without a need to reimplement any of the behavior methods.
ActionDispatch::Request rather than Rack::Request. * Changed ActionDispatch::Request#method to return a String, to be compatible with the Rack::Request superclass. * Changed ActionDispatch::Request#method to return the original method in the case of methodoverride and #request_method not to, to be compatible with Rack::Request
…l formats. Signed-off-by: Yehuda Katz <wycats@Yehuda-Katz.local>
…gured. Signed-off-by: Jeremy Kemper <firstname.lastname@example.org>
…d for caching and pagination. Signed-off-by: Yehuda Katz <email@example.com>
… ActionController::MimeResponds::Responder to ActionController::MimeResponds::Collector.