-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DoctrineBridge] issues with UniqueEntityValidator on 7.1-RC1 #57075
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
Comments
Ok I managed to reproduce it now on symfony-demo as well. See https://github.com/symfony/demo/compare/main...dmaicher:symfony-demo:reproduce_issue_57075?expand=1
|
same for me |
Added a failing test case here: https://github.com/symfony/symfony/compare/7.2...dmaicher:symfony:issue_57075?expand=1 Will see if I find the time in the next days to take a look at fixing it |
Good, you found it. I broke untested code. |
xabbuh
added a commit
that referenced
this issue
May 31, 2024
…ject (HypeMC) This PR was merged into the 7.1 branch. Discussion ---------- [DoctrineBridge] Fix `UniqueEntityValidator` with proxy object | Q | A | ------------- | --- | Branch? | 7.1 | Bug fix? | yes | New feature? | no | Deprecations? | no | Issues | Fix #57075 | License | MIT Before #38662, `$fieldValue = $class->reflFields[$fieldName]->getValue($entity);` was used to get the value of a property, so it makes sense to keep using it when the object is an entity. Commits ------- 99f279b [DoctrineBridge] Fix `UniqueEntityValidator` with proxy object
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Symfony version(s) affected
7.1 RC1
Description
I just tested 7.1 RC1 on my biggest app and I noticed this error:
How to reproduce
Unfortunately I cannot reproduce this issue yet on a smaller app likesymfony-demo
. Still looking into it 😕See #57075 (comment)
Possible Solution
use
PropertyAccessor
to get the value here?Additional Context
Downgrading DoctrineBridge and PropertyInfo to 7.0.7 solves the issue for me.
The text was updated successfully, but these errors were encountered: