Problem
DefaultEntityForm tries to skip fields that are not writable, but the current checks are not consistent across association types.
Current behavior
- simple Doctrine fields are skipped when the property is not public and there is no setter
- one-to-one associations apply the same guard
- many-to-one associations are added without the same writability check
Why it matters
The generated default form can expose association fields that the entity cannot actually write through the normal property or setter path.
Suggested direction
Apply the same writability checks to many-to-one associations as to the other autogenerated fields, or define a clearer contract for which associations the default form is allowed to expose.
Problem
DefaultEntityFormtries to skip fields that are not writable, but the current checks are not consistent across association types.Current behavior
Why it matters
The generated default form can expose association fields that the entity cannot actually write through the normal property or setter path.
Suggested direction
Apply the same writability checks to many-to-one associations as to the other autogenerated fields, or define a clearer contract for which associations the default form is allowed to expose.