kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Merge pull request #10747 from javan/patch-1

Browse source 
Add note about upgrading custom routes from `put` to `patch`.
This commit is contained in:
David Heinemeier Hansson 2013-06-03 05:20:13 -07:00
commit 051228699d
1 changed files with 18 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

18
guides/source/upgrading_ruby_on_rails.md
View file

@ -41,6 +41,24 @@ So, in Rails 4 both `PUT` and `PATCH` are routed to update. We recommend
switching to `PATCH` as part of your upgrade process if possible, as it's more
likely what you want.
Note, when using `form_for` to update a resource in conjunction with a custom route,
you'll need to update your route to explicity match the `patch` verb:
```erb
<%= form_for [ :update_name, @user ] do |f| %>
...
<% end %>
```
```ruby
resources :users do
# Rails 3
put :update_name, on: :member
# Rails 4
patch :update_name, on: :member
end
```
For more on PATCH and why this change was made, see [this post](http://weblog.rubyonrails.org/2012/2/25/edge-rails-patch-is-the-new-primary-http-method-for-updates/)
on the Rails blog.