search

MudBlazor / MudBlazor

Blazor Component Library based on Material design with an emphasis on ease of use. Mainly written in C# with Javascript kept to a bare minimum it empowers .NET developers to easily debug it if needed.
http://mudblazor.com
MIT License
7.22k stars 1.18k forks source link

Lack of Range Operator for Date and Number Filtering in DataGrid #8836

Closed yangf85 closed 2 weeks ago

yangf85 commented 2 weeks ago

Feature request type

Enhance component

Component name

DataGrid

Is your feature request related to a problem?

No response

Describe the solution you'd like

Description: The current implementation of filters in the DataGrid component does not provide an operator that allows users to specify a range when filtering by date or number fields. This limitation prevents users from performing searches within a specific date or time interval, which is a common requirement for data analysis and reporting purposes.

Expected Behavior: Users should be able to select a range operator for date and number fields in the filters. This operator would enable filtering data that falls within a specified start and end date or numerical range.

Suggested Solution: Implement a new filter operator that supports range selection for date and number columns. This operator should provide two input fields to define the lower and upper bounds of the range, allowing users to filter for records that fall between these two values.

Impact: Adding a range operator for date and number filtering would greatly enhance the DataGrid's functionality, making it more useful for users who need to perform complex data queries and analyses.

Have you seen this feature anywhere else?

No response

Describe alternatives you've considered

No response

Pull Request

Code of Conduct

Anu6is commented 2 weeks ago

This can currently be achieved by applying multiple filters to the field

image

ScarletKuro commented 2 weeks ago

This can currently be achieved by applying multiple filters to the field

I always thought that this one is obvious if you want to have a range for numbers.

Implementing range in a single filter would be troublesome for current implementation. Considering that filters still do not have the capability to add own filter ui for custom types (I kind of abandoned this https://github.com/MudBlazor/MudBlazor/pull/6626, but this one could partially solve it too as you'd be able to remap existing ones too, but still would require the enchantment of the abstraction for the range feature) and there is still unresolved things with localization https://github.com/MudBlazor/MudBlazor/pull/8581#issuecomment-2054087363 etc this issue is no priority at all. PRs are obviously welcome, but I would suggest to focus on more important topics.

yangf85 commented 2 weeks ago

@Anu6is

Thank you, I've tried it, and it works very well. Given the current circumstances, this is the only option available.