Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Overview
Currently
vee-validate
is only usable by using Vue's plugin APIWhich is simple enough for most workflows, however some scenarios require having a rather selective installation, for example you want vee-validate to be working in some components but not others. Which could improve load time when using async components.
Another factor is the global pollution, VeeValidate currently injects a mixin and a directive in all components regardless if they are going to be using it or not, which is unnecessary.
This PR aims to add the ability to install vee-validate manually by converting the directive and mixin to standalone parts, so they can be imported and injected selectively into a component.
Issues Fixed
closes #778
Any thoughts are welcome, this PR might either get merged or rejected as this is not a must-have feature.