Symfony中CollectionType字段验证错误未绑定到字段的问题求助

问题重现 #

在Symfony表单中为CollectionType字段添加验证器（自定义或自带如Count）时，错误信息未绑定到该字段，而是出现在表单根节点，无法在对应字段下方渲染错误。

相关代码如下：

实体类 #

Phase实体

class Phase // 省略Doctrine注解和getter/setter
{
    private int $idPhase;
    private ?DateTimeInterface $dtDue = null;
    private int $nbNoticeDaysExpert = 7;
    private int $nbNoticeDaysMember = 7;
}

Call实体

class Call // 省略Doctrine注解和getter/setter
{
    private ?int $idCall = null;
    private ?string $acronym = null;
    private ?Call $previousCall = null;
    private Collection $phases;

    public function __construct()
    {
        $this->phases = new ArrayCollection();
    }
}

自定义验证器 #

class PhaseUniqueByCallValidator extends ConstraintValidator
{
    public function validate(mixed $value, Constraint $constraint): void
    {
        $this->context->buildViolation('paffffff')->addViolation();
        return;
    }
}

表单类型（存在错误的版本） #

class CallType extends AbstractType
{
    public function buildForm(FormBuilderInterface $builder, array $options): void
    {
        $builder
            ->add('lbAcronyme', TextType::class, [
                'required' => true,
                'constraint' => [new PhaseUniqueByCall()], // 错误：应为复数constraints
            ])
            ->add('previousCall', EntityType::class, [
                'class' => Call::class,
                'constraint' => [new PhaseUniqueByCall()], // 错误：应为复数constraints
            ])
            ->add('phases', CollectionType::class, [
                'entry_type' => Phase::class, // 错误：应为表单类型类（如PhaseType::class）
                'constraint' => [new PhaseUniqueByCall()], // 错误：应为复数constraints
            ]);
    }
}

解决步骤 #

1. 修正表单配置的拼写错误 #

Symfony表单字段的验证配置项为复数形式constraints，而非单数constraint；同时CollectionType的entry_type必须指向对应的表单类型类（而非实体类）：

class CallType extends AbstractType
{
    public function buildForm(FormBuilderInterface $builder, array $options): void
    {
        $builder
            ->add('lbAcronyme', TextType::class, [
                'required' => true,
                'constraints' => [new PhaseUniqueByCall()], // 改为复数
            ])
            ->add('previousCall', EntityType::class, [
                'class' => Call::class,
                'constraints' => [new PhaseUniqueByCall()], // 改为复数
            ])
            ->add('phases', CollectionType::class, [
                'entry_type' => PhaseType::class, // 替换为对应的表单类型类
                'constraints' => [
                    new PhaseUniqueByCall(), // 改为复数
                    // 示例：添加Symfony自带的Count验证器
                    new Count([
                        'min' => 1,
                        'minMessage' => '至少需要添加一个阶段',
                    ])
                ],
            ]);
    }
}

2. 确保自定义验证器的错误路径正确 #

如果验证器是绑定到CollectionType字段的，验证上下文已经指向该字段，无需额外指定atPath，直接构建错误即可：

class PhaseUniqueByCallValidator extends ConstraintValidator
{
    public function validate(mixed $value, Constraint $constraint): void
    {
        // 先判断值是否为集合类型
        if (!$value instanceof Collection) {
            return;
        }

        // 这里添加你的实际验证逻辑，比如检查阶段是否重复
        $hasDuplicates = false;
        // ... 你的验证代码 ...

        if ($hasDuplicates) {
            $this->context->buildViolation($constraint->message)
                ->addViolation();
        }
    }
}

3. 验证Constraint类的目标设置 #

确保自定义Constraint类的验证目标设置为PROPERTY_CONSTRAINT（默认值，但显式声明更清晰）：

/**
 * @Annotation
 */
class PhaseUniqueByCall extends Constraint
{
    public string $message = '集合中的阶段不能重复';

    public function getTargets(): string|array
    {
        return self::PROPERTY_CONSTRAINT;
    }
}

4. Twig中正确渲染字段错误 #

在Twig模板中，确保为CollectionType字段渲染错误：

{{ form_row(form.phases) }}
{# 或者手动渲染错误 #}
{% if form.phases.vars.errors is not empty %}
    <div class="alert alert-danger">
        {% for error in form.phases.vars.errors %}
            {{ error.message }}<br>
        {% endfor %}
    </div>
{% endif %}

内容的提问来源于stack exchange，提问作者olivier lejeune