-
Notifications
You must be signed in to change notification settings - Fork 822
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement DBField validation #11403
Comments
This was referenced Sep 30, 2024
FieldValidatorsBooleanValidator
DBFields
FormFields
CompositeValidator
DBFields
FormFields
EnumValidator
DBFields
FormFields
DecimalValidator
DBFields
FormFields
DateValidator
DBFields
FormFields
DateTimeValidator
DBFields
FormFields
EmailValidator
DBFields
FormFields
IntValidator
DBFields
FormFields
IpValidator
DBFields
FormFields
LocaleValidator (extends StringValidator)
DBFields
FormFields
StringValidator
DBFields
FormFields
TimeValidator
DBFields
FormFields
UrlValidator
DBFields
FormFields
|
This was referenced Sep 30, 2024
This was referenced Oct 10, 2024
Merged
@emteknetnz Don't forget to do a CMS 5 changelog PR for the deprecations. |
6 tasks
@emteknetnz I can't test these PRs because they need to be rebased after the recent template work got merged in. |
Has been done |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Consolidate validation systems contained a POC that added DBField validation via a new shared FIeldsValidator class. We agreed that we should proceed with implementing this for CMS 6
Acceptance criteria
Existing FormField validate methods are updated to use FieldValidator's where possibleSplit off as new issueNew issues created
Kitchen sink CI CMS 6
CMS 5 PRs
CMS 6 PRs
The text was updated successfully, but these errors were encountered: