-
-
Notifications
You must be signed in to change notification settings - Fork 6.9k
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
merge ActiveRelation into ActiveQuery #2497
Conversation
allow extending only one class to add scopes, fixes #2146 TODO: - [ ] adjust guide docs - [ ] adjust README files of extensions - [ ] finish work and fix test breaks
Great job! Should we also merge |
They are but it is good to separate the logic imo. This way you see which methods are for which kind of query by just checking from which trait they come for example. It also still possible to create AR with an extra relation class if there is any need. |
WIP merge ActiveRelation into ActiveQuery
Updated the docs and merged. |
Should the changes in .travis.yml and composer.json really be in there? :o |
They are not related to this change but I made them while noticing that the test chain was broken a bit when working local so I fixed it. |
👍 |
WIP merge ActiveRelation into ActiveQuery
allow extending only one class to add scopes, fixes #2146
TODO: