Question: Validate clientside multiple fields as 'distinct' rule

Versions

• vee-validate: 2.0.9
• vue: 2.5.16

This is more of a question than a bug IMO. I literally searched through the entire API, the community online, the issues on github but couldn’t figure a way to deal with this problem.

So I have a form which contains dynamic sections. Each section contains a dropdown (let’s keep it simple). For all of my dropdown, I want to make sure that the same value is not picked more than once.

I thought of making a custom rule that would call our Laravel backend, but this is not possible currently because of our implementation of validation on this side.

Currently, this is how I manage backend errors coming in:

manageBackendErrors(errors) {
      for (let fieldName in errors) {
        // gives us an error in the ErrorBag-item format
        const fieldErrors = errors[fieldName].map(msg => {
          return { field: fieldName, msg };
        });

        const field = this.$validator.fields.find({ name: fieldName });

        // then for that field, make a correlation on the id of the error and the field
        // and add the error to our Error Bag
        fieldErrors.forEach(error => {
          // we can access the id using field.id
          error.id = field.id;
          error.rule = 'distinct';
          this.verrors.add(error);
        });

        // finally update the flags, which also updates the opposite flags
        // (i.e: valid-invalid, dirty-pristine)
        field.setFlags({
          valid: !! fieldName.length,
          dirty: true
        });
      }
    }

This work well for single dropdown; the error is mapped correctly. But when I change the value of any dropdown, I would like the other errors of these fields to react as well. Is there any way I could let Vee-Validate know that multiple fields are binded to each other so that when one change, the other’s error re-evaluate as well?

[logaretm]

@kevrousso it will be available in v3, this cannot be implemented in v2. I don’t have an ETA yet, but v3 still needs more code samples and examples before its ready.

[logaretm]

I don’t have a planned release date unfortunately as the beta releases introduced a major re-write, and the amount of time is severely limited due to my army mandatory service. Now I have a few features in mind that I would like to address before the 2.1 is ready:

https://github.com/baianat/vee-validate/projects/3