Why generated not nullable fields have nullable types (?T) instead of type (T)

[SirMishaa]

Hello,

I'm wondering something why when I generate a not-nullable field, like for example $name, the generated type is ?string and not string. This can have pretty huge impact when using tools like PHPStan since the usage of property may need additional check verification.

Is there something I miss ?
For context, I have read also this issue : #1074, but I don't see why it's still the case in 2023 in the latest version of the marker bundle.

class User {
    #[ORM\Column(length: 255)]
    private ?string $name= null;
}

Regards

[SirMishaa]

Oh, my bad, I feel stupid.

I just thought about the case when you instantiate an entity, and you set some property using setter.

$user = new User();
$user->setName("uwu");

So that's why you need the field to be marked as nullable, since we're setting each field one by one, not in the instantiation of the class in the constructor for example.

If I'm correct, you can close this issue ! 😅