As I've done more development with Rails I've become more interested in refactoring and simplifying my code. One of the ways I've found to do that is to combine actions in object creation. This means going from having separate "new" and "create" actions to just having single "new" action.
How? The wonder of @request.post?@.
So let's say I have an action "new" that lets a user fill out a form to create a new Widget. It might look something like this:
<pre>
<%= start_form_tag :action => "create" %>
<%= text_field "widget", "name" %>
<%= submit_tag "create" %>
<%= end_form_tag %>
</pre>
With the corresponding actions in the controller:
<pre>
def new
@widget = Widget.new
end
def create
@widget = Widget.new(params[:widget])
@widget.save
end
</pre>
So wouldn't it be easier to just have one action for this whole process? I'd like to think so. Here's the combined solution:
Change our form action:
<pre>
<%= start_form_tag :action => "new" %>
</pre>
And combine our controller actions:
<pre>
def new
@widget = Widget.new
if request.post?
@widget = Widget.new(params[:widget])
@widget.save
end
end
</pre>
Now our form redirects to itself, but it passes along the user entered form information as a post request. By checking for the presence of the post information in the request we can determine if the call of the "new" action is the first initial load or a user submit click.
The result is one less action in the controller and a simpler process for creating a new Widget. The process is the same for combining Edit/Update actions into a single Edit action.
2006-05-20T23:14:47+00:00
0
<p>As I’ve done more development with Rails I’ve become more interested in refactoring and simplifying my code. One of the ways I’ve found to do that is to combine actions in object creation. This means going from having separate “new” and “create” actions to just having single “new” action.</p>
<p>How? The wonder of <code>request.post?</code>.</p>
<p>So let’s say I have an action “new” that lets a user fill out a form to create a new Widget. It might look something like this:</p>
<pre>
<%= start_form_tag :action => "create" %>
<%= text_field "widget", "name" %>
<%= submit_tag "create" %>
<%= end_form_tag %>
</pre>
<p>With the corresponding actions in the controller:</p>
<pre>
def new
@widget = Widget.new
end
def create
@widget = Widget.new(params[:widget])
@widget.save
end
</pre>
<p>So wouldn’t it be easier to just have one action for this whole process? I’d like to think so. Here’s the combined solution:</p>
<p>Change our form action:</p>
<pre>
<%= start_form_tag :action => "new" %>
</pre>
<p>And combine our controller actions:</p>
<pre>
def new
@widget = Widget.new
if request.post?
@widget = Widget.new(params[:widget])
@widget.save
end
end
</pre>
<p>Now our form redirects to itself, but it passes along the user entered form information as a post request. By checking for the presence of the post information in the request we can determine if the call of the “new” action is the first initial load or a user submit click.</p>
<p>The result is one less action in the controller and a simpler process for creating a new Widget. The process is the same for combining Edit/Update actions into a single Edit action.</p>
26
1
1
How To Combine Form Actions in Rails
notebook/2006/05/20/how_to_combine_form_actions_in_rails