lion/packages/validate
CircleCI 591ef9f4fa chore: release new versions
- @lion/button@0.1.19
 - @lion/calendar@0.1.14
 - @lion/checkbox-group@0.1.18
 - @lion/checkbox@0.1.16
 - @lion/choice-input@0.1.16
 - @lion/field@0.1.16
 - @lion/fieldset@0.1.16
 - @lion/form-system@0.0.19
 - @lion/form@0.1.18
 - @lion/input-amount@0.1.16
 - @lion/input-date@0.1.16
 - @lion/input-datepicker@0.1.11
 - @lion/input-email@0.1.16
 - @lion/input-iban@0.1.17
 - @lion/input@0.1.16
 - @lion/localize@0.3.6
 - @lion/popup@0.1.19
 - @lion/radio-group@0.1.18
 - @lion/radio@0.1.16
 - @lion/select@0.1.16
 - @lion/textarea@0.1.16
 - @lion/tooltip@0.1.19
 - @lion/validate@0.2.6
2019-05-31 12:10:08 +00:00
..
docs fix(validate): fix isDateDisabled validator 2019-05-17 11:45:11 +02:00
src fix(validate): fix isDateDisabled validator 2019-05-17 11:45:11 +02:00
test fix(validate): fix isDateDisabled validator 2019-05-17 11:45:11 +02:00
translations fix(validate): fix isDateDisabled validator 2019-05-17 11:45:11 +02:00
CHANGELOG.md chore: release new versions 2019-05-31 12:10:08 +00:00
index.js feat(validate): added disabledDatesValidator 2019-05-16 10:39:57 +02:00
package.json chore: release new versions 2019-05-31 12:10:08 +00:00
README.md feat: release inital public lion version 2019-04-26 10:37:57 +02:00

Validate

Features

  • allow for advanced UX scenarios by updating validation state on every value change
  • provide a powerful way of writing validation via pure functions
  • multiple validation types(error, warning, info, success)
  • default validators
  • custom validators

Validation is applied by default to all form controls via the ValidateMixin.

For a detailed description of the validation system and the ValidateMixin, please see ValidationSystem.

How to use

Installation

npm i --save @lion/validate
import '@lion/input/lion-input.js';
import { %validatorName% } from '@lion/validate';

Note that we import an lion-input here as an example of a form control implementing ValidateMixin. We could equally well use lion-textarea, lion-select, lion-fieldset etc. to illustrate our example.

Example

All validators are provided as pure functions. They should be applied to the formcontrol (implementing ValidateMixin) as follows:

import '@lion/input/lion-input.js';
import { isString, maxLengthValidator, defaultOkValidator } from '@lion/validate';

const isInitialsRegex = /^([A-Z]\.)+$/;
export const isExampleInitials = value => isString(value) && isInitialsRegex.test(value.toUpperCase());
export const isExampleInitialsValidator = () => [
  (...params) => ({ isExampleInitials: isExampleInitials(...params) }),
];
<lion-input
  label="Initials"
  name="initials"
  .errorValidators="${[['required], maxLengthValidator(10)]}"
  .warningValidators="${[isExampleInitialsValidator()]}"
  .successValidators="${[defaultOkValidator()]}"
></lion-input>

In the example above we use different types of validators. A validator applied to .errorValidators expects an array with a function, a parameters object and optionally an additional configuration object.

minMaxLengthValidator({ min: 5, max: 10 })

The custom isExampleInitialsValidator checks if the value is fitting our regex, but does not prevent the user from submitting other values.

Retrieving validity states is as easy as checking for:

myInitialsInput.errorState === false;