\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[1984,1987],{"name":1985,"color":1986},"enhancement","a2eeef",{"name":1988,"color":1989},"triage","ffffff",3868,"nuxt","ui","open","Allow assigning IDs to Nuxt UI Tab panels for scroll targeting","2025-04-12T08:35:52Z","https://github.com/nuxt/ui/issues/3868",0.76096815,{"description":1999,"labels":2000,"number":2004,"owner":1991,"repository":1991,"state":1993,"title":2005,"updated_at":2006,"url":2007,"score":2008},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v21.5.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.15.4\r\n- Builder: -\r\n- User Config: ssr, devtools, modules, imports, shadcn\r\n- Runtime Modules: @nuxtjs/supabase@1.1.6, @nuxtjs/tailwindcss@6.11.4, @vueuse/nuxt@10.8.0, @pinia/nuxt@0.5.1, nuxt-icon@0.6.8, shadcn-nuxt@0.9.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-refreshnuxtdata-bug?file=app.vue\r\n\r\n### Describe the bug\r\n\r\n1. Open the reproduction.\r\n2. Click \"add new user\", the new user is added to the 'SidebarUsers' component (refreshNuxtData triggers the re-fetch because the sidebar is visible).\r\n3. Click \"toggle sidebar\" to hide it, now click \"add new user\" and re-open the sidebar (when refreshNuxtData is executed, the sidebar is not visible so it doesn't re-fetch the data). The new user is not added to the list.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2001],{"name":2002,"color":2003},"pending triage","E99695",26165,"`refreshNuxtData` doesn't re-fetch data when `useAsyncData`/`useFetch` (with `getCachedData`) are not in scope","2024-09-19T09:10:10Z","https://github.com/nuxt/nuxt/issues/26165",0.7613343,{"description":2010,"labels":2011,"number":2014,"owner":1991,"repository":1992,"state":1993,"title":2015,"updated_at":2016,"url":2017,"score":2018},"### Description\r\n\r\nHi 👋🏻 \r\n\r\nI started using NuxtUI and realized one more thing that can be improved. Right now, For `v-model` of tabs component index (number) is used.\r\n\r\nIf we want to get the key of active tab for making API req then we have to do something like below:\r\n```ts\r\nconst activeTabKey = items[itemsModel.value]!.key\r\n\r\n// With this feature implemented we can directly use `itemsModel.value`\r\n```\r\n\r\nInstead, if we can allow using `key` then:\r\n- I'll be more readable\r\n- If we change the order of the tabs (in items array) it doesn't affect the active tab\r\n\r\n### Additional context\r\n\r\nWe can also introduce this change in v3.",[2012,2013],{"name":1985,"color":1986},{"name":1988,"color":1989},2061,"Allow using tab item key as value for v-model","2024-08-20T06:04:17Z","https://github.com/nuxt/ui/issues/2061",0.7615046,{"description":2020,"labels":2021,"number":2025,"owner":1991,"repository":1991,"state":1993,"title":2026,"updated_at":2027,"url":2028,"score":2029},"### Describe the feature\n\nIt's really nice UX to auto-refresh data when the user re-focus the page.\r\n\r\n```js\r\nuseFetch({\r\n refreshOnFocus: true,\r\n})\r\n```\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2022],{"name":2023,"color":2024},"discussion","538de2",26018,"useFetch: refresh on window focus/activate","2024-06-30T11:05:32Z","https://github.com/nuxt/nuxt/issues/26018",0.7636775,{"description":2031,"labels":2032,"number":2033,"owner":1991,"repository":2034,"state":2035,"title":2036,"updated_at":2037,"url":2038,"score":2039},"https://www.figma.com/file/OLlmzoVQ7FSBh4FJJORNpl/nuxt.com?node-id=4452%3A42741",[],472,"nuxt.com","closed","[Company] Careers integration `/company/careers`","2023-02-15T12:31:28Z","https://github.com/nuxt/nuxt.com/issues/472",0.6931942,{"description":2041,"labels":2042,"number":2052,"owner":1991,"repository":1991,"state":2035,"title":2053,"updated_at":2054,"url":2055,"score":2056},"he documentation does not mention a \"query\" option, this should be updated and explained across the docs.\r\n\r\n_Originally posted by @Aietes in https://github.com/nuxt/nuxt.js/issues/15359\r\n ",[2043,2046,2049],{"name":2044,"color":2045},"documentation","5319e7",{"name":2047,"color":2048},"good first issue","fbca04",{"name":2050,"color":2051},"3.x","29bc7f",15368,"Document `query` option for `useFetch`","2023-01-19T17:49:12Z","https://github.com/nuxt/nuxt/issues/15368",0.72346705,{"labels":2058,"number":2061,"owner":1991,"repository":1991,"state":2035,"title":2062,"updated_at":2063,"url":2064,"score":2065},[2059,2060],{"name":2050,"color":2051},{"name":2002,"color":2003},14328,"`useFetch` fired only once despite navigating back to the page","2023-01-19T17:33:49Z","https://github.com/nuxt/nuxt/issues/14328",0.7365081,{"description":2067,"labels":2068,"number":2071,"owner":1991,"repository":1991,"state":2035,"title":2072,"updated_at":2073,"url":2074,"score":2075},"I recently encountered an issue while using useFetch where I needed to prevent caching in a request. Unfortunately, it took me several hours of research to discover that a cache option exists for useFetch since it wasn't explicitly mentioned in the documentation. As a beginner, this was quite challenging and led to some frustration.\r\n\r\nI believe adding a cache option to the documentation would greatly benefit users like myself. Clear documentation plays a crucial role in making tools accessible, especially for those who are just starting. By explicitly mentioning the cache option and providing usage examples, beginners would be able to leverage this functionality more efficiently, saving time and effort.\r\n\r\nExample:\r\n\r\n```\r\nconst { data, error} = await useFetch\u003CGeneralResponse>('/bookmark/add', {\r\n method: 'post',\r\n cache: false,\r\n headers: {\r\n 'Content-Type': 'application/json',\r\n Authorization: `Bearer ${token.value}`\r\n },\r\n body: {\r\n id: id\r\n },\r\n });\r\n```",[2069,2070],{"name":2044,"color":2045},{"name":2050,"color":2051},27080,"Suggestion for useFetch Documentation: Add cache Option","2024-05-15T10:51:48Z","https://github.com/nuxt/nuxt/issues/27080",0.7447497,{"description":2077,"labels":2078,"number":2081,"owner":1991,"repository":1991,"state":2035,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v19.5.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@9.3.1`\r\n- Builder: `vite`\r\n- User Config: `modules`, `runtimeConfig`, `content`, `image`, `googleFonts`\r\n- Runtime Modules: `@nuxt/content@2.5.2`, `@nuxtjs/google-fonts@3.0.0`, `@nuxt/image-edge@1.0.0-27968280.9739e4d`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nThe following code fetches search results. It's automatically refreshed when the searchquery ref is changed.\r\n\r\n```javascript\r\nconst navSearchAPICall = useLazyAsyncData(\r\n 'searchWorking',\r\n () => $fetch('/api/search', {\r\n params: {\r\n query: searchquery.value\r\n }\r\n }),\r\n { \r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\nThis works as expected. But the following code, wich should behave the same according to the documentation, does not work. The request is refreshed when the searchquery ref changes, but the query parameters stay the same.\r\n\r\n```javascript\r\nconst searchAPICall = useLazyFetch('/api/search', {\r\n key: 'searchNotWorking',\r\n params: {\r\n query: searchquery.value\r\n },\r\n server: false,\r\n watch: [searchquery]\r\n }\r\n)\r\n```\r\n\r\n\r\n\n\n### Describe the bug\n\nAs described in the reproduction, when using `useLazyAsyncData`, the request is refreshed with updated query parameters according to the searchquery ref. \r\n\r\nBut when using `useLazyFetch`, the request is refreshed but sent with unchanged query parameters.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2079,2080],{"name":2050,"color":2051},{"name":2002,"color":2003},19665,"useLazyFetch does not behave like useLazyAsyncData","2023-03-14T11:09:45Z","https://github.com/nuxt/nuxt/issues/19665",0.7467136,{"description":2087,"labels":2088,"number":2096,"owner":1991,"repository":1991,"state":2035,"title":2097,"updated_at":2098,"url":2099,"score":2100},"### Environment\n\nNuxi 3.0.0-rc.12 11:37:18\r\nRootDir: /Users/staffan/dev/giglets/site/frontend 11:37:18\r\nNuxt project info: (copied to clipboard) 11:37:18\r\n\r\n------------------------------\r\n- Operating System: `Darwin`\r\n- Node Version: `v14.20.1`\r\n- Nuxt Version: `3.0.0-rc.12`\r\n- Nitro Version: `0.6.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `ssr`, `sourcemap`, `app`, `modules`, `proxy`, `vite`\r\n- Runtime Modules: `@nuxtjs-alt/proxy@1.3.7`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\napp.vue:\r\n```\r\n\u003Cscript setup>\r\nconst count = ref(1);\r\nconst data = ref('');\r\nwatch(count, () =>\r\n useFetch('/api/hello/', { key: 'hello' }).then(\r\n (r) => (data.value = r.data.value)\r\n )\r\n);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CNuxtExampleLayout example=\"composables/use-fetch\">\r\n \u003Cdiv>\r\n Fetch result:\r\n \u003Cpre class=\"text-left\">\u003Ccode>{{ data }}\u003C/code>\u003C/pre>\r\n \u003CNButton\r\n @click=\"\r\n clearNuxtData('$fhello');\r\n count++;\r\n \"\r\n >\r\n Works\r\n \u003C/NButton>\r\n \u003CNButton\r\n @click=\"\r\n clearNuxtData('hello');\r\n count++;\r\n \"\r\n >\r\n Does not work\r\n \u003C/NButton>\r\n \u003C/div>\r\n \u003C/NuxtExampleLayout>\r\n\u003C/template>\r\n```\r\n\r\nserver/api/[...hello].ts:\r\n```\r\nlet seq = 1;\r\nexport default defineEventHandler((event) => ({\r\n seq: seq++,\r\n}));\r\n```\r\n\n\n### Describe the bug\n\n`useFetch` is called with an explicit `key` and that same value is used in `clearNuxtData` to clear the cached data and force a refresh.\r\n\r\nExpected result:\r\nThe cache is cleared and new data is fetched.\r\n\r\nActual result:\r\nThe cache is not cleared and no data is fetched.\r\n\r\nWorkaround:\r\nPrepend the key with `$f` when calling `clearNuxtData`. This works, but is not the documented behaviour.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2089,2090,2093],{"name":2050,"color":2051},{"name":2091,"color":2092},"bug","d73a4a",{"name":2094,"color":2095},"🍰 p2-nice-to-have","0E8A16",15337,"clearNuxtData does not work with useFetch and a provided key","2023-01-19T17:48:45Z","https://github.com/nuxt/nuxt/issues/15337",0.7509765,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"JB0P2f5afaA9OkgpsAvrOqduUKbmFyn0OL1hzEKL7Uw":-1},"/nuxt/fonts/471"]