\n\nconst items = ref([\n \"ok\",\n \"this one would not be ok because of how long it is\"\n])\n```\n\nThough, you could use something like Zod to do form validation, I think this could just apply a `maxlength` to the input itself to prevent typing more than the limit.\n\n### Additional context\n\n_No response_",[2975,2977],{"name":2919,"color":2976},"a2eeef",{"name":2936,"color":2937},4405,"InputTags max item length","2025-07-01T08:35:33Z","https://github.com/nuxt/ui/issues/4405",0.75972927,{"labels":2984,"number":2990,"owner":2909,"repository":2909,"state":2940,"title":2991,"updated_at":2992,"url":2993,"score":2994},[2985,2986,2987],{"name":2919,"color":2920},{"name":2962,"color":2963},{"name":2988,"color":2989},"app","17512D",11736,"`options.css` is not supported","2023-01-19T15:52:40Z","https://github.com/nuxt/nuxt/issues/11736",0.76189893,{"description":2996,"labels":2997,"number":2999,"owner":2909,"repository":2909,"state":2940,"title":3000,"updated_at":3001,"url":3002,"score":3003},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-zges3w?file=types%2Fapp.config.d.ts,app.vue,types%2Fvariables.d.ts\r\n\r\n### Describe the bug\r\n\r\nWhen referencing `theme` from `useAppConfig`, typescript should **always** allow both the `primary` and `secondary` type as possible values.\r\n\r\nThis should be possible by overriding the App Config Output as described here: https://nuxt.com/docs/guide/directory-structure/app-config#app-config-output.\r\n\r\nHowever, that does not work when using `extends` and only works when the `AppConfig` interface has the overriding types explicitly written out.\r\n\r\nStackblitz doesn't visibly show the error, but VS Code with the volar extensions does:\r\n\r\n\r\n### Additional context\r\n\r\nI use this pattern in a monorepo where there is a `base` layer with components that take in the config set by child sites.\r\n\r\nThis **does** work if `export {};` is **not** declared after `declare module '@nuxt/schema'`. However this will break types in `nuxt.config.ts`\r\n\r\n### Logs\r\n\r\n_No response_",[2998],{"name":2965,"color":2966},26116,"interface AppConfig does not take types when using `extends`","2024-12-16T12:46:25Z","https://github.com/nuxt/nuxt/issues/26116",0.76375,{"description":3005,"labels":3006,"number":3011,"owner":2909,"repository":2939,"state":2940,"title":3012,"updated_at":3013,"url":3014,"score":3015},"### Description\n\nIn our project, we aim to standardize the size of components across the application for consistency and maintainability. However, it seems there isn't a straightforward way to configure the default size for all inputs using app.config.",[3007,3010],{"name":3008,"color":3009},"question","d876e3",{"name":2936,"color":2937},2973,"How to allow customization of default components sizes via app.config?","2024-12-26T16:30:20Z","https://github.com/nuxt/ui/issues/2973",0.76599675,{"labels":3017,"number":3023,"owner":2909,"repository":2909,"state":2940,"title":3024,"updated_at":3025,"url":3026,"score":3027},[3018,3019,3020],{"name":2962,"color":2963},{"name":2933,"color":2934},{"name":3021,"color":3022},"nitro","bfd4f2",12837,"It looks like #config isn't defined for TypeScript?","2023-01-19T16:37:25Z","https://github.com/nuxt/nuxt/issues/12837",0.7663297,["Reactive",3029],{},["Set"],["ShallowReactive",3032],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f1U39-UF5tr8vmZzamE1QxKsNuEerkF8Wk976oa-NrcY":-1},"/nuxt/ui/4409"]