Use native views for url generation when using exposed filter facets

Patch attached.

To use this, follow these steps.

- Enable the "facets_exposed_filters" submodule
- On your views facetsource, change the url processor to "Views exposed filters"
- Create facets (the widget part will be hidden now, as all widget related settings are now managed in views/better exposed filters)

Go to views, and add a Facet Filter

Change "Exposed form" to Better exposed filters and select which widget you want.

PS, for now, a patch for Better Exposed filters is still required, to make BEF support this module.

Attached is the patch for better exposed filters, which is also required to make this work.

Once this issue is RTBC, we can create an actual issue in BEF issue queue to ask them to commit this patch too.

Attached is an update which also supports facet count, dependent facets and empty facets.

Patch on BEF from #3 still required.

For now, only hierarchy does not seem to work. We might need to write a custom BEF widget as there is not any hierarchy widget available for now.

+++ b/modules/facets_exposed_filters/facets_exposed_filters.info.yml
@@ -0,0 +1,11 @@
+core_version_requirement: ^9.2 || ^10.0

I already raised the requirement to ^10.1

10.0 will reach EOL before we'll have a final 3.0.0 release.

In general I vote for commiting this patch as it is and to provide a better base for further development and bugfixes of the 3.0.x branch.
But doesn't the erroneous FacetsViewsAjaxController influence this patch somehow?
See https://www.drupal.org/project/facets/issues/3379445#comment-15275979 🐛 Facets breaks all AJAX views that uses pagers even without facets Fixed

We should upload patch #3 to ✨ Compatibility with facets 3.0.x Needs review .

Bumped to 10.1 version

So, just trying to confirm direction here. Is the idea that this will be the way forward for facets? Cause having them in the exposed filters really limits UX. It's pretty common among product facets to have filters/sorts above and facets in a sidebar area, but by making them part of exposed filters they must be in the same form, is there any thought into how this could work?

The old block approach is still supported, but without AJAX.

I'm aware of the form issue. We already managed to have exposed filters in two areas. But it is a solution I don't want to put into the module as it is.
I think this will be next topic if everything basically works.

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