\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[2885,2888],{"name":2886,"color":2887},"enhancement","a2eeef",{"name":2869,"color":2870},4139,"USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.7608368,{"description":2895,"labels":2896,"number":2902,"owner":2875,"repository":2875,"state":2877,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Describe the feature\n\nHey all 👋🏻\r\n\r\nWe have `defineCachedEventHandler` for custom event handlers from Nitro, e.g. for API endpoints. The only scenario where we can't use these at the moment is the main Server-Side Rendering handler as it is not under the end users control.\r\n\r\nI propose a hook to have the option to insert custom code which should be able to configure the handler's options.\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,2899],{"name":2886,"color":2898},"8DEF37",{"name":2900,"color":2901},"nitro","bfd4f2",26598,"Fine-grained config of the SSR renderer's Nitro event handler via hook","2025-02-16T04:30:40Z","https://github.com/nuxt/nuxt/issues/26598",0.7676071,{"description":2908,"labels":2909,"number":2916,"owner":2875,"repository":2875,"state":2917,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Describe the feature\n\nThe event emitter & listener should be a built-in feature because it's so important. Yes we can use a third party plugin like https://www.npmjs.com/package/mitt, but isn't it great that nuxt/vue 3 has this feature by default like nuxt/vue 2?\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).",[2910,2913],{"name":2911,"color":2912},"3.x","29bc7f",{"name":2914,"color":2915},"pending triage","E99695",19629,"closed","Event emitter & listener","2023-03-13T06:59:40Z","https://github.com/nuxt/nuxt/issues/19629",0.70639837,{"description":2923,"labels":2924,"number":2928,"owner":2875,"repository":2876,"state":2917,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Description\n\nI think a nice addition could be the method `isOpen(id: symbol): boolean` to check if an overlay opened programmatically is currently open.\nCan I get this assigned? I would like to open a PR about this :)\n\n### Additional context\n\n_No response_",[2925,2926,2927],{"name":2886,"color":2887},{"name":2869,"color":2870},{"name":2872,"color":2873},4007,"[useOverlay] add `isOpen` method","2025-05-01T16:48:42Z","https://github.com/nuxt/ui/issues/4007",0.7369657,{"description":2934,"labels":2935,"number":2938,"owner":2875,"repository":2876,"state":2917,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Description\n\nCurrently when I use useOverlay and pass props it says props is type any.\nby adding `satisfies InstanceType\u003Ctypeof COMPONENT>[\"$props\"]` it gets the right types.\n\nBut it should work out of the box. Could the typesafety for props be implemented?\n\ncurrent solution\n```\n useOverlay()\n .create(COMPONENT, {\n props: {\n id: id,\n onUpdated() {\n...\n },\n } satisfies InstanceType\u003Ctypeof COMPONENT>[\"$props\"],\n })\n .open();\n```\n\n### Additional context\n\nSomething like this could create type safety\n\n```\nfunction createTypedOverlay\u003CT extends new (...args: any) => any>(\n component: T,\n options: {\n props: InstanceType\u003CT>[\"$props\"];\n [key: string]: any;\n }\n) {\n return useOverlay().create(component, options);\n}\n```",[2936,2937],{"name":2866,"color":2867},{"name":2869,"color":2870},3915,"Typesafety on useOverlay props","2025-05-01T20:57:51Z","https://github.com/nuxt/ui/issues/3915",0.7433104,{"description":2944,"labels":2945,"number":2949,"owner":2875,"repository":2950,"state":2917,"title":2951,"updated_at":2952,"url":2953,"score":2954},"Don't we have too many links in Community section compared to `Resources`, `Company`...?",[2946],{"name":2947,"color":2948},"question","ff1ab2",825,"nuxt.com","[Community] Too many links","2022-11-17T11:43:46Z","https://github.com/nuxt/nuxt.com/issues/825",0.74546534,{"description":2956,"labels":2957,"number":2965,"owner":2875,"repository":2876,"state":2917,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Environment\n\n```\nNuxt project info: 4:13:17 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\n\nMy issue is pretty close to https://github.com/nuxt/ui/issues/468.\n\nIt's when you switch between different types of props on a component document that this issue occurs, the first time you enter it no such issue occurs.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2958,2959,2962],{"name":2866,"color":2867},{"name":2960,"color":2961},"documentation","0075ca",{"name":2963,"color":2964},"duplicate","cfd3d7",2429,"DOCS: You should use slots with \u003CContentRenderer>","2024-10-21T10:20:28Z","https://github.com/nuxt/ui/issues/2429",0.75038683,{"description":2971,"labels":2972,"number":2975,"owner":2875,"repository":2950,"state":2917,"title":2976,"updated_at":2977,"url":2978,"score":2979},"https://content-v2.nuxtjs.org/guide/writing/mdc#props\n\n",[2973],{"name":2866,"color":2974},"ff281a",496,"[Milkdown] On serialize, component props should keep their current format `inline` or `yaml`","2023-06-06T12:14:53Z","https://github.com/nuxt/nuxt.com/issues/496",0.7583746,{"description":2981,"labels":2982,"number":2975,"owner":2875,"repository":2986,"state":2917,"title":2987,"updated_at":2988,"url":2989,"score":2979},"",[2983],{"name":2984,"color":2985},"vitest-environment","b60205","test-utils","documentation/examples","2023-12-02T22:52:29Z","https://github.com/nuxt/test-utils/issues/496",["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSmwNJ6QOSL-EnZtxlAgjSFY1hiaXjk6yqNw70RS8vTQ":-1},"/nuxt/ui/3842"]