[Suggestion] Other validators / contrib?

Had a couple of suggestions for common validators in an corporate setting:

• IP fields (v4 / v6)
• MAC address

I’d imagine these are common enough in usage that a common implementation would be helpful; however, I can understand not wanting to bloat the core library. If it’s unacceptable to have these in the core library, would you consider a wiki or other piece of documentation that links to external open source validators? For example, if I could push something like vuelidate-ip-validator to GitHub, it would seen sensible to have that referred to here to prevent others writing their own implementations.

Thanks

[Frizi]

Sure, though you are free to use any exiting library that provide validation functions, treating the vuelidate only as a validation engine. The only additional thing that could be added specifically for vuelidate is withParams usage, so you can get the feedback from validator function about it’s configuration. This is optional though, useful only when you plan to use $params property.

Validators are already separate from the core anyway. The only problem is that “web” bundle contains them all in single file, validators.min.js, so you can’t opt-out from using them. Having them in separate files would help and we can continue to add even less frequently used validators to this repo. I’m not sure if splitting the packages is necessary and any beneficial. It’s not as general purpose as lodash for example.

BTW, I’m actually using exactly IP fields and mac addresses in my project with Vuelidate 😄

[robcresswell]

Oh, fantastic. Thanks so much!