\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[2865,2868],{"name":2866,"color":2867},"enhancement","a2eeef",{"name":2869,"color":2870},"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.7512324,{"description":2880,"labels":2881,"number":2889,"owner":2872,"repository":2873,"state":2874,"title":2890,"updated_at":2891,"url":2892,"score":2893},"### Environment\n\nsandbox\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/admiring-herschel-qyt4kh\n\n### Description\n\n`app.config`\n\n```\nbutton: {\n compoundVariants: [\n {\n color: 'primary',\n variant: 'soft',\n class: {\n base: 'text-green-500',\n leadingIcon: 'text-red-500'\n }\n },\n ]\n}\n```\n\nif button defined like without `active` the icon is red, but text is green\n```\n\u003CUButton\n label=\"Label\"\n color=\"primary\"\n variant=\"soft\"\n icon=\"mdi-account\"\n />\n```\n\nsame result is expected when using `active`, but `leadingIcon` is ignored\n```\n\u003CUButton\n label=\"Label\"\n active\n active-color=\"primary\"\n active-variant=\"soft\"\n icon=\"mdi-account\"\n @click.prevent=\"active = !active\"\n/>\n```\n\n### Additional context\n\n\u003Cimg width=\"202\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0756fb1c-772c-44ae-855d-90aba304bd9e\" />",[2882,2885,2888],{"name":2883,"color":2884},"bug","d73a4a",{"name":2886,"color":2887},"v3","49DCB8",{"name":2869,"color":2870},3972,"Different result than static for active-color & active-variant","2025-04-24T15:30:39Z","https://github.com/nuxt/ui/issues/3972",0.7528392,{"description":2895,"labels":2896,"number":2900,"owner":2872,"repository":2872,"state":2874,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Describe the feature\n\nSince Nuxt 3.2, useFetch automatically passes request data to api call in an SSR context. The steps described in the docs aren't needed anymore: https://nuxt.com/docs/getting-started/data-fetching#example-pass-client-headers-to-the-api\r\n\r\nI think we shouldn't remove this section right away, but I propose to add a small alert in the docs saying that this change is not necessary anymore. \n\n### Additional information\n\n- [X] 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).",[2897],{"name":2898,"color":2899},"documentation","5319e7",18927,"Documentation: Describe the new useFetch() behavior","2024-06-30T11:09:27Z","https://github.com/nuxt/nuxt/issues/18927",0.7573715,{"description":2906,"labels":2907,"number":2911,"owner":2872,"repository":2872,"state":2874,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### 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).",[2908],{"name":2909,"color":2910},"discussion","538de2",26018,"useFetch: refresh on window focus/activate","2024-06-30T11:05:32Z","https://github.com/nuxt/nuxt/issues/26018",0.75747186,{"description":2917,"labels":2918,"number":2921,"owner":2872,"repository":2873,"state":2874,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### 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.",[2919,2920],{"name":2866,"color":2867},{"name":2869,"color":2870},2061,"Allow using tab item key as value for v-model","2024-08-20T06:04:17Z","https://github.com/nuxt/ui/issues/2061",0.7594813,{"description":2927,"labels":2928,"number":2929,"owner":2872,"repository":2930,"state":2931,"title":2932,"updated_at":2933,"url":2934,"score":2935},"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.68555963,{"description":2937,"labels":2938,"number":2946,"owner":2872,"repository":2872,"state":2931,"title":2947,"updated_at":2948,"url":2949,"score":2950},"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 ",[2939,2940,2943],{"name":2898,"color":2899},{"name":2941,"color":2942},"good first issue","fbca04",{"name":2944,"color":2945},"3.x","29bc7f",15368,"Document `query` option for `useFetch`","2023-01-19T17:49:12Z","https://github.com/nuxt/nuxt/issues/15368",0.7273518,{"labels":2952,"number":2957,"owner":2872,"repository":2872,"state":2931,"title":2958,"updated_at":2959,"url":2960,"score":2961},[2953,2954],{"name":2944,"color":2945},{"name":2955,"color":2956},"pending triage","E99695",14328,"`useFetch` fired only once despite navigating back to the page","2023-01-19T17:33:49Z","https://github.com/nuxt/nuxt/issues/14328",0.7407712,{"description":2963,"labels":2964,"number":2967,"owner":2872,"repository":2872,"state":2931,"title":2968,"updated_at":2969,"url":2970,"score":2971},"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```",[2965,2966],{"name":2898,"color":2899},{"name":2944,"color":2945},27080,"Suggestion for useFetch Documentation: Add cache Option","2024-05-15T10:51:48Z","https://github.com/nuxt/nuxt/issues/27080",0.74505246,{"description":2973,"labels":2974,"number":2977,"owner":2872,"repository":2872,"state":2931,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### 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_",[2975,2976],{"name":2944,"color":2945},{"name":2955,"color":2956},19665,"useLazyFetch does not behave like useLazyAsyncData","2023-03-14T11:09:45Z","https://github.com/nuxt/nuxt/issues/19665",0.7465561,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fJB0P2f5afaA9OkgpsAvrOqduUKbmFyn0OL1hzEKL7Uw":-1},"/nuxt/fonts/471"]