Unverified Commit b2c48352 authored by Joseph's avatar Joseph Committed by GitHub

docs: correct the upper stale bound for App Shell exclusion in cacheLife (#97653)

Clarifying that:

> - **`stale` from 30 seconds up to 5 minutes**: included in prerenders,
but excluded from the route's [App Shell](/docs/app/glossary#app-shell).

Means, 30 <= stale and stale < 5minutes
parent a91dff6e
...@@ -265,7 +265,7 @@ A short cache lifetime changes where the cached content can be delivered from: ...@@ -265,7 +265,7 @@ A short cache lifetime changes where the cached content can be delivered from:
- **`revalidate` of `0`, or `expire` under 5 minutes**: excluded from prerenders, becoming a "dynamic hole" resolved at request time. - **`revalidate` of `0`, or `expire` under 5 minutes**: excluded from prerenders, becoming a "dynamic hole" resolved at request time.
- **`stale` under 30 seconds**: excluded from prerenders, because a prefetch would expire before the user could click. - **`stale` under 30 seconds**: excluded from prerenders, because a prefetch would expire before the user could click.
- **`stale` from 30 seconds up to 5 minutes**: included in prerenders, but excluded from the route's [App Shell](/docs/app/glossary#app-shell). - **`stale` of at least 30 seconds but under 5 minutes**: included in prerenders, but excluded from the route's [App Shell](/docs/app/glossary#app-shell).
Of the presets, only `seconds` falls under any of these thresholds: its `expire` of 1 minute excludes it from prerenders. Of the presets, only `seconds` falls under any of these thresholds: its `expire` of 1 minute excludes it from prerenders.
......
Markdown is supported
0% or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment