Skip to content

Validation Constraints for Collections #2559

Closed
@peterrehm

Description

@peterrehm

When using validation constraints most things work out of the box and easy. However for Collections it is strange, that the enabled error_bubbling leads to a passing of the error to the root form.

The behaviour is documented for the collection entity, but I think it should be documented as well for the actual constraints. I would suggest a tip that informs if you want to bind the error to the actual field, you need to disable error_bubbling. This would have saved some time for me.

I would submit a PR for that, but need Feedback if this is wanted, and where it should be implemented. Since there is no general page about Validation for Collections, there is the only way to add this to every Collection Validation opportunity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions