Zengtudor/Nuxt
1
0
Fork 0
mirror of https://github.com/nuxt/nuxt.git synced 2024-11-22 05:35:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: fix useFetch key generation logic (#24082)

Browse Source
This commit is contained in:
Marco Solazzi 2023-11-02 18:35:09 +09:00 committed by GitHub
parent e753abd7b8
commit ec317befc0
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
docs/3.api/2.composables/use-fetch.md
View File

@ -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)):
- `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`)
- `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`)