@@ -241,11 +241,11 @@ View all the available `cache` options in the [`fetch` API reference](/docs/app/
...
@@ -241,11 +241,11 @@ View all the available `cache` options in the [`fetch` API reference](/docs/app/
If you have multiple `fetch` requests in a route segment (e.g. a Layout or Page), you can configure the caching behavior of all data requests in the segment using the [Segment Config Options](/docs/app/api-reference/file-conventions/route-segment-config).
If you have multiple `fetch` requests in a route segment (e.g. a Layout or Page), you can configure the caching behavior of all data requests in the segment using the [Segment Config Options](/docs/app/api-reference/file-conventions/route-segment-config).
For example, using `constdynamic='force-dynamic` will cause all data to be fetched at request time, and the segment to be rendered dynamically.
For example, using `constdynamic='force-dynamic'` will cause all data to be fetched at request time, and the segment to be rendered dynamically.
```jsfilename="layout.js / page.js"
```jsfilename="layout.js / page.js"
// Add
// Add
export const dynamic = 'auto'
exportconstdynamic='force-dynamic'
```
```
There's an extensive list of Segment Config options, giving you fine-grained control of static and dynamic behavior of a route segment. See the [API reference](/docs/app/api-reference/file-conventions/route-segment-config) for more.
There's an extensive list of Segment Config options, giving you fine-grained control of static and dynamic behavior of a route segment. See the [API reference](/docs/app/api-reference/file-conventions/route-segment-config) for more.