Ajax facet block seems to lose Views context (filters, etc)

Patch #33 🐛 Ajax facet block seems to lose Views context (filters, etc) RTBC worked for me.
My current use case.
Drupal views with an exposed filter search input and exposed and the filters are exposed as a block and the view is an exposed block.
Ajax turned on for the view using with combination with views ajax history module → and this patch 🐛 Facets searches don't update results Needs review .

Now ajax works and respects facets + the views exposed filter yay!

Current markup with inside a paragraph using twig tweaks:

{# Site search view exposed form #}
<div class="search-form-container">
{{ drupal_entity('block', 'site_search_form', check_access=false) }}
</div>
{# Facets #}
<div class="facets-container">
  {{ drupal_block('facet_block:content_type') }}
  {{ drupal_block('facet_block:subject') }}
  {{ drupal_block('facet_block:media') }}
</div>
{# Site search view exposed form #}
{{ drupal_view('site_search', 'site_search_default') }}

@burnellw_cit , patches should be created relative to the module, not your project.

You should also rely on composer to apply properly rolled patches such as patch number 32

https://www.drupal.org/docs/develop/git/using-git-to-contribute-to-drupa... →

@burnellw_cit,
A properly rolled patch looks like this:

diff --git a/src/Plugin/facets/facet_source/SearchApiDisplay.php b/src/Plugin/facets/facet_source/SearchApiDisplay.php
index 017f34f..7eac4b1 100644
--- a/src/Plugin/facets/facet_source/SearchApiDisplay.php
+++ b/src/Plugin/facets/facet_source/SearchApiDisplay.php

Yours was made relative to your project, is incorrect.

diff --git a/modules/contrib/facets/src/Plugin/facets/facet_source/SearchApiDisplay.php b/modules/contrib/facets/src/Plugin/facets/facet_source/SearchApiDisplay.php
index d5b7042d..4a6d2510 100644
--- a/modules/contrib/facets/src/Plugin/facets/facet_source/SearchApiDisplay.php
+++ b/modules/contrib/facets/src/Plugin/facets/facet_source/SearchApiDisplay.php

If you used composer to specify patches you would be able to use correctly rolled patches such as patch #32.

Please review this with esteemed colleagues , for further assistance please reach out to someone on slack in the Drupal channels or on https://drupalchat.me . Your organisation may have to change it's process/build slightly to adhere to built norms.

I have created a fork with the changes from #32 and added a check for the route object, this can be null if the request is serialized and used at a other time, we use this to get the view options on cron when processing some jobs.

@nickvanboven, the 2 fails seen in MR 137 comment#40 not related to your changes.

🐛 HEAD tests failing since March 23, 2023 Closed: duplicate