Hi,
I’m getting some unexpected query parameters passed back to
the server when redefining some of the grid’s filter operators.
For example, if I customize the filter operators with the following:
filterable: {
operators: {
string: {
"Contains"
:
"Contains"
,
"DoesNotContain"
:
"Does not contain"
,
"Equals"
:
"Is equal to"
,
"DoesNotEqual"
:
"Is not equal to"
,
"StartsWith"
:
"Starts with"
,
"EndsWith"
:
"Ends with"
}
}
},
I would then expect one of the query parameters to be the following when using the “Equals” operator.
filter[filters][0][operator]=Equals
However, instead it sends the standard equals operator:
filter[filters][0][operator]=eq
The behaviour is as I’d expect for the other operators. e.g.
filter[filters][0][operator]=StartsWith
I only experience the problem with the equals, greater than
and less than operators.
Here is a jsfiddle demonstrating the problem. Of course the
filters don’t actually work as the server side code doesn't support the custom operators. You need to look at the requests sent to the server to see the problem.
https://jsfiddle.net/snowman611/6mnzbc1e/3/
Has anyone else had this problem? What am I doing wrong?
Thanks,
Andrew