[FrameworkBundle][PhpUnitBridge] Configure doctrine/deprecations as expected #50468
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced May 30, 2023
nicolas-grekas
force-pushed
the
doctrine-deprec
branch
from
48876a1
to
cbe4808
Compare
carsonbot
changed the title
|
Updated to enable the trigger when using the phpunit-bridge also. |
ostrolucky
approved these changes
May 30, 2023
mtarld
approved these changes
May 30, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Following doctrine/deprecations#41, so that deprecations from Doctrine take the same code path as any other deprecations in Symfony apps.
Submitted to 6.3 to notify about the deprecations as early as possible but not too early to not trigger new deprecations in existing apps.