-
-
Notifications
You must be signed in to change notification settings - Fork 25
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
Track whether filtering was applied #263
Conversation
CI failures are unrelated to the PR. |
Can't we just return true/false if filtering was applied in the respective methods? |
You mean |
I don't really understand the problem to be honest. What would be the difference between false and null? |
|
1 similar comment
Looks good to me. @aschempp if you don't have any objections we can merge it. |
Sorry for the delay. Released as 4.0.8 :) |
I have reverted this pull request changes due to #272. @fritzmg did you test this pull request? For example, this line https://github.com/codefog/contao-news_categories/pull/263/files#diff-d540d7da12a707b7694cc9f3135ee02a80f7a211c40b9a1fd90767dfb2a8a06aR56 Similar to this line https://github.com/codefog/contao-news_categories/pull/263/files#diff-d540d7da12a707b7694cc9f3135ee02a80f7a211c40b9a1fd90767dfb2a8a06aR39 where |
True, the return type of the hooks are wrong. These hooks expect |
See #273 |
Fix for #258
This PR introduces a
CategoryFilteringNotAppliedException
in theNewsCriteriaBuilder::setRegularListCriteria
method which will allow you to returnfalse
if desired in anewsListFetchItems
ornewsListCountItems
hook. For backwards compatibilityNewsCriteriaBuilder::getCriteriaForListModule
will not throw this exception by default.