Open kendo-bot opened 3 years ago
Issue only replicates when schema.model.fields.type is specified as the field parser is used in this scenario.
Behavior is introduced with the following fix:
@ag-petrov, @gyankov, Hello. Is there any plan for when this bug will be fixed? I upgraded the application from .net framork to .net core and it stopped working correctly. In the previous version it looked like this:
Hi @a-witkowski, this behavior was introduced when we implemented null filtering. Thus, we parse "null" strings to actual null values. Reverting it is not an option, we could, however, add a setting to the datasource, that when set explicitly, will not parse "null" strings to nulls. Would that work for you?
I am raising the priority of this report, and I will discuss with them any other options that might not require additional configuration.
Hi, @gyankov. it might work. The reason is that the real data does contain strings with the value "null", because there are no forbidden words, the user can enter any text. And users enter exactly "null" to see that a value has been entered, but it is empty. Stupid solution, but as it is.....
Enhancement
FIltering a string field in the Grid with Contains operators and value null throws an error
Reported in 1492459
Current behavior
FIltering a string field in the Grid with Contains operators and value null throws an error![image](https://user-images.githubusercontent.com/46747298/97304599-9fb27100-1864-11eb-8f52-ee3e1cd48eee.png)
https://demos.telerik.com/aspnet-mvc/grid/remote-data-binding
Expected/desired behavior
An error shall not be thrown
Environment Kendo UI version: [all] Browser: [all]