distinct() updates QueryBuilder state correctly#10789
Conversation
|
2.14.x is no longer maintained. I retargeted on 2.15.x, and now there is a conflict. |
eec49b5 to
73237c2
Compare
|
Conflicts are resolved now. |
|
The build failure seems unrelated to your changes 🤔 |
|
|
|
Should I fix those in my PR or are these fixed separately? |
|
I don't think you can fix them: slevomat/coding-standard#1585 |
|
Their maintainers might provide a fix for the broken comment parsing in their latest release soon. I'll leave it for now and check back on Monday. |
|
They are usually quite swift, so yeah, maybe. Also, it might be possible to work around some of the issues (use |
|
Addressed in #10790 |
Previously calling distinct() when the QueryBuilder was in clean state would cause subsequent getDQL() calls to ignore the distinct queryPart Fixes doctrine#10784
73237c2 to
efb50b9
Compare
|
Thanks @macroparts ! |
|
Thank you @greg0ire ! |
Previously calling distinct() when the QueryBuilder was in clean state would cause subsequent getDQL() calls to ignore the distinct queryPart
Fixes #10784