-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
use PropertyAccessorInterface instead of PropertyAccessor #30136
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
Conversation
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. Should we backport to 3.4 actually?
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 like something for 3.4 indeed.
I don't know how you guys usually handle this, but since the change is very small and probably has no negative impact, it could make sense. Let me know if i should open PR's for other branches as well. |
Thank you @nick-zh. |
…(nick-zh) This PR was submitted for the master branch but it was squashed and merged into the 3.4 branch instead (closes #30136). Discussion ---------- use PropertyAccessorInterface instead of PropertyAccessor [Validator] [Constraints] use PropertyAccessorInterface instead of PropertyAccessor | Q | A | ------------- | --- | Branch? | master | Bug fix? | no | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #30133 (partially) | License | MIT | Doc PR | none Commits ------- 3e3ca9d use PropertyAccessorInterface instead of PropertyAccessor
[Validator] [Constraints] use PropertyAccessorInterface instead of PropertyAccessor