[MGNLFORM-85] FormValidators: Should be definable on the component itself (-> multisite capable) Created: 18/Apr/11  Updated: 04/Nov/15  Resolved: 04/Nov/15

Status: Closed
Project: Magnolia Form Module
Component/s: validation
Affects Version/s: 1.2.2
Fix Version/s: None

Type: Improvement Priority: Major
Reporter: Christian Ringele Assignee: Unassigned
Resolution: Won't Do Votes: 4
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Date of First Response:

 Description   

The validators used in the form fields are served from the modules config:
/config/modules/form/config/validators

So all validators are served for all form templates throughout the system/all sites.

It would be better, if it would be definable on the concrete component itself, which validators should be choosable.
Otherwise its not possible, to provide validators just for a specific site/form.

Most flexible it would be, if they would be definable on the the main form components ('form') which are generally allowed.
And probably on the concrete form-field component constraining of the general defined ones which sot server (if nothing defined, all forms the 'form' paragraph are allowed).



 Comments   
Comment by Christopher Zimmermann [ 03/Dec/13 ]

It would be helpful to hear the use cases for this - in order to determine which of the options would make the most sense. We want to provide enough flexibility - but only at the cost of the appropriate amount of complexity in code and UI.

Comment by Michael Mühlebach [ 04/Nov/15 ]

Given the thousands of other issues we have open that are more highly requested, we won't be able to address this issue in the foreseeable future. Instead we will focus on issues with a higher impact, and more votes.
Thanks for taking the time to raise this issue. As you are no doubt aware this issue has been on our backlog for some time now with very little movement.
I'm going to close this to set expectations so the issue doesn't stay open for years with few updates. If the issue is still relevant please feel free to reopen it or create a new issue.

Generated at Mon Feb 12 05:36:43 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.