From ec317befc0c807f32e9c3b304cdcbec4677bc676 Mon Sep 17 00:00:00 2001 From: Marco Solazzi Date: Thu, 2 Nov 2023 18:35:09 +0900 Subject: [PATCH] docs: fix `useFetch` key generation logic (#24082) --- docs/3.api/2.composables/use-fetch.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/3.api/2.composables/use-fetch.md b/docs/3.api/2.composables/use-fetch.md index e26231098c..ecf3cbcf5a 100644 --- a/docs/3.api/2.composables/use-fetch.md +++ b/docs/3.api/2.composables/use-fetch.md @@ -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`)