[DoctrineBridge] Allow to ignore specific nullable fields in UniqueEntity

[VincentLanglet]

Q	A
Branch?	6.3
Bug fix?	no
New feature?	yes
Deprecations?	no
Tickets	Fix #...
License	MIT
Doc PR	symfony/symfony-docs#... TODO

When the UniqueEntity is applied on multiple things the only option was

• ignore all nullable values
• do not ignore any nullable values

With this feature, it would be possible to ignore nullable values for specific field only and do not ignore nullable values for others.

[carsonbot]

Hey!

I think @malarzm has recently worked with this code. Maybe they can help review this?

Cheers!

Carsonbot

[VincentLanglet]

Hi @nicolas-grekas, Would you have some time to review this PR ?
Thanks a lot

[VincentLanglet]

Hi @fabpot maybe you have some time to take a look or redirect me to the right reviewer ?

Thanks

[malarzm]

Frankly I have a hard time figuring out a use case for this. Could you please share one?

[VincentLanglet]

Frankly I have a hard time figuring out a use case for this. Could you please share one?

I have an entity of UserRoles which are related to

• An Organization
• A Project
• A User
• An email

For a specific Organization and Project, only one UserRole should exists.
But UserRole with no relation to a project can exists, it will be only related to a Project, it's only allowed one time.
And the User is nullable, because it's not set until the email is validated.

For the same User/Organization, you cannot have multiple null project
but for the same Organization/Project, you can have multiple null user (pending)

UniqueEntity(fields={organization, project, user}, ignoreNull={user})

[malarzm]

Thanks for the use case, it makes more sense now!

[VincentLanglet]

Would you have time to take a look/review this @nicolas-grekas @fabpot ?
Thanks a lot !

[fabpot]

LGTM

[nicolas-grekas]

Thank you @VincentLanglet.