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
[ ] Change the double array config from the POC to instead allow options A), B) and C)
[x] Types of validation that could be handled on FieldValidator's are identified, e.g. Email, URL, Int size, etc - note the existing data types
[ ] Existing FormField validate methods are updated to use FieldValidator's where possible
[ ] Some new DB fields are created with validation e.g. DBEmail, DBUrl, DBIp
[ ] New DB fields are autoscaffold existing equivalent FormField if one exists e.g. EmailField, though DBIp would just be a TextField
[ ] New DBFields are listed in docs on the Data types page
[ ] DBField validation is mentioned in the developer docs
[ ] 6.0.0 changelog calls out that data will no longer be inserted and truncated if it exceeds varchar character lengths, etc, instead it will throw a validation exception
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
Kitchen sink CI
PRs