When I set a string field as null, I get a string “null”.
What I expect: receive null value, not a string. By the way, for string or boolean fields I get null as expected.
This is especially bad for using ternar operator where I receive “null” if null.
Undefined
The same with undefined. In 0.236.0 when I defined a string field with a non-existent value to a string, nothing happened. I used this to check if the prop was defined.
In 1,8 2 a field with “undefined” string value is created. Why, it shouldn’t be like that.
Internally for the string we will try to convert the value as we are expecting it to be a string, We should probably not do that for null / undefined. I will get a dev ticket created now for a future change.