Velo Package Release: bulk-input-validation

We recently released a new Velo Package - bulk-input-validation

The Bulk Validation package allows you to validate a group of input elements. The package functions check a group of input elements and make sure that each individual input element is validated according to its specified validation type.

Check out the Velo Packages article to learn more, or make a request for a new package .

This isn’t working right for me. If I try an invalid input and then correct this to a valid input, console.log(result.result) stays as “fail” even though result.components shows that all individual inputs are valid:

First, console.log(result.components) on the invalid input (where one required input is missing):

[
  {
    "component": "latitudeField",
    "msg": "",
    "valid": true
  },
  {
    "component": "longitudeField",
    "msg": "",
    "valid": true
  },
  {
    "component": "rangeOutputM",
    "msg": "",
    "valid": true
  },
  {
    "component": "firstNameInput",
    "msg": "",
    "valid": true
  },
  {
    "component": "lastNameInput",
    "msg": "",
    "valid": true
  },
  {
    "component": "emailInput",
    "msg": "value missing",
    "valid": false
  }
]

Secondly, the corrected input where all individual inputs are valid, but console.log(result.results) is still returning “fail”:

[
  {
    "component": "latitudeField",
    "msg": "",
    "valid": true
  },
  {
    "component": "longitudeField",
    "msg": "",
    "valid": true
  },
  {
    "component": "rangeOutputM",
    "msg": "",
    "valid": true
  },
  {
    "component": "firstNameInput",
    "msg": "",
    "valid": true
  },
  {
    "component": "lastNameInput",
    "msg": "",
    "valid": true
  },
  {
    "component": "emailInput",
    "msg": "",
    "valid": true
  }
]

Please could this be addressed?

Hey Ryan!

Thank you very much for your feedback, you are indeed correct that the valid indicator does not update when switching validity.

I have fixed this and pushed the changes to live. It should be fixed in no time, just make sure to update the package when prompted.

Thanks again!
Majd Qumseya

Thanks for sorting this out so promptly @majdq , I’ll update the package when I can and give it a try again

Hi @majdq , this issue appears to be resolved. I have now noticed that the group of inputs can be be resolved as valid in spite of a required checkbox in that group being unchecked? Should this package work with checkboxes?

Hey Ryan,

Checkboxes should be included as well in the verification. That change should be live now!

This package just made my day.

What I really want is a way to trigger validation onInput, instead of just onChange. The reason being that if you have a text field (let’s say it’s required), and you delete all the text in it, and then the very next thing you do is click on submit, then the submit doesn’t know that the text field is invalid and it submits away. I wanted to disable the submit button until everything was valid, but that requires that the user click somewhere…anywhere…after making an invalid text field valid. which is mildly annoying.

Since I couldn’t do that, I was in the midst of hand coding what this package does…find every form element…check its validity…block the submit.

omg…thank you.

Did Velo packages recently break? I installed wix-bulk-validation and it worked beautifully. Today, the Wix editor is unable to find any Velo packages, and the validation code from this package no longer runs.

When I click on the zippy in the code menu, there is nothing in the folder. When I click on the ellipsis and choose open README, there is no readme file. I tried uninstalling and reinstalling. I also tried installing another Velo package (Google Drive integration) just to see if there might be something wrong with this package specifically, but that one has the same issue as well.

Thanks in advance

there was an issue recently fixed by the team, that affected the editor experience using the package (ability to see the readme files + use the package methods in editor). Note that the issue didn’t affect the live sites.