Related to #403 but not the same (bc a different submodule). Seems like there is a need to allow users to "unselect" a specific Full Text search entry from a facet summary instead of "clear" all Search Full text, which is right now the beaver (not a bug, this is how we designed it). This has many issues which I can not fix:
The user (or us) can not know which Facet Entry on an Advanced Search is e.g the one that lead to no results. Which means deleting one might NOT give the user more results/achieve what is desired
We can not allow gaps between fields. So if adv_1 and adv_2 and adv_3 are passed and the user deletes adv_2, we need to move adv_3 to adv_3, means we need to, on every facet summary read how the Filter itself is configured to iterate from 1 to N allowed fields and re-build them. This is hard.
DiegoPino
commented
5 months ago
What?
Related to #403 but not the same (bc a different submodule). Seems like there is a need to allow users to "unselect" a specific Full Text search entry from a facet summary instead of "clear" all Search Full text, which is right now the beaver (not a bug, this is how we designed it). This has many issues which I can not fix:
But it was requested, so will try it out.