\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[2024,2026],{"name":1985,"color":2025},"a2eeef",{"name":2027,"color":2028},"triage","ffffff",3868,"ui","Allow assigning IDs to Nuxt UI Tab panels for scroll targeting","2025-04-12T08:35:52Z","https://github.com/nuxt/ui/issues/3868",0.7329772,{"description":2036,"labels":2037,"number":2042,"owner":1994,"repository":2030,"state":1995,"title":2043,"updated_at":2044,"url":2045,"score":2046},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.2\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules\n- Runtime Modules: @nuxt/ui@2.21.0\n- Build Modules: -\n\n### Version\n\nv2.21.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-kt7kxa75?file=app.vue\n\n### Description\n\nThe position of the arrow of a tooltip which is used inside a popover appears in the wrong position if the `top` placement is used\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2038,2041],{"name":2039,"color":2040},"bug","d73a4a",{"name":2027,"color":2028},3164,"Bug on tooltip arrow position if inside a popover","2025-01-23T09:36:39Z","https://github.com/nuxt/ui/issues/3164",0.73643833,{"labels":2048,"number":2055,"owner":1994,"repository":1994,"state":2056,"title":2057,"updated_at":2058,"url":2059,"score":2060},[2049,2052],{"name":2050,"color":2051},"3.x","29bc7f",{"name":2053,"color":2054},"pending triage","E99695",14292,"closed","Respect dynamic params when calling `refresh()` returned by `useFetch`","2023-01-19T17:32:45Z","https://github.com/nuxt/nuxt/issues/14292",0.6798788,{"description":2062,"labels":2063,"number":2065,"owner":1994,"repository":2030,"state":2056,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### Description\n\n### Use Case\nWhen using UTable with expandable rows alongside row-click navigation, it's currently impossible to prevent the expand action from triggering the row navigation. A custom slot would allow users to implement `@click.stop` on the expand button, separating its behavior from row clicks.\n\n### Example of Desired Usage\n```vue\n\u003CUTable :rows=\"rows\" :columns=\"columns\" @row-click=\"navigateToPage\">\n \u003Ctemplate #expand-btn=\"{ expanded, toggle }\">\n \u003Cbutton @click.stop=\"toggle\">\n {{ expanded ? 'Collapse' : 'Expand' }}\n \u003C/button>\n \u003C/template>\n\u003C/UTable>\n```\n\nI'd also like to take this opportunity to add another suggestion : Implement a way to control expandability on a per-row basis.\n\nThanks\n\n### Additional context\n\n_No response_",[2064],{"name":1985,"color":2025},2301,"Expand Button Slot for UTable","2024-11-05T16:13:52Z","https://github.com/nuxt/ui/issues/2301",0.6871749,{"description":2071,"labels":2072,"number":2074,"owner":1994,"repository":1994,"state":2056,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Describe the feature\n\n**Problem:** Nuxt currently lacks an integrated way to make query parameters reactive. Although useRoute().query provides access to query parameters, it is not reactive, which limits dynamic updates when the query parameter changes.\nA common solution in Vue is to use useUrlSearchParams() from VueUse; however, this approach isn’t compatible with SSR, which is essential in many Nuxt applications.\n\n**Proposed Solution:** Add a new composable which makes query parameters reactive without sacrificing SSR compatibility, like this:\n```ts\nfunction useRouteQuery(id: string) {\n const route = useRoute()\n const router = useRouter()\n return computed({\n get: () => route.query[id],\n set: (value) => {\n router.push({ query: { ...route.query, [id]: value } })\n },\n })\n}\n```\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).",[2073],{"name":2053,"color":2054},29861,"feat: Add Reactive Query Parameters in Nuxt with SSR Compatibility","2024-11-20T13:40:06Z","https://github.com/nuxt/nuxt/issues/29861",0.7080673,{"description":2080,"labels":2081,"number":2083,"owner":1994,"repository":1994,"state":2056,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: -\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\n[https://stackblitz.com/edit/nuxt-starter-bpyqqk?embed=1&file=pages%2Fbad.vue](url)\n\n\n**good case**\n\n```\nconst ss_sl = ref(0);\n// useGoodSSRFetch defined in composables\nconst { data, error, refresh } = useGoodSSRFetch(\n 'https://api.kuleu.com/api/suijimima',\n 'GET',\n { ss_sl } // The parameter type is: ref\n);\n\nconst next = async () => {\n ss_sl.value++;\n console.log('count-->', ss_sl.value);\n\n refresh();\n};\n```\n\n**bad case**\n```\nconst ss_sl = ref(0);\n// useBadSSRFetch defined in composables\nconst { data, error, refresh } = useBadSSRFetch(\n 'https://api.kuleu.com/api/suijimima',\n 'GET',\n { ss_sl: ss_sl.value } // The parameter type is: value\n);\n\nconst next = async () => {\n ss_sl.value++;\n console.log('count-->', ss_sl.value);\n\n refresh();\n};\n```\n\n### Describe the bug\n\nI encapsulated the useAsyncData function under ‘composables’, and the call in the vue file was successful and I got the first page data, but when I wanted to get the second page data via 'refresh', I found that if the 'page' parameter is of the value type, I can only get the first page forever, but if the input parameter is a ref, I can get the subsequent pages normally.\n\n我在‘composables’目录下对‘useAsyncData’进行了封装,在vue文件中成功调用并得到了第1页数据,但当我想通过‘refresh’获取第2页数据时,我发现如果传入的'page'参数是值类型时,虽然我修改了'page'参数的值为2,但我仍然获取到第1页;但如果传入参数是ref类型则可以正常获取后续的页面。\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2082],{"name":2053,"color":2054},29846,"useAsyncData cannot be refreshed with ref-value in 'composables'","2024-12-19T13:54:49Z","https://github.com/nuxt/nuxt/issues/29846",0.7157552,{"description":2089,"labels":2090,"number":2097,"owner":1994,"repository":2030,"state":2056,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2091,2094],{"name":2092,"color":2093},"question","d876e3",{"name":2095,"color":2096},"v3","49DCB8",3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.7206395,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"mjI2cy2L3bc_22OV-vfavx-XSSWhzX8Adl8EAaARR9E":-1},"/nuxt/ui/3398"]