\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[3190,3191,3194],{"name":3151,"color":3152},{"name":3192,"color":3193},"needs reproduction","CB47CF",{"name":3195,"color":3196},"v3","49DCB8",3546,"ui","`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.7171521,{"description":3204,"labels":3205,"number":3212,"owner":3140,"repository":3198,"state":3175,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nI've defined my custom color in `app.vue`:\n```\n\u003Cstyle>\n@theme {\n --color-foobar-50: #f3f1ff;\n --color-foobar-100: #ebe5ff;\n...\n```\nand defined this as primary color in `app.config.ts`:\n```\nexport default defineAppConfig({\n ui: {\n colors: {\n primary: 'foobar',\n...\n```\n\nThis causes a type error:\n> Type '\"foobar\"' is not assignable to type 'Color | undefined'.\n\nThe only workaround seems to be `'foobar' as any`. However, I'd like to avoid both `as` and `any` in my code base.\n\n### Additional context\n\n_No response_",[3206,3209,3211],{"name":3207,"color":3208},"duplicate","cfd3d7",{"name":3172,"color":3210},"a2eeef",{"name":3195,"color":3196},2531,"Allow custom colors in app.config.ts","2024-11-13T12:09:04Z","https://github.com/nuxt/ui/issues/2531",0.7177097,{"description":3218,"labels":3219,"number":3220,"owner":3140,"repository":3174,"state":3175,"title":3221,"updated_at":3222,"url":3223,"score":3224},"Multiple links in showcase links to either dead sites or dead pages on the sites. I have attached a few. Also the russian mcdonalds site is on there\r\nhttps://mcdonalds.ru/\r\nhttps://ai.marketing/user/robot\r\nhttps://game.fonts.adobe.com/\r\nhttps://annual.awwwards.com/\r\nhttps://globalmaintainersummit.github.com/\r\nhttps://vintageria.it/\r\nhttps://hyundaiusa.com/",[],1530,"Dead showcase links","2024-03-11T22:26:22Z","https://github.com/nuxt/nuxt.com/issues/1530",0.7238909,{"description":3226,"labels":3227,"number":3231,"owner":3140,"repository":3140,"state":3175,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### Environment\r\n\r\nStackblitz\r\n\r\n### Reproduction\r\n\r\n1. Open [Vue Playground Link](https://play.vuejs.org/#eNp9U1tP2zAU/itHfmk6lRQoT12pxrY+MImLBtsLRlOanBSDY2eOXYqq/PcdO2nacakURcc+1+87n9fsrCzjpUM2ZpMqNaK0UKF15ZQrUZTaWFiDwXwAz4lNH2Z5jqmFGnKjC+hRXq+Lu3j5pslSqGzrjoc7d74JBXOValVZsFjZM2Pg1FeP7tYgsjEcQT2gft483pqjrXkC9X2fq51ZoqgPp1PwRbXEWOpF1JaOl4l0OIDe1a/bm/Pvs16fMifDBiTBo4PFopSJRToBTHYBLA8KnaEc+1oHiTGnnLVlOYMhxU+GXTIbsFc4X5MJMlELX6LibJfYjzj9zJV9KRFuqeXV/JFIauArV8zRQP2WxAxzofDCzzxps+7up1Gvjeh5Ag3+dcIg1bHGIdREB1e5U6kVWoErMwJDscnLTGJBSCKhMlxtug5AqFyP4ToxViRdl2kf1p69/0i/C5n3fm7vA4jj+L2AQef1tcOJsNG3AZjh3C1++wyq1Wz6nTmPN/K4SOxDnEutTRRMk6hMF5T36ejwsN8ifiueMOQ+BZ1fNgKivdT+t09FmVgGg8y5s5aY/ZJKkT7R+rdoggx8DMANktrCXZM0bLJa/3rdLbkmXry/abCjP65IgbYiALlYxI+VVqS/gImzlGQpJJqr0i+Z5DferISzREr9/CPceUG0y6CcB0yf3rl/rFb+jrNrgxWaJaHofDYxC7SNe3ZziSuyOyc9JScpeo/zJxL5zs/YhH11KqOxd+LCtOfh5Qi1uK1mK4uq2oDygwb5hHjO6BX5F/kR9O24o3i0kR2x+GeJxtckAkfxSTwasfof0HG4/Q==)\r\n2. Click on \"Set value\"\r\n3. Check the console and see that watchEffect was triggered (\"outside\" and \"inside\")\r\n\r\nNow with Nuxt 🙈 \r\n\r\n1. Open the [Stackblitz](https://stackblitz.com/edit/nuxt-issues-28240)\r\n2. Click on \"Set Value\"\r\n3. Check the console -> watchEffect **was not triggered**, neither \"outside\" nor \"inside\"\r\n\r\n### Describe the bug\r\n\r\nI am not sure why the behavior is different than in plain Vue but somehow, even with `ssr: false`, the update event of `defineModel` is never fired when using an array ref as value and modifying an element of the array.\r\n\r\n### Additional context\r\n\r\nusing `watch` + `deep` (in either inside or outside) will trigger properly.\r\n\r\n### Logs\r\n\r\n_No response_",[3228],{"name":3229,"color":3230},"pending triage","E99695",28240,"defineModel behavior for `ref` arrays differs from plain Vue","2024-07-22T08:30:11Z","https://github.com/nuxt/nuxt/issues/28240",0.72821826,{"description":3237,"labels":3238,"number":3241,"owner":3140,"repository":3198,"state":3175,"title":3242,"updated_at":3243,"url":3244,"score":3245},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nAs of now, in Nuxt UI v3.0.0-alpha.x, the `SIDE_OPTIONS` constant is defined as follows:\n\n``` ts\nconst SIDE_OPTIONS: [\"top\", \"right\", \"bottom\", \"left\"];\n```\n\nThe current four directions cannot meet the practical development needs. For example, when there is a button on the far right of the screen to open a dropdown menu, it cannot automatically appear as 'bottom-right'.Tooltips, dropdown menus, or popovers may require positioning beyond the basic cardinal directions to avoid obscuring content or to better fit within the viewport.\n\n#### Proposed Enhancement\n\nI propose to extend the SIDE_OPTIONS constant to include combinations of the cardinal directions to allow for greater flexibility and finer control over positioning. The updated SIDE_OPTIONS would be:\n\n``` ts\nconst SIDE_OPTIONS = [\n \"top\", \"right\", \"bottom\", \"left\",\n \"bottom-left\", \"bottom-right\",\n \"left-top\", \"left-bottom\",\n \"top-left\", \"top-right\",\n \"right-top\", \"right-bottom\"\n];\n```\n\n\n### Additional context\n\n| | |\n| ----------- | ----------- |\n|  | |\n\n\n",[3239,3240],{"name":3172,"color":3210},{"name":3195,"color":3196},2712,"Side needs more direction","2024-11-20T19:59:29Z","https://github.com/nuxt/ui/issues/2712",0.7283722,["Reactive",3247],{},["Set"],["ShallowReactive",3250],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fln11kzOHvoOzB5aaOjxf6iy42tXfrQKgLHlG6nDYSaQ":-1},"/nuxt/scripts/334"]