You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Our current string deserializers consider coercion configurations for integer input types (#3608) but not for boolean or floating point number inputs. This is an issue because the library lets users configure float-to-string and boolean-to-string coercion behavior, which the corresponding deserializers do not stick to.
Describe the solution you'd like
Implement the handling for the following coercion configurations:
boolean to string coercion config: [Fail, TryConvert, AsNull, AsEmpty]
floating point number to string config: [Fail, TryConvert, AsNull, AsEmpty]
Is your feature request related to a problem? Please describe.
Our current string deserializers consider coercion configurations for integer input types (#3608) but not for boolean or floating point number inputs. This is an issue because the library lets users configure float-to-string and boolean-to-string coercion behavior, which the corresponding deserializers do not stick to.
Describe the solution you'd like
Implement the handling for the following coercion configurations:
Usage example
Additional context
Similar issues:
StdDeserializer
coerces ints to floats even if configured to fail #3503 (int-to-float)CoercionConfig
#3013 (int-to-string)The text was updated successfully, but these errors were encountered: