- LinkedSetField
- SelectObjectField
- MultipleChoicesField (warning this hierarchy contains non multiple value fields like SelectField !)
Also change AbstractValidator::Validate signature : now we are returning an array of error messages, so that we can return multiple ones
New AbstractValidator class, with new method Validate
All existing validators are now children of AbstractRegexpValidator
Handle validators JS counterparts in renderers : only regexp validators are implemented client side
Was caused by field value check added in MultipleChoicesField and SelectObjectField in b71cd218
With this commit the checks are now only done if we have a ContextTag::TAG_REST
Since introduction of MultipleChoicesField and SelectObjectField value checks with b71cd218, when a portal user was trying to do an action on a resolved UR the agent_id field was rejected. The reason for the rejection is the corresponding SelectObjectField query is containing the portal user scopes (query generated in ObjectFormManager::Build), and of course the agent_id set isn't in this scope...
As a workaround we are disabling those checks for read only fields (values are set server side and possibly in a different context than the portal user)
