As mentioned in the post at http://drupal.org/node/1156606#comment-4725960, there could be a filter that prevents facets from being displayed if there are only x number of items. This is simple for flat trees, however it is slightly more difficult when hierarchical facets are taken into account. This filter must be smart enough to handle that use case.

Comments

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented

Subscribing.

cpliakas’s picture

cpliakas commented
Priority: Normal » Minor

Bumping down in priority, because someone could implement this outside of the module as a result of the pluggable filter system.

cpliakas’s picture

cpliakas commented
Component: Code » Contrib

Adding to the Contrib component, which means that I am looking for this functionality to be added outside of this module in a separate contrib.

cpliakas’s picture

cpliakas commented
Project: Facet API » Facet API Extra
Component: Contrib » Code
Priority: Minor » Normal

Moving over to Facet API Extra for consideration.

SergeyR’s picture

SergeyR commented

may be somebody show me case from real life -if hypotetically implemented "don't show items that don't narrow result" is NOT ENOUGH
still now -i cant imagine such cases
At least it must be different priority untill no real life requests are presented

SergeyR’s picture

SergeyR commented

changing my opinion about this issue
i think in case when only 1 item happens to be -is not right just hide it !
in this approach we will never see dependent facets as parent choice is hidden
another idea -to make this choice automatically -also not correct
i think may right compromize here to ASK user is this the single facet item appropriate or not? -so in another word is it sense to show dependent facets (it may be not the only one item!!!)
The pure realization of this issue is correct for case where no dependent facets exist ,or may be they also have the only one item. Little bit sofisticated logic ))

ygerasimov’s picture

ygerasimov commented
Status: Active » Fixed

Implemented. Committed a3655ca

Automatically closed -- issue fixed for 2 weeks with no activity.