A namespace for the BCD-UI widget validation (specific).
Members
-
staticbcdui.widgetNg.validation.validators.widget.TYPE_VALIDATORS
-
type validator adapters
Methods
-
staticbcdui.widgetNg.validation.validators.widget.getValue(){string}
widgetNg/validators.js, line 124 -
this getter we have to use which is compliant to the non-native placeholder feature
- See:
-
- implementation at bcdui.widgetNg.input.isFieldEmpty
Returns:
Type Description string value of the field or "" if the field is empty -
staticbcdui.widgetNg.validation.validators.widget.invalidModelDataValidator()
widgetNg/validators.js, line 184 -
checks that target data node is not tagged invalid with bcdInvalid attribute. The attribute itself carries the validation-message. This validator shall not be used generally by sticking it to other widget validators, since it does NOT validate widget's validity but the model's validity. This validator shall be handled manually by a widget only during SYNC_READ, so that it is always able to SYNC_WRITE (write back) widget's data to the model. General widget validation API supports this case as of widget.validator.validateElement(htmlElementId, checkDataValidity) function. extended widget configuration api used: - config.target.modelId - config.target.xPath
-
staticbcdui.widgetNg.validation.validators.widget.notEmptyValidator()
widgetNg/validators.js, line 165 -
staticbcdui.widgetNg.validation.validators.widget.patternValidator()
widgetNg/validators.js, line 153 -
staticbcdui.widgetNg.validation.validators.widget.valueLength(){Object|null}
widgetNg/validators.js, line 141 -
checks the value of element for its length constraints, widget configuration API used: - maxlength
Returns:
Type Description Object | null null if valid, validationMessageObject otherwise