-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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 setting readonly properties in different scopes #10059
Fix setting readonly properties in different scopes #10059
Conversation
f67c840
to
0693ae3
Compare
There is: |
Good to know, thanks, I will adjust that. |
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.
looks ok to me
a9af8c7
to
d1844a2
Compare
d1844a2
to
fc9ef70
Compare
This PR handles embeddables but other properties also are impacted by #10049 😕 |
There hasn't been any activity on this pull request in the past 90 days, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 7 days. |
This pull request was closed due to inactivity. |
Looks like #10049 can be fixed like this, it simply uses the described method from the RFC by changing the scope to the declaring class.
It will only be executed if the
isReadOnly
-method is present, this will also check if PHP is 8.1 or higher, I am not sure if there is any performance impact on this.As I described in the
tests/Doctrine/Tests/ORM/Functional/Ticket/GH10049Mocks.php
file, it is required to have them outside, otherwise, the file will be fully parsed by PHP 7.4 and will throw an error because the keywordreadonly
is new and not backwards compatible.Fixes: #10049