class ActionView::PartialRenderer

<% end %>
<%- end -%>
Deadline: <%= user.deadline %>
<%- when :footer -%>
Title: <%= user.title %>
<%- case section when :header -%>
<%= render :layout => @users do |user, section| %>
<%# app/views/users/index.html.erb &>
</div>
<%= yield user, :footer %>
Budget: $<%= user.budget %>
<%= yield user, :header %>
<div class=“user”>
<%# app/views/users/_user.html.erb &>
You can also yield multiple times in one layout and use block arguments to differentiate the sections.
This will render the layout for each user and yield to the block, passing the user, each time.
<% end %>
Title: <%= user.title %>
<%= render :layout => @users do |user| %>
<%# app/views/users/index.html.erb &>
</div>
<%= yield user %>
Budget: $<%= user.budget %>
<div class=“user”>
<%# app/views/users/_user.html.erb &>
an array to layout and treat it as an enumerable.
If you pass arguments to “yield” then this will be passed to the block. One way to use this is to pass
As you can see, the :locals hash is shared between both the partial and its layout.
</div>
Title: <%= chief.name %>
Budget: $<%= user.budget %>
<div id=“administrator”>
…this will return:
<% end %>
Title: <%= chief.title %>
<%= render(:layout => “administrator”, :locals => { :user => chief }) do %>
<%# app/views/users/_chief.html.erb &>
You can also apply a layout to a block within any template:
</div>
Name: <%= user.name %>
Deadline: <%= user.deadline %>
<div id=“editor”>
Here’s the editor:
</div>
Name: <%= user.name %>
Budget: $<%= user.budget %>
<div id=“administrator”>
Here’s the administrator:
…this will return:
</div>
<%= yield %>
Deadline: <%= user.deadline %>
<div id=“editor”>
<%# app/views/users/_editor.html.erb &>
</div>
<%= yield %>
Budget: $<%= user.budget %>
<div id=“administrator”>
<%# app/views/users/_administrator.html.erb &>
Name: <%= user.name %>
<%# app/views/users/_user.html.erb &>
<%= render :partial => “user”, :layout => “editor”, :locals => { :user => editor } %>
Here’s the editor:
<%= render :partial => “user”, :layout => “administrator”, :locals => { :user => administrator } %>
Here’s the administrator:
<%# app/views/users/index.html.erb &>
of users:
specified globally for the entire action, but they work in a similar fashion. Imagine a list with two types
Partials can have their own layouts applied to them. These layouts are different than the ones that are
== Rendering partials with layouts
<%= render @posts %>
# <%= render :partial => “posts/post”, :collection => @posts %>
# that’s why we can replace:
# @posts is an array of Post instances, so every post record returns ‘posts/post’ on ‘to_partial_path`,
<%= render @account %>
# <%= render :partial => “accounts/account”, :locals => { :account => @account} %>
# @account.to_partial_path returns ’accounts/account’, so it can be used to replace:
<%= render “account”, :account => @buyer %>
# Instead of <%= render :partial => “account”, :locals => { :account => @buyer } %>
<%= render “account” %>
# Instead of <%= render :partial => “account” %>
defaults of render to render partials. Examples:
If you’re not going to be using any of the options like collections or layouts, you can also use the short-hand
== Rendering the default case
<%= render :partial => @posts %>
# <%= render :partial => “posts/post”, :collection => @posts %>
# that’s why we can replace:
# @posts is an array of Post instances, so every post record returns ‘posts/post’ on ‘to_partial_path`,
<%= render :partial => @account %>
# <%= render :partial => “accounts/account”, :locals => { :account => @account} %>
# @account.to_partial_path returns ’accounts/account’, so it can be used to replace:
all objects must return the same path.
and pick the proper path by checking ‘to_proper_path` method. If the object passed to render is a collection,
Instead of explicitly naming the location of a partial, you can also let PartialRenderer do the work
== Rendering objects that respond to `to_partial_path`
This will render the partial “advertisement/_ad.html.erb” regardless of which controller this is being called from.
<%= render :partial => “advertisement/ad”, :locals => { :ad => @advertisement } %>
Two controllers can share a set of partials and render them like this:
== Rendering shared partials
just keep domain objects, like Active Records, in there.
NOTE: Due to backwards compatibility concerns, the collection can’t be one of hashes. Normally you’d also
<%= render(:partial => “ad”, :collection => @advertisements) || “There’s no ad to be displayed” %>
to specify a text which will displayed instead by using this form:
If the given :collection is nil or empty, render will return nil. This will allow you
<%= render :partial => “ad”, :collection => @advertisements, :spacer_template => “ad_divider” %>
The following example will render advertiser/_ad_divider.html.erb between each ad partial:
You can specify a partial to be rendered between elements via the :spacer_template option.
The :as option may be used when rendering partials.
partial_name_counter. In the case of the example above, the template would be fed ad_counter.
iteration counter will automatically be made available to the template with a name of the form
This will render “advertiser/_ad.html.erb” and pass the local variable ad to the template for display. An
<%= render :partial => “ad”, :collection => @advertisements %>
example in “Using partials” can be rewritten with a single line:
accepts an array and renders a partial by the same name as the elements contained within. So the three-lined
render a sub template for each of the elements. This pattern has been implemented as a single method that
The example of partial use describes a familiar pattern where a template needs to iterate over an array and
== Rendering a collection of partials
<%= render :partial => “account”, :locals => { :user => @buyer } %>
This is equivalent to
<%= render :partial => “account”, :object => @buyer, :as => ‘user’ %>
wanted it to be user instead of account we’d do:
With the :as option we can specify a different name for said local variable. For example, if we
<%= render :partial => “account”, :locals => { :account => @buyer } %>
equivalent to:
would provide the +@buyer+ object to the partial, available under the local variable account and is
<%= render :partial => “account”, :object => @buyer %>
The :object option can be used to pass an object to the partial. For instance:
By default ActionView::PartialRenderer doesn’t have any local variables.
== The :as and :object options
render “advertiser/_ad.html.erb” and pass the local variable ad to the template for display.
This would first render “advertiser/_account.html.erb” with @buyer passed in as the local variable account, then
<% end %>
<%= render :partial => “ad”, :locals => { :ad => ad } %>
<% @advertisements.each do |ad| %>
<%= render :partial => “account”, :locals => { :account => @buyer } %>
In another template for Advertiser#buy, we could have:
This would render “advertiser/_account.html.erb”.
<%= render :partial => “account” %>
In a template for Advertiser#account:
templates that could be rendered on their own.
follow the naming convention of being prefixed with an underscore – as to separate them from regular
single object (we call this kind of sub templates for partials). It relies on the fact that partials should
There’s also a convenience method for rendering sub templates within the current controller that depends on a
= Action View Partials