\n```",[2016,2019],{"name":2017,"color":2018},"question","d876e3",{"name":1988,"color":1989},3517,"How To Style NavigationMenu items","2025-03-14T13:01:49Z","https://github.com/nuxt/ui/issues/3517",0.71277446,{"description":2026,"labels":2027,"number":2032,"owner":1994,"repository":1995,"state":1996,"title":2033,"updated_at":2034,"url":2035,"score":2036},"",[2028,2031],{"name":2029,"color":2030},"feature","A27AF6",{"name":1988,"color":1989},2322,"[MeterGroup] Implement component","2025-04-07T09:36:44Z","https://github.com/nuxt/ui/issues/2322",0.7136445,{"description":2038,"labels":2039,"number":2042,"owner":1994,"repository":1995,"state":1996,"title":2043,"updated_at":2044,"url":2045,"score":2046},"### Description\n\nThank you very much for the best component library for Nuxt!\nMy question about the Table component (Tanstack)\nThe documentation has an example of how to send data received through fetch to a table, but there is no example for sorting and filtering using the Fetch call(\n\nThe documentation mentions columnFiltersOptions, but I don’t understand at all how to run my MYonColumnFiltersChange function when filters change( \n\n`\u003CUTable ref=\"table\" v-model:column-filters-options=\"MYonColumnFiltersChange \" />`\n\nit doesn't work that way\n\nI really ask for help!",[2040,2041],{"name":2017,"color":2018},{"name":1988,"color":1989},3098,"Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.71367836,{"description":2048,"labels":2049,"number":2052,"owner":1994,"repository":1995,"state":1996,"title":2053,"updated_at":2054,"url":2055,"score":2056},"### Description\n\nCurrently, when I use `UAvatar` and the user's photo returns a 404, it generates an `\u003Cimg>` with the broken image icon:\n\n\nIs there a way to make the image that returns 404 display text from the alt instead?\nIn the documentation it says:\n>When no icon or text is provided, the initials of the `alt` prop are used as fallback\n\nCan `alt` also be used as a fallback when the image is broken?\n\n\n\nExample:\n\n",[2050,2051],{"name":2017,"color":2018},{"name":1988,"color":1989},3809,"[UAvatar] If the image does not exist, return text","2025-04-06T16:07:33Z","https://github.com/nuxt/ui/issues/3809",0.71822125,{"description":2058,"labels":2059,"number":2063,"owner":1994,"repository":2008,"state":2064,"title":2065,"updated_at":2066,"url":2067,"score":2068},"- List modules\n- Install a module\n\nLink it in the modules section in concepts.\n",[2060],{"name":2061,"color":2062},"documentation","9DE2BA",1369,"closed","[API][Commands] Add `modules` ","2023-12-18T12:00:05Z","https://github.com/nuxt/nuxt.com/issues/1369",0.6974484,{"description":2070,"labels":2071,"number":2073,"owner":1994,"repository":1995,"state":2064,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### Environment\r\n\r\nnewest\r\n\r\n### Version\r\n\r\n^2.13.0\r\n\r\n### Reproduction\r\n\r\n`\u003CUTabs :ui=\"{strategy: 'override'}\">`\r\n\r\n### Description\r\n\r\nMake a UTabs component with an ui prop and set strategy as a string. Typescript will complain but it will render as intended\r\n\r\nTypes of property 'strategy' are incompatible.\r\nType 'string' is not assignable to type 'Strategy | undefined'\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2072],{"name":1985,"color":1986},2268,":ui prop typescript error with 'strategy' as a string","2024-09-30T09:51:02Z","https://github.com/nuxt/ui/issues/2268",0.701141,{"description":2079,"labels":2080,"number":2081,"owner":1994,"repository":2008,"state":2064,"title":2082,"updated_at":2083,"url":2084,"score":2085},"After using `pnpm update` to upgrade vue to 3.4.3, the console throws a lot of `Hydration mismatch`. If I am using vue 3.3.13, no `Hydration mismatch` warnings will be thrown.\r\n\r\n\u003Cimg width=\"1402\" alt=\"SCR-20240103-qagg\" src=\"https://github.com/nuxt/nuxt.com/assets/133459587/188ac1c4-e19a-4570-a5d0-4863c92a7bda\">\r\n",[],1467,"About vue@3.4.3 causing hydration mismatch","2024-05-03T00:34:36Z","https://github.com/nuxt/nuxt.com/issues/1467",0.7013542,{"description":2087,"labels":2088,"number":2092,"owner":1994,"repository":1995,"state":2064,"title":2093,"updated_at":2094,"url":2095,"score":2096},"### Description\n\nFor custom validation or for using the Form with Zod, etc. it would be great to have the common form field properties `touched` and `dirty` exposed.\n\n- `Touched` (opposite of `untouched`): A field is considered touched when a user has focused it OR changed it's value\n- `Dirty` (opposite of `pristine`): A field is considered dirty, if the value has changed (AND is different from its initial value). The second part is depending on the definition.\n\nYou can currently work around most of these by using a computed on the exposed `errors` ref and the state reactive, but for custom validation having these values natively exposed from the API would be very helpful.\n\n### Additional context\n\n_No response_",[2089,2091],{"name":2005,"color":2090},"a2eeef",{"name":1988,"color":1989},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.70316803,["Reactive",2098],{},["Set"],["ShallowReactive",2101],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"9a6TgToM58ZOAzz2sFkTlXEoHQc0exlfz_Lvvm8IXAc":-1},"/nuxt/ui/3652"]