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
If a field is marked numeric or number and the value parsed begins with . instead of a leading 0 the period is stripped off. For instance, if you pass .1 instead of 0.1 the parsed value becomes 1. This is a problem. This is related to the regex used to parse numbers expecting a sign, then digits, then optionally a period and more digits. However, the optional bit is ignored, the digit is captured and the period is dropped. This could be fixed by adding . to the character class before the first digit but I'm not sure that is the correct thing to do in all cases. Here's a gist example.
The text was updated successfully, but these errors were encountered:
If a field is marked
numeric
ornumber
and the value parsed begins with.
instead of a leading 0 the period is stripped off. For instance, if you pass.1
instead of0.1
the parsed value becomes1
. This is a problem. This is related to the regex used to parse numbers expecting a sign, then digits, then optionally a period and more digits. However, the optional bit is ignored, the digit is captured and the period is dropped. This could be fixed by adding.
to the character class before the first digit but I'm not sure that is the correct thing to do in all cases. Here's a gist example.The text was updated successfully, but these errors were encountered: