diff options
author | Kasper Timm Hansen <kaspth@gmail.com> | 2015-02-15 22:39:04 +0100 |
---|---|---|
committer | Kasper Timm Hansen <kaspth@gmail.com> | 2015-02-21 16:06:57 +0100 |
commit | 11644fd0ceb99f3f0529323df5ad625c596b3f21 (patch) | |
tree | d81f01715fd7966d193a657cc452edd308234fb0 /actionview/test/fixtures/override2/layouts | |
parent | e56c63542780fe2fb804636a875f95cae08ab3f4 (diff) | |
download | rails-11644fd0ceb99f3f0529323df5ad625c596b3f21.tar.gz rails-11644fd0ceb99f3f0529323df5ad625c596b3f21.tar.bz2 rails-11644fd0ceb99f3f0529323df5ad625c596b3f21.zip |
Collections automatically cache and fetch partials.
Collections can take advantage of `multi_read` if they render one template
and their partials begin with a cache call.
The cache call must correspond to either what the collections elements are
rendered as, or match the inferred name of the partial.
So with a notifications/_notification.html.erb template like:
```ruby
<% cache notification %>
<%# ... %>
<% end %>
```
A collection would be able to use `multi_read` if rendered like:
```ruby
<%= render @notifications %>
<%= render partial: 'notifications/notification', collection: @notifications, as: :notification %>
```
Diffstat (limited to 'actionview/test/fixtures/override2/layouts')
0 files changed, 0 insertions, 0 deletions