Unwrap caching guide prose and replace invalidation table with a sentence

Author: joelhawksley

docs/guide/caching.md

@@ -12,12 +12,9 @@ Experimental
 Since 4.14.0
 {: .label }
 
-**This API is experimental.** It may change or be removed in a non-major release.
-Please share feedback in [#234](https://github.com/ViewComponent/view_component/issues/234).
+**This API is experimental.** It may change or be removed in a non-major release. Please share feedback in [#234](https://github.com/ViewComponent/view_component/issues/234).
 
-Rails computes a digest for every template from its source and from the templates
-it renders. That digest is mixed into the key of every `<% cache %>` block in the
-template, so editing a partial invalidates the caches of everything that renders it.
+Rails computes a digest for every template from its source and from the templates it renders. That digest is mixed into the key of every `<% cache %>` block in the template, so editing a partial invalidates the caches of everything that renders it.
 
 Components are invisible to that mechanism, which means this doesn't work:
 
@@ -27,13 +24,11 @@ Components are invisible to that mechanism, which means this doesn't work:
 <% end %>
 ```
 
-Editing `PostComponent`'s template, Ruby class, or sidecar files doesn't invalidate
-the fragment, so the stale markup is served until the cache is cleared by hand.
+Editing `PostComponent`'s template, Ruby class, or sidecar files doesn't invalidate the fragment, so the stale markup is served until the cache is cleared by hand.
 
 ## Opting in
 
-Include `ViewComponent::ExperimentallyCacheable` in each component that should
-participate in caching:
+Include `ViewComponent::ExperimentallyCacheable` in each component that should participate in caching:
 
 ```ruby
 class PostComponent < ViewComponent::Base
@@ -45,29 +40,11 @@ class PostComponent < ViewComponent::Base
 end
 ```
 
-That's all that's needed for the `<% cache %>` block above to work. The component
-is registered with Rails' digest tree, and the fragment is invalidated when any of
-the following change:
-
-| Change | Invalidates |
-|---|---|
-| The component's template | ✅ |
-| The component's Ruby class | ✅ |
-| A sidecar file (such as an i18n `.yml`) | ✅ |
-| A superclass's template or Ruby class | ✅ |
-| A child component rendered by the template | ✅ |
-| A partial rendered by the template | ✅ |
-| A child component rendered by an inline template or `#call` method | ✅ |
-| A partial rendered by an inline template | ✅ |
-| A partial rendered by a `#call` method | ❌ [use the escape hatch](#declaring-dependencies-static-analysis-cant-see) |
-
-Components that don't include the module are unaffected, and applications that
-never opt in pay no cost.
+That's all that's needed for the `<% cache %>` block above to work. The component is registered with Rails' digest tree, and the fragment is invalidated when the component's template, Ruby class, sidecar files, superclasses, child components, or rendered partials change, including children and partials rendered from an inline template and children rendered from a `#call` method. The one exception is a partial referenced by string path from a `#call` method, which needs [the escape hatch](#declaring-dependencies-static-analysis-cant-see).
 
 ## Caching a component's own output
 
-Use `cache_on` to have the component cache its own rendered output. Each argument
-names a method whose value identifies a rendering of the component:
+Use `cache_on` to have the component cache its own rendered output. Each argument names a method whose value identifies a rendering of the component:
 
 ```ruby
 class PostComponent < ViewComponent::Base
@@ -85,15 +62,13 @@ class PostComponent < ViewComponent::Base
 end
 ```
 
-Rendering the component now reads from and writes to `Rails.cache`, with no
-`<% cache %>` block at the call site:
+Rendering the component now reads from and writes to `Rails.cache`, with no `<% cache %>` block at the call site:
 
 ```erb
 <%= render PostComponent.new(post: @post) %>
 ```
 
-Private methods are allowed, so the values that form the key don't have to be
-part of the component's public interface.
+Private methods are allowed, so the values that form the key don't have to be part of the component's public interface.
 
 The cache key combines:
 
@@ -103,13 +78,11 @@ The cache key combines:
 - the current `I18n.locale`
 - the values returned by the `cache_on` methods
 
-Caching is skipped unless `perform_caching` is enabled on the controller, matching
-the behavior of Rails' `cache` helper. Override `#cache_key` for full control.
+Caching is skipped unless `perform_caching` is enabled on the controller, matching the behavior of Rails' `cache` helper. Override `#cache_key` for full control.
 
 ## Reading a component's digest
 
-`.cache_digest` returns the digest of everything the component renders from. It
-works outside a request, where no view context exists:
+`.cache_digest` returns the digest of everything the component renders from. It works outside a request, where no view context exists:
 
 ```ruby
 PostComponent.cache_digest # => "a1b2c3..."
@@ -125,24 +98,21 @@ Use it to build cache keys by hand, or to key a cache in a background job:
 
 ## Declaring dependencies static analysis can't see
 
-Dependencies are discovered by scanning template and Ruby source, so dynamic
-renders are invisible:
+Dependencies are discovered by scanning template and Ruby source, so dynamic renders are invisible:
 
 ```erb
 <%= render @component %>
 ```
 
-The same applies to a partial referenced by string path from a `#call` method,
-which is the one dependency kind that isn't discovered automatically:
+The same applies to a partial referenced by string path from a `#call` method, which is the one dependency kind that isn't discovered automatically:
 
 ```ruby
 def call
   render "posts/byline" # not tracked
 end
 ```
 
-Declare these with Rails' `# Template Dependency:` comment, in either the Ruby
-file or the template:
+Declare these with Rails' `# Template Dependency:` comment, in either the Ruby file or the template:
 
 ```ruby
 class PostComponent < ViewComponent::Base
@@ -154,8 +124,7 @@ end
 
 ## Caveats
 
-**Content blocks aren't cached.** Content passed as a block isn't part of the
-cache key, so caching it would risk serving one caller's content to another:
+**Content blocks aren't cached.** Content passed as a block isn't part of the cache key, so caching it would risk serving one caller's content to another:
 
 ```erb
 <%# Not cached: the block's content isn't in the key %>
@@ -164,18 +133,10 @@ cache key, so caching it would risk serving one caller's content to another:
 <% end %>
 ```
 
-To cache a component that takes content, include the values that determine that
-content in `cache_on`, and set the content from within the component rather than
-from the call site.
+To cache a component that takes content, include the values that determine that content in `cache_on`, and set the content from within the component rather than from the call site.
 
-**Slots have the same constraint.** Slot content set by the caller isn't part of
-the key unless declared in `cache_on`.
+**Slots have the same constraint.** Slot content set by the caller isn't part of the key unless declared in `cache_on`.
 
-**`cache_on` methods run before the component renders**, so they can only depend
-on the component's own state, not on `helpers` or the view context. A cache key
-that depends on the view context is usually a sign the value should be passed to
-the component instead.
+**`cache_on` methods run before the component renders**, so they can only depend on the component's own state, not on `helpers` or the view context. A cache key that depends on the view context is usually a sign the value should be passed to the component instead.
 
-**Included modules aren't tracked.** A component's superclasses are, but a module
-included into a component isn't, since a module has no template or source file of
-its own to hash. Use `# Template Dependency:` for those.
+**Included modules aren't tracked.** A component's superclasses are, but a module included into a component isn't, since a module has no template or source file of its own to hash. Use `# Template Dependency:` for those.