\n \u003C/template>\n\u003C/UModal>\n```\n\n\n### Description\n\nselect menu's search input always autofocus inside modal, even when the autofocus is set to false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2017,2020,2021],{"name":2018,"color":2019},"bug","d73a4a",{"name":2006,"color":2007},{"name":2022,"color":2023},"triage","ffffff",3933,"SelectMenu's autofocus doesn't work inside Modal","2025-04-19T06:22:26Z","https://github.com/nuxt/ui/issues/3933",0.7405083,{"description":2030,"labels":2031,"number":2036,"owner":1994,"repository":1994,"state":1995,"title":2037,"updated_at":2038,"url":2039,"score":2040},"### Describe the feature\r\n\r\nThe assert version of [isDefined](https://vueuse.org/shared/isDefined/#isdefined).\r\nOften when creating a page and fetching data (f.e. using `useFetch`) it is needed to show error page when there is no data or the error happened on the server. Currently we have to do something like this to assert data in the runtime and TS:\r\n```ts\r\nconst { data, error } = await useFetch('/api/...')\r\nif (!isDefined(data)) throw createError(error.value!)\r\n// data value is not null here, and in the template \r\n// for both runtime and TS\r\n```\r\nAs you can see we should use nullish assertion for either `data` or `error`:\r\nI suggest to add another `assertData` util which can be used like this:\r\n```ts\r\nconst { data, error } = await useFetch('/api/...')\r\nassertDefined(data, error)\r\n// data value is not null here, and in the template \r\n// for both runtime and TS\r\n```\r\nUnder the hood, simplified version (for refs only):\r\n```ts\r\nfunction assertDefined\u003CT>(data: Ref\u003CT>, error): asserts data is Ref\u003CExclude\u003CT, null | undefined>> {\r\n const _error = toValue(error)\r\n if (!toValue(data) && _error) throw createError(_error)\r\n}\r\n```\r\nwhile I doubt whether it will somehow improve DX 🤔\r\n\r\nAlso it would be great to add an option to make `fatal = true` by default for createError. \r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2032,2033],{"name":1985,"color":1986},{"name":2034,"color":2035},"discussion","538de2",26106,"`assertDefined` utility","2024-06-30T11:05:27Z","https://github.com/nuxt/nuxt/issues/26106",0.7405604,{"description":2042,"labels":2043,"number":2054,"owner":1994,"repository":1994,"state":1995,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### Environment\n\n```BASH\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.19.1`\r\n- Nuxt Version: `3.3.1`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@8.19.3`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `app`, `css`, `postcss`, `modules`, `typescript`\r\n- Runtime Modules: `@pinia/nuxt@0.4.7`, `@vueuse/nuxt@9.13.0`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\n\n### Reproduction\n\nMust use Nuxt 3.3, it doesnt error on lower versions.\r\n```TS\r\n// server/api/something/[id]/index.get.ts\r\nexport default defineEventHandler(async (event) => {\r\n return event.context.params.id; // 'event.context.params' is possibly 'undefined'.\r\n})\r\n```\r\nSee: https://codesandbox.io/p/github/nuxt/starter/csb-gjy45g/draft/admiring-brown\n\n### Describe the bug\n\nWhen accessing event.context.params nuxt throws an error saying it's possibly undefined when it's nested under a dynamic route, and thus, cannot be undefined.\r\n\r\nFor example, if I GET https://gjy45g-3000.csb.app/api/something/213/ using the above mentioned reproduction `event.context.params` will always have 1 key, id, and it's value is 213. `event.context.params` shouldn't be marked as possibly undefined in this event as it will never be undefined.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2044,2045,2048,2051],{"name":1985,"color":1986},{"name":2046,"color":2047},"types","2875C3",{"name":2049,"color":2050},"nitro","bfd4f2",{"name":2052,"color":2053},"🍰 p2-nice-to-have","0E8A16",19871,"Server routes event.context.params typed incorrectly","2024-06-30T11:09:12Z","https://github.com/nuxt/nuxt/issues/19871",0.743363,{"description":2060,"labels":2061,"number":2066,"owner":1994,"repository":2009,"state":2067,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### 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```",[2062,2065],{"name":2063,"color":2064},"question","d876e3",{"name":2006,"color":2007},3294,"closed","UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.6935884,{"description":2073,"labels":2074,"number":2078,"owner":1994,"repository":2009,"state":2067,"title":2079,"updated_at":2080,"url":2081,"score":2082},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.12.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@10.6.2\n- Builder: -\n- User Config: modules, css, runtimeConfig, uiPro, compatibilityDate, devtools, future, experimental\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/ui-pro@3.0.0, @nuxt/content@3.3.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```html\n\u003CProsePre lang=\"yaml\">{{ yaml }}\u003C/ProsePre>\n```\n\n\n### Description\n\nMade sure I have content installed and loaded - renders just fine, copy button shows the ✅ - but nothing is copied\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2075,2076,2077],{"name":2018,"color":2019},{"name":2006,"color":2007},{"name":2022,"color":2023},3545,"Clipboard button doesnt copy content when using ProsePre directly","2025-03-13T00:31:04Z","https://github.com/nuxt/ui/issues/3545",0.7028868,{"description":2084,"labels":2085,"number":2090,"owner":1994,"repository":1994,"state":2067,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### What problem does this feature solve?\r\n\r\nThe main problem I am experiencing is the unnecessary query parameters inside `$router.replace()`. Now, assuming I am inserting multiple parameters or a JSON object inside the `query:`, some of the paramters might have null, undefined or empty values. It would be great if we had an option to simply avoid showing these parameters in the URL if they are not wanted.\r\n\r\n### What does the proposed changes look like?\r\n\r\nAs an example I have the below `replace()`\r\n```\r\nconst hasBrandQuery = 'brandIds: 5'\r\nconst hasProductQuery = null\r\nthis.$router.replace({\r\n query: {\r\n hasBrandQuery,\r\n hasProductQuery\r\n }\r\n})\r\n```\r\nThe problem I have with the code above is that I don't want `hasProductQuery` to be shown in my URL, simply because it has no specific value and it should only show `hasBrandQuery`.\r\nI think this would be a good feature if we had an option to enable such a thing.\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8879\">#c8879\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2086,2087],{"name":1985,"color":1986},{"name":2088,"color":2089},"2.x","d4c5f9",5305,"$router Optional query parameters ","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/5305",0.7109265,{"description":2096,"labels":2097,"number":2103,"owner":1994,"repository":1994,"state":2067,"title":2104,"updated_at":2105,"url":2106,"score":2107},"### Describe the feature\n\nWhen using the `useRoute` composable, the route params aren't beeing typed.\r\nI'm in the folder's path `pasges/me/[id].vue` and when I type the code below, the `id` insn't in the vscode completition.\r\n\r\n```javascript\r\n\u003Cscript setup>\r\nconst route = useRoute();\r\nconsole.log(route.params.id) // id isn't in the vscode completition\r\n\u003C/script>\r\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).",[2098,2099,2102],{"name":1985,"color":1986},{"name":2100,"color":2101},"3.x","29bc7f",{"name":2052,"color":2053},20299,"Route params typefication","2023-05-18T09:59:31Z","https://github.com/nuxt/nuxt/issues/20299",0.72986543,{"description":2109,"labels":2110,"number":2112,"owner":1994,"repository":2009,"state":2067,"title":2113,"updated_at":2114,"url":2115,"score":2116},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v20.16.0\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.13.2\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.8.1\r\n- Builder: -\r\n- User Config: future, compatibilityDate, runtimeConfig, routeRules, app, devtools, css, modules, plugins, build, i18n, pinia, image, icon, ui, schemaOrg\r\n- Runtime Modules: @pinia/nuxt@0.5.4, @nuxtjs/i18n@8.5.5, @nuxtjs/device@3.2.4, @nuxt/image@1.8.0, @formkit/auto-animate/nuxt@0.8.2, @vueuse/nuxt@11.1.0, @nuxt/ui@2.18.6, nuxt-lodash@2.5.3, @pinia-plugin-persistedstate/nuxt@1.2.1, nuxt-schema-org@3.4.0, nuxt-gtag@2.1.0\r\n- Build Modules: -\r\n\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-im7dek?file=app.vue\n\n### Description\n\nUSelectMenu :option-attribute does not handle nested objects with dot.notation as described in the docs\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2111],{"name":2018,"color":2019},2247,"USelectMenu :option-attribute does not handle nested objects","2024-11-07T14:10:37Z","https://github.com/nuxt/ui/issues/2247",0.7360673,["Reactive",2118],{},["Set"],["ShallowReactive",2121],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"i5InhazUAyWS5j1HaoeuIsRep4SYOzeWjmAhprUXPdc":-1},"/nuxt/ui/3050"]