Details
-
New Feature
-
Status: Closed
-
Normal
-
Resolution: Fixed
-
None
-
None
-
None
-
8
-
Tiger
-
Tiger Sprint 200, Tiger Sprint 201
Description
Currently, one or multiple validation messages are always shown on top of a document with a generic description (no indication of which field is invalid).
As a first step of supporting existing and custom validators in the visual editor, we align the validator support in Wicket with the validator support in Angular; this shows the validation message directly below the invalid field. In case of multiples, it is rendered after the last field.
In addition, there should be a summary on the top of the document displaying the names of the violating fields.
This means that all existing generic messages should be updated to be field specific. Custom validators will keep the old behavior of printing a validation message on top. To differentiate between messages per field and messages on top, we will mark existing built-in validators with a new property scope = field using the following update script
for all known-validator-names if plugin.class matches expected default add property scope=field
Attachments
Issue Links
- causes
-
CMS-11692 Make more field validation messages scope aware
- Open
-
CMS-12717 Change structure of validation messages
- New
- is awaited by
-
CMS-11667 Add validator service module
- Closed
- relates to
-
CHANNELMGR-1450 Add the same validator support to VE as is currently supported in content perspective
- Closed
-
CMS-11521 Field validation doesn't tell you which field is empty
- Closed
- testing discovered
-
HIPPLUG-1580 Content blocks applies validation in an incorrect way
- Closed