Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork9.7k
[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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
460fe7b toc642345Comparexabbuh commentedFeb 20, 2017
Symfony 3.1 doesn't receive bug fixes any more. Can you rebase on the |
dmaicher commentedFeb 20, 2017
Ah sorry you are right. Will rebase it later today 😉 |
c642345 to70d962cCompare70d962c toad59370Comparedmaicher commentedFeb 21, 2017
@xabbuh done 😉 |
xabbuh left a comment
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 theclass constants instead of strings, but that's not a blocker IMO.
Status: Reviewed
fabpot commentedFeb 21, 2017
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 | -Thisfixes#21619 by not assuming the invalid `$value` is a Doctrine entity if its an objectCommits-------ad59370 [DoctrineBridge] Fixed validating custom doctrine type columns
Uh oh!
There was an error while loading.Please reload this page.
Thisfixes#21619 by not assuming the invalid
$valueis a Doctrine entity if its an object