Form question

Rails
1

Hi, just started reading

and this code example:
<%= form_for(@post) do |f| %>
…

<%= f.label :name %>
<%= f.text_field :name %>
<%= f.label :title %>
<%= f.text_field :title %>
<%= f.label :content %>
<%= f.text_area :content %>
<%= f.submit %>

In case we need to show a field in several templates, we need to
duplicate its type (text_field etc). The type belongs to the field, so
why not remove this repetition by making a self-contained “field” like
f.name, or f.label, or f.content, that would encompass rendering logic
and would spit out proper form snippet: <%= f.name %> Then if someone
wanted to override how a certain field is rendered, they could spell
everything out as above.

2

On Tuesday, April 30, 2013 8:48:50 AM UTC+1, rihad wrote:

f.name, or f.label, or f.content, that would encompass rendering logic

and would spit out proper form snippet: <%= f.name %> Then if someone

wanted to override how a certain field is rendered, they could spell

everything out as above.

You certainly can do that - I think either the guide or the api docs for
form_for show how to subclass FormBuilder to achieve this. This is
something that is going to be quite specific to each app so doesn’t
belong in rails itself

Fred