-
Notifications
You must be signed in to change notification settings - Fork 596
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
parseNumbers returns NaN on empty strings. #700
Comments
I am having the same issue. I expected that it should return as an empty string. |
I would expect to have an empty string in this case - will also use my own processor for now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When use the preprocessor parseNumbers, it returns
NaN
for empty string values. Is this expected? I would prefer to leave the value as is (I'm parsing a large object).isNaN('') === false
howeverparseInt('') === NaN
If this is everyone's desired behaviour, please ignore my issue. If this isn't what people are expecting, I can submit a PR. I will see if there are any comments on this issue. In the meantime I will use my own preprocessor.
The text was updated successfully, but these errors were encountered: