The exposed sort identifiers are not configurable in the same way as the exposed filters identifiers. This leaks some internal IDs in the URL and that we can consider part of the UI, even is in the browser address bar, not in the page. For example, with Search API, the user might see such parameter/value in the query string &sort_by=search_api_relevance, which is not elegant at all.
Allow the exposed sort identifiers to be configured.
None.
New, textfield element in the exposed sort configuration subform.
New parameter string $handler_type in \Drupal\views\Plugin\views\display\DisplayPluginBase::isIdentifierUnique() signature.
None.
When exposing a sort in the exposed form, the site builder is able to configure the identifiers that are exposed in the URL as query parameter values.
While working on a Rest API via Views, I noticed that exposed Sorts could not have custom identifier likes Filters could. As such, I have created a (probably terrible) patch to add in this functionality.
Please comment on items that need to be changed or fixed and I will be happy to do so!
Fixed
9.3
Last updated
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.