search

antoniandre / wave-ui

A UI framework for Vue.js 3 (and 2) with only the bright side. ☀️
https://antoniandre.github.io/wave-ui
MIT License
544 stars 39 forks source link

W-select issues #133

Closed R0N1n-dev closed 8 months ago

R0N1n-dev commented 8 months ago

Been trying to implement a select but having numerous issues and then docs are actually kind of missing on the specifics. I get errors. Think it as to do with model-value but do not even understand that part of the docs properly. The javascript examples(as few as they are) dont show the template usage. Screenshot from 2023-11-28 13-04-00 Screenshot from 2023-11-28 13-03-53 Screenshot from 2023-11-28 13-03-41

Don't know what to do. Some clarification on how to set them up would be appreciated

antoniandre commented 8 months ago

Hi @R0N1n-dev, I've created a Stackblitz for ya here: https://stackblitz.com/edit/waveui-3-wpxs6i?file=src%2FApp.vue where you can see a working w-select with Vue 3 and composition API. If this doesn't help you, please fork and update the above reproduction link and let me know.

In the future, please share your full code in a reproduction link. That will help me help you faster. ;)

R0N1n-dev commented 8 months ago

Had even given up on this issue. Picked another framework but OK https://stackblitz.com/github/R0N1n-dev/nuxt-issues for repro. (Good luck if you bother to look at it, the first thing you gonna get is config error.) Think this has to do with wave ui under the hood but its ur ui framework not mine, so you would know better. It is messing up my whole component including the operation of the cloudinary widget which i dont understand at all. Dont know how far with the nuxt module coz maybe this is coz its not setup for nuxt properly

I have tried the exact same component (my FORM component which contains the select) in nuxt projects with the following UI framworks: Vuetify, PrimeVue , Quasar and Inkline and none has presented the issue, so clearly it has to do with wave-ui implementation itself

AND THE really stupid part is if i keep stopping and restarting the dev server, sometimes it works with no issues,and then the error comes up again after making changes and saving or just simply reloading the page. Something is wrong under the hood but like i said, you would know better than me. But this is annoying at best.

It gives following error Screenshot from 2023-12-13 12-16-46

BTW it also gives the same error on attempting to use w-icon component always. Wave 3 docs really removed alot of js stuff. mostly see pug templates. This is just weird and dont see the reason for it.. Am literally guessing with certain components how to use them.