aboutsummaryrefslogtreecommitdiffstats
path: root/guides
diff options
context:
space:
mode:
authorDavid Verhasselt <david@crowdway.com>2015-09-28 13:56:28 +0300
committerDavid Verhasselt <david@crowdway.com>2015-10-05 19:55:00 +0300
commitb4f4de050010aef2982c46b1b878a6deb1318429 (patch)
tree3d170f30ec09ead8a5be29c5411d26fc75675cde /guides
parent805bd7a81a376198b8ae8a90539e6487f3f14ca7 (diff)
downloadrails-b4f4de050010aef2982c46b1b878a6deb1318429.tar.gz
rails-b4f4de050010aef2982c46b1b878a6deb1318429.tar.bz2
rails-b4f4de050010aef2982c46b1b878a6deb1318429.zip
Remove TIP on parse_query
[ci skip]
Diffstat (limited to 'guides')
-rw-r--r--guides/source/form_helpers.md7
1 files changed, 0 insertions, 7 deletions
diff --git a/guides/source/form_helpers.md b/guides/source/form_helpers.md
index 84a8d695cb..34345e68a2 100644
--- a/guides/source/form_helpers.md
+++ b/guides/source/form_helpers.md
@@ -711,13 +711,6 @@ action for a Person model, `params[:person]` would usually be a hash of all the
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.
-TIP: You may find you can try out examples in this section faster by using the console to directly invoke Rack's parameter parser. For example,
-
-```ruby
-Rack::Utils.parse_query "name=fred&phone=0123456789"
-# => {"name"=>"fred", "phone"=>"0123456789"}
-```
-
### Basic Structures
The two basic structures are arrays and hashes. Hashes mirror the syntax used for accessing the value in `params`. For example, if a form contains: