Typed Properties and default column/association types #6356

New Issue

admin · 2026-01-22T15:31:39+01:00

admin commented

2026-01-22 15:31:39 +01:00

Originally created by @beberlei on GitHub (Dec 1, 2019).

Feature Request

Q	A
New Feature	yes
RFC	no
BC Break	no

Summary

When declaring a type on a property, this should act as a default for field type or ManyToOne/OneToOne targetEntity.

class User
{
    /** @ORM\Column */
    public int $id; // defaults to type="integer"

   /** @ORM\ManyToOne */
   public Email $email; // defaults to targetEntity=Email::class
}

The relevant code would be in ClassMetadataInfo::mapField, mapManyToOne and mapOneToOne. Whenever type or targetEntity is missing, it could look this up in reflection property instead if it has a type.

Originally created by @beberlei on GitHub (Dec 1, 2019). ### Feature Request | Q | A |------------ | ------ | New Feature | yes | RFC | no | BC Break | no #### Summary When declaring a type on a property, this should act as a default for field type or ManyToOne/OneToOne targetEntity. ```php class User { /** @ORM\Column */ public int $id; // defaults to type="integer" /** @ORM\ManyToOne */ public Email $email; // defaults to targetEntity=Email::class } ``` The relevant code would be in `ClassMetadataInfo::mapField`, `mapManyToOne` and `mapOneToOne`. Whenever `type` or `targetEntity` is missing, it could look this up in reflection property instead if it has a type.

admin referenced this issue

2026-01-22 16:05:57 +01:00

[PR #6356] Fix wrong variable name #9946

admin referenced this issue

2026-01-22 16:06:07 +01:00

[PR #6494] Add failing test for #6314 and PR #6356 #10001

Sign in to join this conversation.