BREAKING: Dynamic variables inside dynamic content are problematic for tools that use static analysis, therefore we have removed it, but you can still add it back on your extension if it works for you. The change may break your extension if you relied on this logic, you can add it back yourself by overriding the static get localizeNamespaces(). Example can be found here: https://github.com/ing-bank/lion/blob/%40lion/localize%400.8.10/packages/localize/stories/50-system-overview.stories.mdx#rendering-with-localizemixin |
||
|---|---|---|
| .. | ||
| docs | ||
| src | ||
| stories | ||
| test | ||
| test-helpers | ||
| test-suites | ||
| translations | ||
| CHANGELOG.md | ||
| index.js | ||
| lion-validation-feedback.js | ||
| package.json | ||
| README.md | ||
| test-helpers.js | ||
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 { Required, IsString, MaxLength, DefaultSuccess, Validator } from '@lion/validate';
const isInitialsRegex = /^([A-Z]\.)+$/;
class IsInitialsExample extends Validator {
static get validatorName() {
return 'IsExampleInitials';
}
execute(value) {
let hasFeedback = false;
const isStringValidator = new IsString();
if (!isStringValidator.execute(value) || !isInitialsRegex.test(value.toLowerCase())) {
hasFeedback = true;
}
return hasFeedback;
}
static getMessage({ fieldName }) {
return `Please enter a valid {fieldName} in the format "A.B.C.".`;
}
}
<lion-input
label="Initials"
name="initials"
.validators="${[new Required(), new MaxLength(10), new IsInitialsExample(null, { type: 'warning' }), new DefaultSuccess()]}"
></lion-input>
In the example above we use different types of validators.
A validator applied to .validators expects an array with a function, a parameters object and
optionally an additional configuration object.
MinMaxLength({ min: 5, max: 10 });
The custom IsInitialsExample 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.hasFeedbackFor.include('error');