-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Process deprecation of FieldDescriptionInterface::getTargetEntity() #6187
Conversation
0838d51
to
d836851
Compare
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.
Good catch @jorrit!
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 guess it's RTM. Please, squash your commits.
95e9fbf
to
7212e3d
Compare
To fix the build you need to trigger it again. it was a problem with the latest version of prophecy |
7212e3d
to
86ccd4d
Compare
86ccd4d
to
08d828c
Compare
Thank you @jorrit! |
Hi, this PR should be reverted since |
I see. The deprecation notices on runtime are unavoidable then? Perhaps the |
Maybe we should check if the class implements the method, if not fallback to the old behavior |
Subject
It seems that the change from
getTargetEntity()
togetTargetModel()
in #6108 was not fully implemented in the rest of the code. This changeset fixes some deprecation notices I get on runtime and some notices about test classes not implementingFieldDescriptionInterface
.Changelog
I think this internal change does not need a changelog entry.