Add Better Exposed Filters integration

That would be suuuper awesome! +1 for this suggestion!

Doesn't seem to work yet, the autocomplete endpoint returns a HTTP 403 response. Diving into the controller code, I noticed $selection_settings is FALSE, causing this code to be triggered:

// Disallow access when the selection settings key is not found in the
// key/value store.
throw new AccessDeniedHttpException();

Something else: it would look better if these widgets would be the same height as other form fields, but that might be a Gin specific issue (not tested using Claro).

@DieterHolvoet Thanks for the review!

I've added a quick change to fix the issue with the height in the Tagify element.

The rest of the implementation works fine for me.

Claro

Gin Theme

Also works with Olivero.

You're right, it does work for taxonomy autocomplete filters. I forgot only taxonomy autocomplete filters are currently supported by core, I'm using a patch from ✨ Continuation Add Views EntityReference filter to be available for all entity reference fields Active to support other entity types as well. It didn't work in combination with that patch, but I found a fix and pushed it to the fork. One minor issue I noticed: it's not possible anymore to submit the filter form by pressing enter.

Thank you for working on this!