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.
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix EventArgs::getEntityManger deprecation #2639
fix EventArgs::getEntityManger deprecation #2639
Changes from 2 commits
4b45e37
e48c9ca
4e3ff09
c8ed0b2
7c50aab
fc2518a
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this be
\Error::class
?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think a TypeError is fine if we look at it as the $args class (type) not implementing the getObjectManager method. If we look at it like "the type $args::class must implement getObjectManager for version 4.0" then it should be \Error.
Edit: never mind, you're right. It wouldn't throw a TypeError.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If there won't be an
instanceof
check here, I guess we can't even be sure if\Error
will be thrown. If that is the case, I guess we should say something like "it will be not supported" instead.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No instanceof check is required, calling a method that doesn't exist throws an \Error.
Fatal error: Uncaught Error: Call to undefined method OldEventArgs::getObjectManager()
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we maybe add instanceof checks with
LifecycleEventArgs
,LoadClassMetadataEventArgs
,ManagerEventArgs
andOnClearEventArgs
? Maybe they should all extend fromManagerEventArgs
indoctrine/persistence
🤔 ? For thegetObjectManager()
call I mean, or any other solution?It would be nice to finally move this forward.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see any need to do that. The \method_exists call will make sure that it's fully backwards compatible for now.
If anything, that would be a discussion for later (when Doctrine ORM 3.0 releases and getEntityManager is removed
and we release DoctrineExtensions 4.0) when we remove the \method_exists call and directly call
getObjectManager()
. But even then, I don't see a point in checking the type of the args - all we care about is that they abide by Doctrines interfaces and implementgetObjectManager()
instead ofgetEntityManager()
(that we currently also call without checking).Check warning on line 108 in src/Mapping/Event/Adapter/ORM.php
Codecov / codecov/patch
src/Mapping/Event/Adapter/ORM.php#L102-L108
Check warning on line 129 in src/Mapping/Event/Adapter/ORM.php
Codecov / codecov/patch
src/Mapping/Event/Adapter/ORM.php#L123-L129
Check warning on line 108 in src/Uploadable/Event/UploadableBaseEventArgs.php
Codecov / codecov/patch
src/Uploadable/Event/UploadableBaseEventArgs.php#L105-L108
Check warning on line 110 in src/Uploadable/Event/UploadableBaseEventArgs.php
Codecov / codecov/patch
src/Uploadable/Event/UploadableBaseEventArgs.php#L110
Check warning on line 118 in src/Uploadable/Event/UploadableBaseEventArgs.php
Codecov / codecov/patch
src/Uploadable/Event/UploadableBaseEventArgs.php#L118
Check warning on line 133 in src/Uploadable/Event/UploadableBaseEventArgs.php
Codecov / codecov/patch
src/Uploadable/Event/UploadableBaseEventArgs.php#L130-L133
Check warning on line 135 in src/Uploadable/Event/UploadableBaseEventArgs.php
Codecov / codecov/patch
src/Uploadable/Event/UploadableBaseEventArgs.php#L135
Check warning on line 143 in src/Uploadable/Event/UploadableBaseEventArgs.php
Codecov / codecov/patch
src/Uploadable/Event/UploadableBaseEventArgs.php#L143
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe we could even replace these mocks to use a class that is no deprecated, like
Doctrine\ORM\Event\PrePersistEventArgs
orDoctrine\ORM\Event\PreUpdateEventArgs
.