Neg. operators (neq,sneq,nin) support in filter query builder (addFieldToFilter) #371
Conversation
|
This one is mandatory for targetrules implementation : allow to exclude current product from the results. |
|
Hey @afoucret , whats the status of this PR? Is there still something to do? I currently have a shop, where another extension (which is needed) uses "nin" filters for Categories and breaks autocompletion. The workaround was to remove the categories from the auto completion, but I need this feature in the future. If there is anything I can do (coding, testing, etc.) I'd like to help finish this PR |
|
/cc @romainruaud ping? |
|
@rbayet can you check this PR is still OK for a potential merge on 2.6.x ? According to the Github GUI, it should, but can you also test it by your side ? Regards |
rbayet
force-pushed
the
addfieldtofilter_negative_op
branch
from
151044c to
7d9ffc7
Compare
|
@romainruaud the PR was no longer OK for a merge on 2.6.x (some conflicting changes in \Smile\ElasticsuiteCore\Search\Request\Query\Filter\QueryBuilder). I rebased on 2.6.x and quickly tested in \Smile\ElasticsuiteVirtualCategory\Model\Preview::prepareProductCollection but trying to find a way to fully test fulltext search navigation. |
rbayet
changed the title
rbayet
force-pushed
the
addfieldtofilter_negative_op
branch
from
7d9ffc7 to
6f7e442
Compare
rbayet
changed the title
|
Tested from \Smile\ElasticsuiteCatalog\Plugin\LayerPlugin::setSortParams in catalognavigation. |
Based on 2.3.x code, a quick-and-dirty solution to support ->addFieldToFilter operators "neq", "sneq" and "nin" in the filter query builder, by simpling negating the terms query generated.
Allows a range of functional negative filters on the product collection: exclude some products by their id, filter out some attribute sets, product type, etc.