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

Merge pull request #27190 from jnoortheen/issue-27189

I found this issue and wanted to give the fix.
This commit is contained in:
Santiago Pastorino 2016-11-27 23:23:16 -03:00 committed by GitHub
commit 8b2505347f

View file

@ -1157,7 +1157,7 @@ it look as follows:
```html+erb
<h1>Edit article</h1>
<%= form_for :article, url: article_path(@article), method: :patch do |f| %>
<%= form_for(@article) do |f| %>
<% if @article.errors.any? %>
<div id="error_explanation">
@ -1195,14 +1195,15 @@ it look as follows:
This time we point the form to the `update` action, which is not defined yet
but will be very soon.
The `method: :patch` option tells Rails that we want this form to be submitted
Passing the article object to the method, will automagically create url for submitting the edited article form.
This option tells Rails that we want this form to be submitted
via the `PATCH` HTTP method which is the HTTP method you're expected to use to
**update** resources according to the REST protocol.
The first parameter of `form_for` can be an object, say, `@article` which would
cause the helper to fill in the form with the fields of the object. Passing in a
symbol (`:article`) with the same name as the instance variable (`@article`)
also automagically leads to the same behavior. This is what is happening here.
also automagically leads to the same behavior.
More details can be found in [form_for documentation]
(http://api.rubyonrails.org/classes/ActionView/Helpers/FormHelper.html#method-i-form_for).