Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

[DependencyInjection] Ensure deprecation detection does not trigger a PHP error#62544

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Open
bnf wants to merge1 commit intosymfony:7.4
base:7.4
Choose a base branch
Loading
frombnf:fix-resolve-class-pass-class-exists-fatal-error

Conversation

@bnf
Copy link
Contributor

@bnfbnf commentedNov 28, 2025
edited
Loading

Exception Interface "TYPO3\CMS\Reports\StatusProviderInterface" not found
Seehttps://forge.typo3.org/issues/108349

QA
Branch?7.4
Bug fix?yes
New feature?no
Deprecations?no
LicenseMIT

Theclass_exists check and the condition$definition instanceof ChildDefinition have been swapped with#61215 in order to produce an error if a service is not available.

This error was later relaxed in#61270, but the executing order of the condition kept to beclass_exists first, theninstanceof.

That means, ifclass_exists fails with a PHP error (like PHP Fatal Error: Interface "My\Vendor\MyInterface" not found`) affected uses will not see the deprecation, but a fatal error instead.

andrew-demb reacted with thumbs up emoji
@carsonbot
Copy link

Hey!

To help keep things organized, we don't allow "Draft" pull requests. Could you please click the "ready for review" button or close this PR and open a new one when you are done?

Note that a pull request does not have to be "perfect" or "ready for merge" when you first open it. We just want it to be ready for a first review.

Cheers!

Carsonbot

@bnfbnfforce-pushed thefix-resolve-class-pass-class-exists-fatal-error branch from7fccf18 toe74ddd9CompareNovember 28, 2025 09:12
@bnfbnf marked this pull request as ready for reviewNovember 28, 2025 09:12
@bnfbnfforce-pushed thefix-resolve-class-pass-class-exists-fatal-error branch 6 times, most recently fromd7e7fab toea76884CompareNovember 28, 2025 09:42
… PHP errorThe `class_exists` check and the condition `$definition instanceof ChildDefinition`have been swapped withsymfony#61215 in order to produce an error if a service is notavailable.This error was later relaxed to a deprecation insymfony#61270, but the executing orderof the condition kept to be `class_exists` first, then `instanceof`.That means, if `class_exists` fails with a PHP error(like PHP Fatal Error: Interface "My\Vendor\MyInterface" not found`)affected uses will not receive the deprecation, but a fatal error instead.
@bnfbnfforce-pushed thefix-resolve-class-pass-class-exists-fatal-error branch fromea76884 to31de844CompareNovember 28, 2025 10:05
@nicolas-grekasnicolas-grekas changed the title[DependencyInjection] Ensure deprecation detection does not trigger a…[DependencyInjection] Ensure deprecation detection does not trigger a PHP errorNov 28, 2025
Sign up for freeto join this conversation on GitHub. Already have an account?Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@bnf@carsonbot

[8]ページ先頭

©2009-2025 Movatter.jp