-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
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
unmaskAsNumber causing jquery serialize to fail #1288
Comments
@mtsunu , Maybe the unmaskAsNumber should return a numeric parsable string. |
won't it be better to fix the custom radixPoint issue? with the option named "unmaskAsNumber", it would make sense if we expect it to return a number rather than numeric string.. |
The custom radixPoint issue is not really An issue as some backends want it that way to parse it correctly depending the culture settings. You can always extend the current implementation. |
@mtsunu , An example
|
Thanks for the code. I think you're right, I really need to fix my backend culture settings. So, have you decide what to do with unmaskAsNumber? |
@mtsunu , unmaskedadnumber stays as is, also the unmasking. When the culture setting of the backend are fixed, you can use the extension above. But I cannot think a reason why you could not change the culture settings on the backend. |
Okay. Thanks for the help! |
using this options:
calling jquery.serialize will throws exception saying that replace is not a function.
this is because jquery serialize assume that the fields value is string and tries to escape new line characters if any.
https://jsfiddle.net/mtsunu/8Ldejeeq/
the other issue is when setting unmaskAsNumber: false.
notice i'm using comma as radixPoint.
when i input 12.000,24 the serialized value is 12000,24 (i'm guessing the unmask value will be wrong too, haven't tried it though)
what is the correct options for that situation?
The text was updated successfully, but these errors were encountered: