Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Switch from vee-validate to vuelidate #334

Closed
taoeffect opened this issue Nov 26, 2017 · 0 comments
Closed

Switch from vee-validate to vuelidate #334

taoeffect opened this issue Nov 26, 2017 · 0 comments
Assignees
Labels
App:Frontend Kind:Core Anything that changes or affects the fundamental core data structures & design of the application. Kind:Enhancement Improvements, new features, performance upgrades, etc. Priority:High

Comments

@taoeffect
Copy link
Member

taoeffect commented Nov 26, 2017

Problem

  • vee-validate injects errors into every component (although this can apparently be disabled via the config by setting inject to false)
  • vee-validate has kinda an ugly API
  • vee-validate is huge, the main .min file is 72.2kb, and the minimal version is still a whopping 33.3kb.

Solution

Look into other validation plugins.

Current promising candidate is vuelidate.

/cc @hubudibu

Update: Yep, looks like we're switching to vuelidate, so let's replace all of the vee-validate stuff with it.

@taoeffect taoeffect added App:Frontend Kind:Core Anything that changes or affects the fundamental core data structures & design of the application. Kind:Enhancement Improvements, new features, performance upgrades, etc. Note:Up-for-grabs Priority:High labels Nov 26, 2017
@taoeffect taoeffect changed the title Switch from vee-validate to vuelidate or something else? Switch from vee-validate to vuelidate Jan 11, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
App:Frontend Kind:Core Anything that changes or affects the fundamental core data structures & design of the application. Kind:Enhancement Improvements, new features, performance upgrades, etc. Priority:High
Projects
None yet
Development

No branches or pull requests

2 participants