Hey!

I see that this is your first PR. That is great! Welcome!

Symfony has a contribution guide which I suggest you to read.

In short:

• Always add tests
• Keep backward compatibility (see https://symfony.com/bc).
• Bug fixes must be submitted against the lowest maintained branch where they apply (see https://symfony.com/releases)
• Features and deprecations must be submitted against the 6.1 branch.

Review the GitHub status checks of your pull request and try to solve the reported issues. If some tests are failing, try to see if they are failing because of this change.

When two Symfony core team members approve this change, it will be merged and you will become an official Symfony contributor!
If this PR is merged in a lower version branch, it will be merged up to all maintained branches within a few days.

I am going to sit back now and wait for the reviews.

Cheers!

Carsonbot

IMHO this is correct behavior. It took some time to understand why the workaround was needed, when reviewing a PR on our side.

Im not sure about changing the behavior in a patch release. 6.1 + changelog works for us 👍

Im not sure about changing the behavior in a patch release. 6.1 + changelog works for us 👍

I first did it on 6.1 but then you said it's a bug in your opinion so i followed the rules and switch to 4.4 to make this PR 😁
I can switch back to 6.1 but i'm not sure what to write in the changelog... 🤔

Thanks for fixing this bug Laurent.