mirror of
https://github.com/nuxt/nuxt.git
synced 2024-11-22 21:55:11 +00:00
docs: fix useFetch
key generation logic (#24082)
This commit is contained in:
parent
e753abd7b8
commit
ec317befc0
@ -86,7 +86,7 @@ All fetch options can be given a `computed` or `ref` value. These will be watche
|
|||||||
::
|
::
|
||||||
|
|
||||||
- `Options` (from [`useAsyncData`](/docs/api/composables/use-async-data)):
|
- `Options` (from [`useAsyncData`](/docs/api/composables/use-async-data)):
|
||||||
- `key`: a unique key to ensure that data fetching can be properly de-duplicated across requests, if not provided, it will be generated based on the static code location where `useAsyncData` is used.
|
- `key`: a unique key to ensure that data fetching can be properly de-duplicated across requests, if not provided, it will be automatically generated based on URL and fetch options
|
||||||
- `server`: whether to fetch the data on the server (defaults to `true`)
|
- `server`: whether to fetch the data on the server (defaults to `true`)
|
||||||
- `lazy`: whether to resolve the async function after loading the route, instead of blocking client-side navigation (defaults to `false`)
|
- `lazy`: whether to resolve the async function after loading the route, instead of blocking client-side navigation (defaults to `false`)
|
||||||
- `immediate`: when set to `false`, will prevent the request from firing immediately. (defaults to `true`)
|
- `immediate`: when set to `false`, will prevent the request from firing immediately. (defaults to `true`)
|
||||||
|
Loading…
Reference in New Issue
Block a user