It helps you provide your users with feedback on their form submission before sending it to your server.
It saves you bandwidth, server load and it saves time for your users.
You have to manage these errors completely manually and they should be independant with other validations. Note that Parsley triggers events that allows Parsley UI to work.
Further more, it could allow you to do some powerful magic if you listen properly to the right events!
That's why Parsley is here: to let you define your general form validation, implement it on the backend side, and simply port it frontend-side, with maximum respect to user experience best practices.
Validators can reject with a custom error message as a first argument if desired.
Parsley is a decoupled library that uses different classes to do the heavy work.
For cases where more complex parameters are needed, you can specify extra parameters; refer to the source and check how the for each locale.
Parsley ships a UI/UX component that is the only one responsible for classes, error messages, focus or trigger events that alter your page. Here are the main mottos for Parsley UI: Naturally, all of this is absolutely customizable; you'll see below how to configure your desired UX behavior.
checkboxes), then you can specify validate Multiple and one of the other two.
Validating functions should return either otherwise. It can instead return a j Query promise that will be resolved if the value is valid, or be rejected otherwise.
Parsley adds its share of classes and elements, to ease nice UI validation result display.