Verify - dependent rules

The docs state that validator.verify() cannot use dependent rules without v-validate:

Note that Target Dependant Rules won’t work as they require a target field being tracked which cannot be done without using the v-validate directive.

However, I don’t understand why this is so.

Surely as an independent function, the additional values / rules could be passed in?

validator.verify(value, rule, values, rules)

In my case, I will have all these, so it should be simple to derive a response?

[logaretm]

Congrats on the plugin release 🎉 Will be sure to mention it in the docs and here in the README.

Currently my work on #1625 has opened my eyes to simpler approach to how validation should be done. Functional approach to fields should reduce the footprint of vee-validate in the future, I’m planning a re-write once I’m done with the Army service in few months, the re-write have a few goals:

• Modular Features (Optional ErrorBag, Flags, Classes, Messages) Which means the core lib would be only validating via the verify API since it is the most flexible among the validation methods, this should bring the size down considerably since it is the downside of vee-validate.
• TypeScript? Haven’t decided yet, but flow isn’t really proofing the code and is missing most of TS features, also being optional encourages my laziness to not actively proof it.
• Review some features like Scopes and if they should be removed or not.

This might warrant a major release 3.x but this list isn’t definitive. It is the few ideas and regrets about the project, feel free to suggest more.

[davestewart]

Well, either way!

Let me know how you go. I released Vee Element this morning:

• https://github.com/davestewart/vee-element

If we can get dependent rules validating here, I will be a happy man!

• https://github.com/davestewart/vee-element/blob/master/src/main.js#L41-L64

Unless you have any better suggestions, like implementing a new Validator instance?