Mask error when changing the value to null about formkit HOT 3 OPEN

I think we can make an exception for this particular use case, but for clarity null is generally treated as a value in FormKit whereas undefined is actually empty. So if you set the value to undefined instead of null it should work fine.

from formkit.

@justin-schroeder Thanks for the explanation. Yes, setting the value to undefined or any string (empty or not) it works without error. I wasn't expecting to get an error when setting a masked value to null programatically. The error doesn't occur when the initial values are set in the form. Also, I haven't hit this problem when using other FormKit types.

Updated playground to test undefined and empty string

from formkit.

I agree we should make it work 👍

from formkit.