AC:
* Can switch between AND and OR when both are enabled
* Builds correct query when OR is selected
* Updates query when switching from AND to OR or the other way round
Show only the top 5 values. Allow viewing additional ones. Ideally we also allow hiding the additional ones again.
The backend is already limiting to 100 (in `ElasticValueCounter`)
![Image](http...
> see what we can do on the caching side
The map approach that I described fully fixes the issue and is much simpler than using caching services, so please don't overcomplicate things.
I'm unsure what the linked code in the hooks file does (where in the UI it is used).
Having a `LocalizedTextLookup` seems plausible, especially if we have use for it in multiple places. We still...
Though like that we get one call to the `PropertyDataTypeLookup` per value. Not necessarily an issue if the used `PropertyDataTypeLookup` implementation does some caching, but certainly not elegant...
The above-mentioned logic issue seems to change the interface you need anyway.
`FacetLabelBuilder->buildLabel( string $valueCount->value, PropertyId $config->propertyId )`
And in `FacetLabelB...
Hmm... `LabelLookup` isn't the best interface... My above suggestion might not be better than the current state after all because `LocalizedTextLookup` provides an interface that makes more sense h...
My first reaction to injecting `LocalizedTextLookup` into the constructor of this class is that we should use `LabelLookup` instead. `ListFacetHtmlBuilder` does not need to know that localization i...
This is wrong. There is no guarantee that the value is an item id. The [logic that looks at the type of the property of the facet that I described for the frontend approach is still needed](https:/...