-
-
Notifications
You must be signed in to change notification settings - Fork 890
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
[Do not merge] Revert merge master into 2.2 #1923
[Do not merge] Revert merge master into 2.2 #1923
Conversation
…ow_dependencies Fix the Behat test suite with low dependencies
Page number int casting
Add missing doctrine alias removed in [email protected]
fix exists filter
Enable item route on collection subresources
The OrderFilter is still triggering bad deprecation/function calls
* Allow GraphQL to filter on nested property fixes api-platform#1714, api-platform#1867 * Allow ordering on nested property values
Seems better than my approach of |
@sroze I told you so 😛 |
We had to try both ways 🤷♂️ |
Nice work ❤️ Could you quickly explain what you did? (I'm assuming
Which ones? Yeah it's okay I just need to make sure I have the work locally somewhere :P.
Smart move although we could force push 😈 |
@soyuka See the checklist above. And you can rebase them based on the old commits in this repo. We're not going to rebase. This is only how I come up with the manual revert commit. =P |
Are both fixes to the 2.2 branch. Only #1899 should've been merged on master instead of 2.2. |
Travis is passing: https://travis-ci.org/teohhanhui/api-platform-core/builds/373994838 The merge conflicts here are to be ignored. 😄 |
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.
Let's have one revert commit instead. I know you have it ready @teohhanhui, thank you ❤️
Closed in favor of #1924 |
Relevant merged PRs (that should actually go into
2.2
) since #1850:2.2
branch without PR)d34fba5...2.2
(start from after d611aa0 and 3fdd546 which was when #1850 was merged)
This is done with
git cherry-pick
, so it's not meant for merging. If everything looks good, I will use this to create a revert commit and open another PR.Unfortunately for @soyuka, you'll probably have to resubmit your 2 PRs if they're appropriate for
2.2
. (Unless they can be rebased here.) Do you think that's okay?