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
I'm upping the issue because this causes compatibility troubles between applications using the v9 library and the ones migrated to the v10.
Date fields are still working but the DateTime fields have changed format, causing an application using the v10 library to read null instead of the expected value when parsing JSON received or saved on storage based on the previous version of the library.
We found in your documentation that you mention this compatibility issue but with no concrete documentation on how to handle it.
What method do you recommend to handle this? Can we expect the JSON parser in v10 to be able to parse old datetime format (or a PR for this to be accepted, even if it will be "deprecated" and possibly removed in a v11) ?
Do you recommend a configuration to pass in the library to tweak the JSON parser and have custom code to handle datetimes of the previous format?
Must we convert all stored MX in JSON format back to XML with v9 based version of the application then parse & convert them again to JSON with the v10 based version?
Hello,
Between v9 and V10 versions, the dates format have changed.
I don’t see anything in the v10 to be compatible with v9 date format.
Is there any custom adapter (or possibility to add one) to able to deserialize the « old » date format (or any other solution ) ?
Many thanks in advance.
Regards
The text was updated successfully, but these errors were encountered: