filterModel prop. When this prop is not passed, the DataGrid supports more than one criteria at a time, but it cannot show which fields are filtered in the DataGrid headers. CrudOperators type in Refine is used to define the operators that can be used in filtering data. Here's what each operator means:"eq": Equal"ne": Not equal"lt": Less than"gt": Greater than"lte": Less than or equal to"gte": Greater than or equal to"in": Included in an array"nin": Not included in an array"ina": Column contains every element in an array"nina": Column doesn't contain every element in an array"contains": Contains"ncontains": Doesn't contain"containss": Contains, case sensitive"ncontainss": Doesn't contain, case sensitive"between": Between"nbetween": Not between"null": Is null"nnull": Is not null"startswith": Starts with"nstartswith": Doesn't start with"startswiths": Starts with, case sensitive"nstartswiths": Doesn't start with, case sensitive"endswith": Ends with"nendswith": Doesn't end with"endswiths": Ends with, case sensitive"nendswiths": Doesn't end with, case sensitive"or": Logical OR"and": Logical ANDCrudFilters type, which is an array of CrudFilter objects. Each CrudFilter can be a LogicalFilter or a ConditionalFilter, and they use these operators to define the conditions for filtering data.useDataGrid hook in Refine provides a way to integrate the MUI DataGrid with Refine's data fetching and manipulation capabilities. However, it seems that there might be some limitations or differences in the filter operators supported by the MUI DataGrid and those defined in Refine's CrudOperators.filterModelCrudOperatorsCrudOperators"eq""ne""lt""gt""lte""gte""in""nin""ina""nina""contains""ncontains""containss""ncontainss""between""nbetween""null""nnull""startswith""nstartswith""startswiths""nstartswiths""endswith""nendswith""endswiths""nendswiths""or""and"CrudFiltersCrudFilterCrudFilterLogicalFilterConditionalFilteruseDataGriduseDataGrid({
filters: {
initial: [
{
field: "name",
operator: "contains",
value: "Foo",
},
],
},
});