I see this as the first step towards having a pluggable outputting mechanism for facet blocks. Then we need some sort of registry of the available implementations, and an interface to specify which one.

Before that, though, I'd like to have a separate class for CCK fields because the current system doesn't serve them right now.

Comments

robertdouglass’s picture

robertdouglass commented
Title: Make apachesolr_date_facet_block an interface with different class implementations » Make and apachesolr_facet_block apachesolr_date_facet_block an interface with different class implementations
robertdouglass’s picture

robertdouglass commented
Title: Make and apachesolr_facet_block apachesolr_date_facet_block an interface with different class implementations » Turn facet block functions into an interface with different class implementations

apachesolr_facet_block and apachesolr_date_facet_block are the target here.

jpmckinney’s picture

jpmckinney commented
Version: 6.x-2.x-dev » 7.x-1.x-dev
pwolanin’s picture

pwolanin commented
Project: Apache Solr Search » Facet API
Version: 7.x-1.x-dev »
cpliakas’s picture

cpliakas commented
Version: » 7.x-1.x-dev
Status: Active » Fixed

There are some more moving parts than described above, however the Facet API facet building process is abstracted so that multiple backends can use it and developers can build backend-agnostic widget plugins to modify the display however they want. marking this as fixed since the architecture addresses the goal of this issue.

Status: Fixed » Closed (fixed)

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