Nullable property type does still not translate to nullable SQL column

[fridde]

Bug Report

Q	A
BC Break	no
Version	2.9.3

Summary

It seems like making a property type nullable like this

 #[ORM\Column]
    protected ?string $Location = null;

does not translate to the SQL column being nullable, contrary to what the docs say. It still has to be declared in the attribute as #[ORM\Column(nullable: true)].

How to reproduce

1. Create an entity using attributes, for example

#[ORM\Table(name: "users")]
class User
{
    #[ORM\Id, ORM\Column, ORM\GeneratedValue]
    protected int $id;

    #[ORM\Column]
    protected ?string $Name = null;
}

2. Set your mapping driver to "attribute".
3. Create a migration with .\bin\console make:migration
4. Inspect the created migration and see that within the up()-method you see [...] Name VARCHAR(255) NOT NULL [...]

Expected behavior

The last step should have contained [...] Name VARCHAR(255) DEFAULT NULL [...].

I think that @beberlei has been working on the implementation?

[beberlei]

Its not a bug, we had to remove it due to problems. The docs should have been updated though

[fridde]

Ah, okay. That's too bad.

But no, I can't find any change in the docs: see here for the relevant line in the docs for 2.9.x.

I might be missing something though.