TEST_CODEOWNERS/rails
3
0
Fork 0
Code Issues Pull Requests 1 Actions Packages Projects Releases Wiki Activity

fix: solves issue#27189

Browse Source
This commit is contained in:
jnoortheen 2016-11-27 22:59:59 +05:30
parent 143fc87cbf
commit fa497ebb0d
1 changed files with 4 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
guides/source/getting_started.md
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).