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.2 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

New features are never backported to previous minor versions

@stof this is not backported feature. When TypeError is thrown it is impossible to handle it with kernel.exception event. This happens to be fixed on next release but it still remains on LTS.

Your PR would introduce a breaking change into an LTS branch. The change you're suggesting has been implemented in a backwards-compatible manner in 6.2 via #45997. If you need this change, upgrade to Symfony 6.2.

@derrabus Is it intentional that PHP errors won't be handled by framework until next stable release? Because they are not handled on current LTS which looks more like a bug, not a feature.

Yes it is: this behavior exists since the beginning of Symfony v2 and changing it would break existing apps.
Actually, 6.2 won't change the current behavior if #47467 is merged (and I hope it will)
See #45997 for more background on the topic.