Views exposed filters don't combine with contextual filters when using exposed form in block

#59 solves the issue for me using Drupal 9.5.5. I'm using a view with a contextual filter and I'm exposing the filters with Better Exposed Filters. Also the Media Library is working normally. Anyway, I removed an empty if.

Ups, my fault. I fixed my last change.

Re-roll of #64 for 11.x.

The Needs Review Queue Bot → tested this issue.

While you are making the above changes, we recommend that you convert this patch to a merge request → . Merge requests are preferred over patches. Be sure to hide the old patch files as well. (Converting an issue to a merge request without other contributions to the issue will not receive credit.)

There's no issue summary. Please use the standard issue template.

Problem/Motivation

View exposed filters and contextual filters cannot be used together. The contextual filter is ignored when the exposed filters are used.

Steps to reproduce

Create a View with both exposed filters and contextual filters. Try to use the exposed filters.

Proposed resolution

Pass the existing contextual filter arguments to the View when exposed filters are used.

Remaining tasks

Finalize implementation.

User interface changes

None except that the filters will work as expected.

API changes

None.

Data model changes

None.

Release notes snippet

Left some comments on MR.

Will need some test coverage to show the issue.

Hiding patches for clarity.

Thanks; changes in comments committed

I tested the code from MR and got the next error:
Fatal error: Type of Drupal\views\Form\ViewsExposedForm::$routeMatch must not be defined (as in class Drupal\Core\Form\FormBase) in /var/www/html/web/core/modules/views/src/Form/ViewsExposedForm.php on line 21

I have removed using of constructor property promotion which should resolve the $routeMatch error.

Thanks for keeping this going

Was previously tagged for tests so moving back to NW for that.

Left a comment about using promotion that should simplify things.

I removed the constructor property promotion because when it is used, the property has a type declared. That type doesn't match the parent and so you get the error shown in #74.

To avoid all this, I just updated the merge request to use ::getRouteMatch().

This was available for Drupal 7, https://www.drupal.org/project/filter_harmonizer →

The changes from the latest MR solved the problem for me. Thank you!
Setting it as RTBC.

This still needs automated test coverage before it can be committed.

In my latest change I allowed the inclusion of parameters with the all value.
Without this change, URLs like /foo/bar/[arg_0]/[arg_1]/[arg_2] throw an exception if [arg_2] has a value but [arg_1] is all.