Allow tokens to be used in views custom more url

Next steps for this would be to add test coverage for the future.

And we should update the help text for the field to specify that it supports token or people will probably not realise.

Tested this out using the test token in the MR and I get view block variables auto added to it. example node/[view:id] returns /node/content?title=&type=All&status=All&langcode=All

Not sure that is desired.

Which shows the test needs to be tweaked to check the full url value.

Hi, In your example the view(content) has exposed filters so which is why exposed variables are added to the "more link" and this came from the following code

    // Merge the exposed query parameters.
    if (!empty($this->view->exposed_raw_input)) {
      $url->mergeOptions(['query' => $this->view->exposed_raw_input]);
    }

on the getMoreUrl() function.

In our tests, we are testing the following view test_display_more and this doesn't have any exposed filters. So It only returns the following result
ie: node/[view:id] => /node/test_display_more

Still convinced they shouldn’t be added. Think it introduces a bad user experience.

Pushed the patch from the MR diff.

This might be a duplicate of ✨ Allow token replacement for array URLs on views custom URLs Needs work