The issue isn't when the data is sent to the server since as you said, it would be converted to the appropriate type. The problem comes when I provide this serialization method, users will inevitably use it for other things, like saving to a DataManager store. Now the data hasn't left the client side and the conversion from an int to a string of something like an id or a quantity would cause issues when using the store's filter method as strict comparisons are made.
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
The issue isn't when the data is sent to the server since as you said, it would be converted to the appropriate type. The problem comes when I provide this serialization method, users will inevitably use it for other things, like saving to a DataManager store. Now the data hasn't left the client side and the conversion from an int to a string of something like an id or a quantity would cause issues when using the store's filter method as strict comparisons are made.