Make exposed date filter operators terminology friendly to non-technical website visitors

Thank you for sharing your idea for improving Drupal.

We are working to decide if this proposal meets the Criteria for evaluating proposed changes. There hasn't been any discussion here for over 8 years which suggests that this has either been implemented or there is no community support. Your thoughts on this will allow a decision to be made.

Since we need more information to move forward with this issue, the status is now Postponed (maintainer needs more info). If we don't receive additional information to help with the issue, it may be closed after three months.

Thanks!

Updated to Drupal 11.2.x. Still relevant.

Thanks!

Will most likely need an issue summary update

I actually did update the summary. Is there anything else you need?

There’s a standard issue template when you create new issues.

I don’t believe it was around when this ticket was created

Updating issue to follow current template.

This to be solved still after the long 10 years since started this ticket.

Granularity option is already discussed and developed at ✨ [PP-1] Views Date Filter Datetime Granularity Option Postponed . No need to address that here.

Here the patch just addressing the issue about the operator labels.

thanks but fixes should be in MRs now

junaidpv → changed the visibility of the branch 2455971-friendly-exposed-operator-labels to hidden.

junaidpv → changed the visibility of the branch 2455971-friendly-exposed-operator-labels to hidden.

junaidpv → changed the visibility of the branch 2455971-friendly-exposed-operator-labels to active.

Created an MR with a new more change to change labels for range fields from "Min" to "From" and "Max" to "To".

Here that in patch form for 10.5.x. To help composer based build process we use.

@junaidpv Thank you for the patch. Aside from the testing issue raised by @smustgrave, it gets us much of the way there.

The drop-down works, substituting the English-friendly terms on all pages.

In the view preview and the view page, I do see From and To.

I don't know whether it is feasible, but in the Views UI itself, we still get the technical labels. It would be nice is those were plain English as well:
Min
Max
Min placeholder
Max placeholder

Added test coverage, two asserts on 2 lines. Hoped for a quick win.

I would create a separate test but I don't understand why those asserts do not provide the coverage needed (yet). So not convinced that breaking it out into a separate test would make any difference.

Hopefully those asserts are right at least?

Studying the test code in relation to this issue did make me see that the names of the relevant fields have 'min' and 'max' suffixes. And perhaps other metadata also uses 'min' and 'max' so we are creating a disconnect between 'from' and 'to' and the metadata? So perhaps we can change one or two of the field names to reflect 'from' and 'to'? And/or add code comments to explain the new mapping of 'min' to 'from' etc?