Conditionally extend the old AnnotationDriver class
#9671
Merged
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 Apr 22, 2022
malarzm
approved these changes
Apr 22, 2022
greg0ire
approved these changes
Apr 22, 2022
This was referenced Apr 22, 2022
derrabus
added a commit
to derrabus/orm
that referenced
this pull request
Apr 22, 2022
* 2.13.x: Conditionally extend the old AnnotationDriver class (doctrine#9671)
derrabus
added a commit
to derrabus/orm
that referenced
this pull request
Apr 22, 2022
* 2.13.x: Conditionally extend the old AnnotationDriver class (doctrine#9671)
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.
Fixes #9668.
Replaces #9670.
This PR restores the old inheritance chain of
AnnotationDriverandAttributeDriverif Persistence 2 is installed. Unfortunately, DoctrineModule uses a flawed logic to determine the constructor arguments of a mapping driver class, see doctrine/DoctrineModule#774. With this change, that logic should work again.When merging this PR up to 3.0.x, I would simply revert it.