Issues

Go to all issues

Select view

List view

Detail view

Select search mode

Basic

JQL

wcm.io validation does not allow multiple validators to be attached to a single field
WWCM-19
Resolved issue: WWCM-19
Clientlibs UI Extension | JS and CSS scripts are included multiple times
WWCM-18
Resolved issue: WWCM-18
Pathfield UI Granite validation
WWCM-17
Resolved issue: WWCM-17
GraniteUI Checkbox does not set false when unchecked
WWCM-16
Resolved issue: WWCM-16
Clientlibs UI Extensions | Incompatible with ACS Versioned Clientlibs
WWCM-14
Resolved issue: WWCM-14
Navigation Core Component is unable to have adjusted paths for navigation
WWCM-12
Resolved issue: WWCM-12
Predicate for pathfield
WWCM-11
Resolved issue: WWCM-11
"value" - config property not used in numberfield if jcr:created and jcr:lastModifed is missing
WWCM-10
Resolved issue: WWCM-10
Parsys: override allowance definition of resourceSuperType
WWCM-9
Resolved issue: WWCM-9
configScopePathBrowser without a resource
WWCM-8
Resolved issue: WWCM-8
Enable passing custom error code to DenyWcmDisabled
WWCM-7
Resolved issue: WWCM-7
Parsys: property wcmio:parsysParagraphCss not working in authoring mode
WWCM-6
Resolved issue: WWCM-6
Basic Granite UI Extension to support array format for a multiple selection field
WWCM-5
Resolved issue: WWCM-5
Basic Granite UI Extensions and Support for Dynamic Granite UI components
WWCM-4
Resolved issue: WWCM-4
Add Generic HttpClientFactory Service
WWCM-2
Resolved issue: WWCM-2
Parsys markup causes layout problems with floating components
WWCM-1
Resolved issue: WWCM-1
Add possiblity to create NonSelfClosingHtmlElement
WWCM-3
Resolved issue: WWCM-3

17 of 17

wcm.io validation does not allow multiple validators to be attached to a single field

Fixed

Description

We noticed that the selectors for the wcm.io validators are too restrictive, they require an exact match. The issue is that, when using multiple validators (it is actually possible to configure the validation-property as a string array property), the exact attribute matching will not work, causing the validator not to be triggered.

In case of a string array property with multiple entries, the values are concatenated with a space (i.e. wcm.io.pattern my.custom.one).

An easy fix would be to replace the = with ~= as is also done in other (OOTB) AEM validators.

Details

Assignee

Stefan Seifert

Reporter

Henry Kuijpers

Components

Fix versions

WCM Granite UI Extensions 1.9.8

Affects versions

WCM Granite UI Extensions 1.7.6

Priority

Major

Created October 12, 2022 at 2:10 PM

Updated October 13, 2022 at 9:00 AM

Resolved October 13, 2022 at 8:34 AM

Configure

Activity

Show:

Stefan SeifertOctober 13, 2022 at 9:00 AM

yes - release is done

Henry KuijpersOctober 13, 2022 at 8:37 AM

Would it be possible to get a release out with this fix?

Stefan SeifertOctober 13, 2022 at 8:34 AM

agreed - MR is merged, thanks!

Henry KuijpersOctober 12, 2022 at 9:34 PM

We very much agree to that! And indeed, we saw that the OOTB validators also seen to do this. I guess the idea is to choose a validator name that is as unique as possible to cause no such conflicts.

We also saw some other validation selectors, that selected on data attributes or class names.

I’m afraid that, given the current setup and also given that Adobe is doing it themselves as well, this is the best way to support having multiple validators.

Stefan SeifertOctober 12, 2022 at 4:24 PM

hmm, do not like that solution, as matching with ~= will not work if you have multiple validator names starting with the same string e.g.:
wcmio.email
wcmio.emai.special1
wcmio.emai.special2

and then you are looking for wcmio.email.

but it seems adobe is doing it internally for their validators as well