Closed Dav1dde closed 5 months ago
It can be confusing at first when deserializing (e.g. JSON) and getting an error like:
invalid type: floating point 3, expected u32
3
It shows a valid integer but it is actually a float.
Changes the error to always show at least one decimal place to avoid confusion.
Nevermind sorry for the noise, didn't realize format does not support formatting with a minimum precision, only maximum.
format
It can be confusing at first when deserializing (e.g. JSON) and getting an error like:
It shows a valid integer but it is actually a float.
Changes the error to always show at least one decimal place to avoid confusion.