-
-
Notifications
You must be signed in to change notification settings - Fork 9.6k
[DoctrineBridge] Fixed validating custom doctrine type columns #21656
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
460fe7b
to
c642345
Compare
Symfony 3.1 doesn't receive bug fixes any more. Can you rebase on the |
Ah sorry you are right. Will rebase it later today 😉 |
c642345
to
70d962c
Compare
70d962c
to
ad59370
Compare
@xabbuh done 😉 |
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.
👍 We could use the class
constants instead of strings, but that's not a blocker IMO.
Status: Reviewed
Thank you @dmaicher. |
…umns (dmaicher) This PR was merged into the 3.2 branch. Discussion ---------- [DoctrineBridge] Fixed validating custom doctrine type columns | Q | A | ------------- | --- | Branch? | 3.1 | Bug fix? | yes | New feature? | no | BC breaks? | no | Deprecations? | no | Tests pass? | yes | Fixed tickets | #21619 | License | MIT | Doc PR | - This fixes #21619 by not assuming the invalid `$value` is a Doctrine entity if its an object Commits ------- ad59370 [DoctrineBridge] Fixed validating custom doctrine type columns
This fixes #21619 by not assuming the invalid
$value
is a Doctrine entity if its an object