The graphql_compose module does not properly handle the "Between" filter for date fields in Views. When using this filter on a date field, it generates a single input field (string), instead of two separate fields (one for the minimum date and one for the maximum date). This causes the filter to fail in filtering the date range correctly.
To address the issue with the "Between" filter for date fields in Views, I propose creating a new schema type specifically for handling "Between" filters on date fields. This new schema type would correctly handle the filtering by generating two separate input fields: one for the minimum date and one for the maximum date.
Additionally, the schema type handling for Views would be updated to recognize when a date field uses the "Between" operator, and apply the appropriate filtering logic. This solution ensures that other field types and filters are not affected by the changes, maintaining compatibility with existing functionality.
Active
2.2
Code
codimpes → changed the visibility of the branch 3482318-views-between-filter to hidden.
codimpes → changed the visibility of the branch 3482318-views-between-filter to hidden.
codimpes → changed the visibility of the branch 3482318-views-between-filter to active.