\r\n```\r\nJust like `trim` and `number` trims the value or coerces to a number respectively.\r\n\r\n### Additional context\r\n\r\nThis PR depends on allowing `null` as initial value as implemented in (#2275)",[2012],{"name":2013,"color":2014},"enhancement","a2eeef",2281,"ui","closed","Input/Textarea nullify modifier","2024-10-23T20:24:45Z","https://github.com/nuxt/ui/issues/2281",0.70507145,{"description":2023,"labels":2024,"number":2025,"owner":1994,"repository":2026,"state":2017,"title":2027,"updated_at":2028,"url":2029,"score":2030},"Each time the project is restarted or changed, the following error occurs:\n\n WARN Could not fetch from https://fonts.google.com/metadata/icons?key=material_symbols&incomplete=true. Will retry in 1000ms. 3 retries left. 19:30:58 \n\n\n WARN Could not fetch from https://fonts.google.com/metadata/icons?key=material_symbols&incomplete=true. Will retry in 1000ms. 2 retries left. 19:31:09 \n\n\n WARN Could not fetch from https://fonts.google.com/metadata/icons?key=material_symbols&incomplete=true. Will retry in 1000ms. 1 retries left. 19:31:20 \n\n\n ERROR Could not initialize provider googleicons. unifont will not be able to process fonts provided by this provider. fetch failed \n ERROR Could not initialize provider googleicons. unifont will not be able to process fonts provided by this provider. fetch failed",[],424,"fonts","Could not initialize provider googleicons. unifont will not be able to process fonts provided by this provider. fetch failed","2025-03-17T08:56:47Z","https://github.com/nuxt/fonts/issues/424",0.7317142,{"description":2032,"labels":2033,"number":2040,"owner":1994,"repository":2016,"state":2017,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### Environment\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: 2.9.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/aloulouamine/nuxt-ui-select-menu-issue\n\n### Description\n\nSelectMenu with paginated search has an issue with default count placeholder.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2034,2037],{"name":2035,"color":2036},"bug","d73a4a",{"name":2038,"color":2039},"duplicate","cfd3d7",2313,"SelectMenu paginated search count issue","2024-10-06T17:49:40Z","https://github.com/nuxt/ui/issues/2313",0.7530383,{"description":2046,"labels":2047,"number":2050,"owner":1994,"repository":2051,"state":2017,"title":2052,"updated_at":2053,"url":2054,"score":2055},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_10_20_at_11_27_53_d9d9a13fb1.mp4\n",[2048],{"name":2035,"color":2049},"ff281a",1004,"nuxt.com","Responsive (mobile & tablet): back to top of nav ","2023-10-10T14:45:28Z","https://github.com/nuxt/nuxt.com/issues/1004",0.7543981,{"description":2057,"labels":2058,"number":2065,"owner":1994,"repository":2016,"state":2017,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### Description\n\nHello, we are currently a small team using nuxt UI pro version 2. We've seen that the new Nuxt UI 3 version is in alpha and we'd like to know if a stable release is planned soon?\n\nWe've seen that Nuxt UI 3 is going to take a long time to migrate and we'd like to start work quickly. Do you think it's cost-effective to make the switch now, or is it better to wait for a more stable version?\n\nThanks for reading ^^",[2059,2062],{"name":2060,"color":2061},"question","d876e3",{"name":2063,"color":2064},"v3","49DCB8",3371,"Nuxt UI V3 official release date","2025-02-21T09:22:07Z","https://github.com/nuxt/ui/issues/3371",0.76217586,{"description":2071,"labels":2072,"number":2075,"owner":1994,"repository":2016,"state":2017,"title":2076,"updated_at":2077,"url":2078,"score":2079},"### Description\n\nJust tried to implement my first form that does some smaller frontend validation and sends the payload to an API that will escalate errors as well.\n\nGoing through all the use cases, some are rather hard and cumbersome to implement:\n\n- Field validation errors are fine\n- Form errors require a field to work, there is no way to define Form wide errors through `Form.setErrors()` nor do they bubble up to a general error display just where the `\u003CUForm />` is anchored if the key is unknown.\n- The missing error bubbeling makes it tricky to react to more common errors like rate limiting through 429 status code, where the server responds with additional headers and maybe a JSON with further information. This creates a hard coupling of the loose backend error message and a hard field within the current form to route the error to.\n\nAlso the submission event `FormSubmitEvent` could offer better developer experience by offering not only data, but the actual Form instance. Right now, to handle any errors by a backend, you need to go through the typical, type-messy approach of\n\n```ts\n\u003Ctemplate>\n \u003CUForm ref=\"form\" @submit=\"onSubmit\" />\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\ntype FormSchema = v.InferOutput\u003Ctypeof CreateSomethingForm>\n\nconst form = useTemplateRef\u003CForm\u003CFormSchema>>('form')\n\nasync function onSubmit(event: FormSubmitEvent\u003CFormSchema>) {\n\n form.value?.setErrors([\n {name: 'account', message: 'Not valid'}\n ])\n}\n\u003C/script>\n```\n\ninstead of a simpler boilerplate:\n\n```ts\n\u003Ctemplate>\n \u003CUForm @submit=\"onSubmit\" />\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\ntype FormSchema = v.InferOutput\u003Ctypeof CreateSomethingForm>\n\nasync function onSubmit(event: FormSubmitEvent\u003CformSchema>) {\n event.form.setErrors([\n {name: 'account', message: 'Not valid'}\n ])\n}\n\u003C/script>\n```\n\n\n\n\n### Additional context\n\n_No response_",[2073,2074],{"name":2013,"color":2014},{"name":2063,"color":2064},3471,"Form improvements","2025-03-12T08:31:46Z","https://github.com/nuxt/ui/issues/3471",0.76934224,{"description":2081,"labels":2082,"number":2084,"owner":1994,"repository":2016,"state":2017,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Description\r\n\r\nFrom the documentation, it does not seem apparent, but it is a useful and common feature to have hover animations over each row in the table with a pointer cursor. The convention is to do something (like go to a separate page) if the user clicks anywhere in the entire row.\r\n\r\n```html\r\n\u003Ctemplate>\r\n \u003CUTable :columns=\"columns\" :rows=\"people\" @click=\"handleRowClick\" />\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst handleRowClick = (person: any): void => {\r\n navigateTo(`/people/${person.id}`)\r\n}\r\n\r\nconst columns = [{\r\n key: 'id',\r\n label: 'ID'\r\n}, {\r\n key: 'name',\r\n label: 'User name'\r\n}, {\r\n key: 'title',\r\n label: 'Job position'\r\n}, {\r\n key: 'email',\r\n label: 'Email'\r\n}, {\r\n key: 'role'\r\n}]\r\n\r\nconst people = [{\r\n id: 1,\r\n name: 'Lindsay Walton',\r\n title: 'Front-end Developer',\r\n email: 'lindsay.walton@example.com',\r\n role: 'Member'\r\n}, {\r\n id: 2,\r\n name: 'Courtney Henry',\r\n title: 'Designer',\r\n email: 'courtney.henry@example.com',\r\n role: 'Admin'\r\n}]\r\n\u003C/script>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_",[2083],{"name":2013,"color":2014},2156,"[UTable] should have a field to enable hover animations and make them clickable","2024-09-10T16:29:52Z","https://github.com/nuxt/ui/issues/2156",0.76995134,{"description":2090,"labels":2091,"number":2096,"owner":1994,"repository":1994,"state":2017,"title":2097,"updated_at":2098,"url":2099,"score":2100},"### Environment\n\n- Operating System: Linux (WSL)\r\n- Node Version: v18.16.0\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.4.0\r\n- Package Manager: npm@9.5.1\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\n1. npx nuxi init my-app\r\n2. cd my-app\r\n3. npm i\r\n4. npm run generate\n\n### Describe the bug\n\nWhen opening the `index.html` file of a static build, resource paths cannot be resolved. This might be a config issue or a system env issue but I think it's odd that with a fresh build this does not work. I couldn't find any direct mentions of how to avoid this in the docs.\r\n\r\nThis issue is present both when I open the file in WSL with a path like this: `file://wsl.localhost/Ubuntu/home/myHomeDir/test-app/.output/public/index.html` and also after I moved the directory to Windows filesystem with a path like this: `file:///C:/Users/MyUserName/Desktop/public/index.html`\r\n\r\nI noticed that the generated tags all have absolute pathing instead of relative. I'm assuming it's for a reason, seeing that I couldn't find any directly related issues. But how would this even work?\r\n\r\n\n\n### Additional context\n\nI wanted to test SSG with the end goal of moving the generated files to some directory and serving them via Nginx. FWIW, I might be misunderstanding this situation but from where I am standing I would expect this to work.\n\n### Logs\n\n_No response_",[2092,2095],{"name":2093,"color":2094},"3.x","29bc7f",{"name":1985,"color":1986},20740,"Static files fail to resolve resource paths","2023-05-09T11:27:34Z","https://github.com/nuxt/nuxt/issues/20740",0.7699559,["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"yxhV-p5GamP4OozeiPg4mJTYBxJKqu8bIV-SLfULOCI":-1},"/nuxt/ui/2882"]