As the saying goes, “After the bitter comes the sweet”, and after a while of silence, we have some good news.

Our project lead Damian has made some very good progress on rewriting the library from scratch using the new Vue Composition API, while still keeping the API relatively close to the current version of Vuelidate. This means the current, model oriented, options-based approach to declaring validations will stay as it is.

The time has come to ask you, the users, what do you find annoying, hard, or just missing from Vuelidate? What would you like us to change or implement?

The project has reached a prototyping phase, where we are open for suggestions, changing the API, to improve the experience for you, the users.

Please leave a ticket, explaining what your idea is and your proposed change, using the RFC template in the Vuelidate Issues. The process will go for a week or two, after which we will close further submissions, go through and filter the feasible ideas.

We are very excited about the future of Vuelidate, and hope so are you!

Link to Issues
Post your Idea