Needs work
Project:
Clientside Validation
Version:
8.x-1.x-dev
Component:
Code
Priority:
Minor
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
23 Feb 2017 at 14:54 UTC
Updated:
14 Sep 2023 at 13:05 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #3
nikunjkotechaHi @andywhale,
You can easily achieve this by implementing your own rule/plugin implementation of type CvValidator.
Thanks,
Nikunj
Comment #4
andy_w commentedUnfortunately implementing our own wouldn't give us the override required, for example to function as an intermediate layer between webform and parsley.
Comment #5
andy_w commentedError located in patch.
Comment #6
nikunjkotecha@andy_w
IMO we should add this to annotation and allow it to be configurable per rule to allow overriding for specific rules wherever required, does that approach make sense to you?
About the patch (in-case you still want to continue with this approach):
1. Any specific reason to use t()?
2. Can you please add the config in yaml with default value (used today), an update hook to initialise and update schema?
Comment #7
nikunjkotechaComment #8
andy_w commentedAdded a configuration form, and removed "t" method and replaced with prefix / suffix (and added config defaults).
Though I am intrigued by the annotation suggestion, if we wanted to affect all of the various validators in use by webform, would we just need to add a full custom set of validators.
Comment #10
andy_w commentedFixed issues / added schema (missed from previous comment)
Comment #11
andy_w commentedRevised for version 4