Skip to main content

This site requires you to update your browser. Your browsing experience maybe affected by not having the most up to date version.

We've moved the forum!

Please use for any new questions (announcement).
The forum archive will stick around, but will be read only.

You can also use our Slack channel or StackOverflow to ask for help.
Check out our community overview for more options to contribute.

Form Questions /

Moderators: martimiz, Sean, Ed, biapar, Willr, Ingo, swaiba

Is there still room to improve form validation? (From the perspective of 3.1)

Go to End



Community Member, 36 Posts

15 November 2015 at 12:53pm

Form validation is still incredibly time consuming for developers. Just today while working with 3.1, I've had http request road-blocks because DateField::setConfig() isn't behaving, and even changing from DateField -> TextField are still throwing DateField validation errors erroneously.

I feel form validation should be an additive model, developers should be able to understand what they're adding to their forms, not battling with bloat that doesn't even behave when following the API documentation to the letter. Even if the preliminary From and FormField structure is for the CMS, then I feel it should be abstracted more effectively.

What can be done about this?