From 5650927c3461f0623b7f96ba51845dc0ffcaa68d Mon Sep 17 00:00:00 2001 From: victorkwok97 Date: Sat, 3 Sep 2022 18:56:12 +0800 Subject: [PATCH] docs: add note about `useFetch` auto generated key (#7044) --- docs/content/3.api/1.composables/use-fetch.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/3.api/1.composables/use-fetch.md b/docs/content/3.api/1.composables/use-fetch.md index dd61bc6bca..5571eba87f 100644 --- a/docs/content/3.api/1.composables/use-fetch.md +++ b/docs/content/3.api/1.composables/use-fetch.md @@ -44,7 +44,7 @@ type AsyncData = { * `headers`: Request headers. * `baseURL`: Base URL for the request. * **Options (from `useAsyncData`)**: - * `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 `url` and fetch options. + * `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 `useAyncData` is used. * `lazy`: Whether to resolve the async function after loading the route, instead of blocking navigation (defaults to `false`). * `server`: Whether to fetch the data on the server (defaults to `true`). * `default`: A factory function to set the default value of the data, before the async function resolves - particularly useful with the `lazy: true` option.