aboutsummaryrefslogtreecommitdiffstats
path: root/guides/source/form_helpers.md
Commit message (Collapse)AuthorAgeFilesLines
...
| * fix wrong hash syntaxMikhail Dieterle2013-01-011-1/+1
| |
* | Change guides to use update instead of update_attributesAmparo Luna + Guillermo Iguaran2013-01-031-3/+3
|/
* Improve EnglishRuafozy2013-01-011-5/+7
| | | | | | * Fix one error * Improve wording * Improve punctuation
* remove Mass Assignment reference from Form Helpers guide [ci skip]Francesco Rodriguez2012-12-101-1/+1
|
* Remove references to Rails versions.Steve Klabnik2012-12-071-2/+0
| | | | | | | | There's no reason for guides to reference old behaviors. They should be current as of the versions of Rails that they ship with, and including older information just clutters thing. I discussed this change with @fxn and he agrees.
* Fixed grammar in a lot of guide prologues.Katie Oldaker2012-12-071-7/+7
|
* Normalize on 'After reading this guide, you will know:'Steve Klabnik2012-11-291-1/+1
| | | | | We have three or four different introduction sentences to the guides. After this commit, we use the same one everywhere.
* Fix title of 'form helpers' guide.Steve Klabnik2012-11-291-2/+2
| | | | | | They're Rails Guides, so obviously we're talking about Rails Form Helpers. Also, 'helpers' should be capitalized.
* Add periods to the bullet points in guides.Steve Klabnik2012-11-291-7/+7
| | | | Talked with @fxn about this. Bullet points should have periods at the ends.
* Switch to 1.9 hash syntaxAgis Anastasopoulos2012-11-161-30/+30
| | | I've intentionally left out some spots as they're the expected output, and since Hash#inspect yields `=>` I guess it may be confusing for beginners to see one syntax in the guide and a different one in their system.
* use em-dashes instead of two minuses in guidesburningTyger2012-11-101-4/+4
|
* Add backticks around link_to example in javascript guide [ci skip]Carlos Antonio da Silva2012-10-281-1/+1
|
* No more Textile guide generation supportPrem Sichanugrist2012-09-171-1/+1
|
* Fix the usage of `*` in MarkdownPrem Sichanugrist2012-09-171-7/+7
| | | | | In Textile `*` would convert to `<strong>`, but in Markdown we have to use `**` instead.
* Fix remaining formatting problems in the guidePrem Sichanugrist2012-09-171-22/+22
|
* Convert all the links into Markdown formatPrem Sichanugrist2012-09-171-12/+12
|
* Convert all inline codes to Markdown syntaxPrem Sichanugrist2012-09-171-106/+106
|
* Convert inline code tags to MarkdownPrem Sichanugrist2012-09-171-3/+3
|
* Convert heading tags and heading sectionPrem Sichanugrist2012-09-171-41/+51
|
* Convert code blocks into GFM stylePrem Sichanugrist2012-09-171-150/+150
|
* Rename the rest of the guides to MarkdownPrem Sichanugrist2012-09-171-0/+945