kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity

Add tip for skipping partial and locals options for render

Browse source 
[ci skip]
This commit is contained in:
Yuki Nishijima 2015-02-08 15:38:20 -08:00
parent de9a3748c4
commit 1faadfdbcb
1 changed files with 15 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

15
guides/source/action_view_overview.md
View file

@ -190,6 +190,21 @@ One way to use partials is to treat them as the equivalent of subroutines; a way
Here, the `_ad_banner.html.erb` and `_footer.html.erb` partials could contain content that is shared among many pages in your application. You don't need to see the details of these sections when you're concentrating on a particular page. Here, the `_ad_banner.html.erb` and `_footer.html.erb` partials could contain content that is shared among many pages in your application. You don't need to see the details of these sections when you're concentrating on a particular page.
#### `render` without `partial` and `locals` options
In the above example, `render` takes 2 options: `partial` and `locals`. But if these are the only options you want to pass, you can skip using these options. For example, instead of:
```erb
<%= render partial: "product", locals: {product: @product} %>
```
You can also do:
```erb
<%= render "product", product: @product %>
```
#### The `as` and `object` options #### The `as` and `object` options
By default `ActionView::Partials::PartialRenderer` has its object in a local variable with the same name as the template. So, given: By default `ActionView::Partials::PartialRenderer` has its object in a local variable with the same name as the template. So, given: