-
Notifications
You must be signed in to change notification settings - Fork 7
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
[Feature Request] And/Or filters over the Causer Model and Subject Model #19
Comments
We solve this tomorrow, if we have the time. This one, we can push as a non-breaking change.
OR 💯
I... don't understand the question/dilemma... could you please rephrase? |
Long story short, after asking @pxpm his opinion, in order to do this, we need to do some nasty stuff 😅 If we have the key to combine the results, in order to have it combined, we need to disable the filters and add the queries manually. Should we proceed? 😬 |
Ouch! So let me understand...
Is that correct? If so... I'm ok with it. I like it. If we could also change the title / heading for this filtered view, so that it makes it clear it's a sub-filtration... that would be great. |
Most of the work is done at https://github.com/Laravel-Backpack/activity-log/tree/combined-filter. |
Feature Request
When coming for a Model that is both Subject and Causer, should the selected filters be with AND (default) or should it be OR?
Should we create that exception?
What if I come from the entry button?
Both the causer model and subject model are selected with
User::class
, and model and subject with Demo User entry. How should the filters behave?The text was updated successfully, but these errors were encountered: