[FEAT]: Use 'defineModel' for simpler v-model support in components

[snepsnepy]

Share your suggestion

Hey!

While I was looking on how "PreviewColor" component is implemented, I noticed it uses the tranditional modelValue/update:modelValue pattern.

I'd like to suggest updating the library to use the new 'defineModel' macro for v-model support. This change can make the codebase cleaner and simplify the pattern mentioned above.

Please let me know what do you think. Thanks!

Validations

• I have checked other issues to see if my issue was already discussed or addressed

[DavidHDev]

Hey! I'm honestly not that well-versed in Vue 3 best practices having worked with React most of my career, but that sounds like a good suggestion!

If you want to give it a shot and update it, go ahead. As long as the look and feel of the website is not affected, I'm completely fine with it.

[snepsnepy]

Makes sense, no worries! I'm not a guru either but I've worked more with Vue and seen some things along the way.

I'll take care of it, thanks for the reply!

[snepsnepy]

Should I do this update for all the component where required or do we want to tackle this in different PRs?

[DavidHDev]

@snepsnepy It can be done project-wide where it makes sense, I think it's faster 👍

[DavidHDev]

Merged in #28

This should be enforced from now on, so if anyone finds inconsistencies in any future PR, make sure to point that out!