IMIO / imio.smartweb.core / 38398924472

88%

push

github

Web 4495 searchable custom taxonomy (#97)

* WEB-4495 : Override ``IFacetedCatalog`` with ``SmartwebFacetedCatalog`` so a taxonomy created
  through the web no longer breaks faceted search

* WEB-4495 : Keep taxonomy criteria of navigation tree queries

collective.solr sends a query that contains a navigation tree path to the
portal catalog (collective/solr/dispatcher.py:73-74). This occurs also
when "use_solr" is set. The "Navigation path" criterion of a Collection
makes such a query.

matches_solr_requirements did not do this check. Thus uses_solr returned
True for such a query, and strip_unindexed_taxonomies removed the unknown
taxonomy. The portal catalog then answered without the taxonomy filter,
and showed results that do not have the selected value.

Add the check before the "use_solr" check, in the same sequence as
collective.solr. Document in SmartwebFacetedCatalog that it sees the
widget query only, and not the Collection query.

Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>

* WEB-4495 : Apply the operator of dict taxonomy criteria in memory

The eea checkbox and multiselect widgets send a taxonomy criterion as
{"query": [...], "operator": ...}. "and" is their default operator
(eea/facetednavigation/widgets/checkbox/widget.py:64 and 99-101).

filter_and_count gave this dict to as_tuple, which returned its keys
("query", "operator"). No result had these values, thus a text search
with a checked box on a taxonomy created through the web showed an empty
page. Also, the filter always used "or", and ignored "and".

Add criterion_terms, which reads the values and the operator of a plain
or dict criterion, and matches_criterion, which applies "and" or "or" as
a KeywordIndex does. filter_and_count uses them. The facet counts do not
change.

Assisted-by: Claude Opus 5.5 <noreply@anthropic.com>

121 of 137 new or added lines in 1 file covered. (88.32%)

6381 of 7217 relevant lines covered (88.42%)

0.88 hits per line