Permalink
Browse files

In example about params naming conventions use params[:person] [ci skip]

The example is about a Person model, say that "params[:model] would usually be a
hash of all the attributes for the person to create" could be confusing.
I changed to params[:person] since the example is about a Person creation.
  • Loading branch information...
1 parent b54e577 commit 030af5e9243a57c2e8bda523ca23fb7d6f5575ed @xoen xoen committed Aug 31, 2012
Showing with 1 addition and 1 deletion.
  1. +1 −1 guides/source/form_helpers.textile
@@ -654,7 +654,7 @@ If +f+ is an instance of FormBuilder then this will render the +form+ partial, s
h3. Understanding Parameter Naming Conventions
As you've seen in the previous sections, values from forms can be at the top level of the +params+ hash or nested in another hash. For example in a standard +create+
-action for a Person model, +params[:model]+ would usually be a hash of all the attributes for the person to create. The +params+ hash can also contain arrays, arrays of hashes and so on.
+action for a Person model, +params[:person]+ would usually be a hash of all the attributes for the person to create. The +params+ hash can also contain arrays, arrays of hashes and so on.
Fundamentally HTML forms don't know about any sort of structured data, all they generate is name–value pairs, where pairs are just plain strings. The arrays and hashes you see in your application are the result of some parameter naming conventions that Rails uses.

0 comments on commit 030af5e

Please sign in to comment.