From a849d1d9261cc76d48472952ea5ed4854a857fb5 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Mislav=20Marohni=C4=87?= Date: Tue, 9 Sep 2008 04:15:00 +0200 Subject: resolve a few things asciidoc complained about --- railties/doc/guides/forms/form_helpers.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'railties') diff --git a/railties/doc/guides/forms/form_helpers.txt b/railties/doc/guides/forms/form_helpers.txt index b490c8bfb7..7b0aeb0ed9 100644 --- a/railties/doc/guides/forms/form_helpers.txt +++ b/railties/doc/guides/forms/form_helpers.txt @@ -65,7 +65,7 @@ To create that, we will use `form_tag`, `label_tag`, `text_field_tag` and `submi <% end %> ---------------------------------------------------------------------------- - [TIP] +[TIP] ============================================================================ `search_path` can be a named route specified in "routes.rb": @@ -198,11 +198,11 @@ Forms that deal with model attributes When we're dealing with an actual model, we will use a different set of form helpers and have Rails take care of some details in the background. In the following examples we will handle an Article model. First, let us have the controller create one: .articles_controller.rb ------------------------- +---------------------------------------------------------------------------- def new @article = Article.new end ------------------------- +---------------------------------------------------------------------------- Now we switch to the view. The first thing to remember is that we should use `form_for` helper instead of `form_tag`, and that we should pass the model name and object as arguments: -- cgit v1.2.3