mirror of
https://github.com/rails/rails.git
synced 2022-11-09 12:12:34 -05:00
Tiny documentation edits [ci skip]
This commit is contained in:
parent
0de359c5ef
commit
0b57f090c9
2 changed files with 8 additions and 8 deletions
|
@ -155,7 +155,7 @@ module ActionMailer
|
|||
# Note that <tt>deliver_later</tt> will execute your method from the background job.
|
||||
#
|
||||
# You never instantiate your mailer class. Rather, you just call the method you defined on the class itself.
|
||||
# All instance method are expected to return a message object to be sent.
|
||||
# All instance methods are expected to return a message object to be sent.
|
||||
#
|
||||
# = Multipart Emails
|
||||
#
|
||||
|
|
|
@ -39,7 +39,7 @@ module ActionView
|
|||
# This will include both records as part of the cache key and updating either of them will
|
||||
# expire the cache.
|
||||
#
|
||||
# ==== Template digest
|
||||
# ==== \Template digest
|
||||
#
|
||||
# The template digest that's added to the cache key is computed by taking an md5 of the
|
||||
# contents of the entire template file. This ensures that your caches will automatically
|
||||
|
@ -75,7 +75,7 @@ module ActionView
|
|||
# render(topics) => render("topics/topic")
|
||||
# render(message.topics) => render("topics/topic")
|
||||
#
|
||||
# It's not possible to derive all render calls like that, though.
|
||||
# It's not possible to derive all render calls like that, though.
|
||||
# Here are a few examples of things that can't be derived:
|
||||
#
|
||||
# render group_of_attachments
|
||||
|
@ -98,14 +98,14 @@ module ActionView
|
|||
# <%# Template Dependency: todolists/todolist %>
|
||||
# <%= render_sortable_todolists @project.todolists %>
|
||||
#
|
||||
# The pattern used to match these is /# Template Dependency: ([^ ]+)/,
|
||||
# The pattern used to match these is <tt>/# Template Dependency: (\S+)/</tt>,
|
||||
# so it's important that you type it out just so.
|
||||
# You can only declare one template dependency per line.
|
||||
#
|
||||
# === External dependencies
|
||||
#
|
||||
# If you use a helper method, for example, inside a cached block and
|
||||
# you then update that helper, you'll have to bump the cache as well.
|
||||
# If you use a helper method, for example, inside a cached block and
|
||||
# you then update that helper, you'll have to bump the cache as well.
|
||||
# It doesn't really matter how you do it, but the md5 of the template file
|
||||
# must change. One recommendation is to simply be explicit in a comment, like:
|
||||
#
|
||||
|
@ -130,8 +130,8 @@ module ActionView
|
|||
# The collection can then automatically use any cached renders for that
|
||||
# template by reading them at once instead of one by one.
|
||||
#
|
||||
# See ActionView::Template::Handlers::ERB.resource_cache_call_pattern for
|
||||
# more information on what cache calls make a template eligible for this
|
||||
# See ActionView::Template::Handlers::ERB.resource_cache_call_pattern for
|
||||
# more information on what cache calls make a template eligible for this
|
||||
# collection caching.
|
||||
#
|
||||
# The automatic cache multi read can be turned off like so:
|
||||
|
|
Loading…
Reference in a new issue