You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the solution you'd like
Currently, filters only allow to select one entry of a list of possible entries, which perfectly suits enums. Date ranges can only be realized by providing a list of selected dates and two filters. There should be a way to configure date value detection and provide a specialized filter view for them to set a date range.
Describe alternatives you've considered
Preset dates like "today", "yesterday", ... can already be realizable if they are provided as values. The same applies to ranges like "this month", "last month", ... If these are sufficient, this solution could even be easier to use, fits into the "standard" filter and is data-agnostic as it is independent of what kind of field might be in the search result.
Requirements
Needs to be as data-agnostic as possible. Date field detection should be configureable to also fit future date fields, e.g. like "any field that contains 'date' in its field name will be treated as date.
Needs to be open for any kind of date (range) selection implementations and libraries. A simple build-in default one should also be included.
Suitable defaults (convention over configuration) should be provided. Date ranges should be supported without any configuration in a predefined way. Configuration should only be necessary for fine-tuning and special adaption.
The text was updated successfully, but these errors were encountered:
Describe the solution you'd like
Currently, filters only allow to select one entry of a list of possible entries, which perfectly suits enums. Date ranges can only be realized by providing a list of selected dates and two filters. There should be a way to configure date value detection and provide a specialized filter view for them to set a date range.
Describe alternatives you've considered
Preset dates like "today", "yesterday", ... can already be realizable if they are provided as values. The same applies to ranges like "this month", "last month", ... If these are sufficient, this solution could even be easier to use, fits into the "standard" filter and is data-agnostic as it is independent of what kind of field might be in the search result.
Requirements
The text was updated successfully, but these errors were encountered: