Issues
- wcm.io validation does not allow multiple validators to be attached to a single fieldWWCM-19Resolved issue: WWCM-19Stefan Seifert
- Clientlibs UI Extension | JS and CSS scripts are included multiple timesWWCM-18Resolved issue: WWCM-18Stefan Seifert
- Pathfield UI Granite validationWWCM-17Resolved issue: WWCM-17
- GraniteUI Checkbox does not set false when uncheckedWWCM-16Resolved issue: WWCM-16
- Clientlibs UI Extensions | Incompatible with ACS Versioned ClientlibsWWCM-14Resolved issue: WWCM-14
- Navigation Core Component is unable to have adjusted paths for navigationWWCM-12Resolved issue: WWCM-12Stefan Seifert
- Predicate for pathfieldWWCM-11Resolved issue: WWCM-11Stefan Seifert
- "value" - config property not used in numberfield if jcr:created and jcr:lastModifed is missingWWCM-10Resolved issue: WWCM-10
- Parsys: override allowance definition of resourceSuperTypeWWCM-9Resolved issue: WWCM-9
- configScopePathBrowser without a resourceWWCM-8Resolved issue: WWCM-8
- Enable passing custom error code to DenyWcmDisabledWWCM-7Resolved issue: WWCM-7Stefan Seifert
- Parsys: property wcmio:parsysParagraphCss not working in authoring modeWWCM-6Resolved issue: WWCM-6
- Basic Granite UI Extension to support array format for a multiple selection fieldWWCM-5Resolved issue: WWCM-5
- Basic Granite UI Extensions and Support for Dynamic Granite UI componentsWWCM-4Resolved issue: WWCM-4
- Add Generic HttpClientFactory ServiceWWCM-2Resolved issue: WWCM-2
- Parsys markup causes layout problems with floating componentsWWCM-1Resolved issue: WWCM-1Stefan Seifert
- Add possiblity to create NonSelfClosingHtmlElementWWCM-3Resolved issue: WWCM-3
wcm.io validation does not allow multiple validators to be attached to a single field
Description
Details
Details
Assignee
Reporter
Components
Fix versions
Affects versions
Priority
MajorActivity
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
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.