Keep proper data type for JSON arrays between conversions. & Fixed conversions for nested JSON arrays and single element Array #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If you convert a JSON array into XML and back to JSON, every data types in the array will be converted to string.
ie.,
{"k": [34, true, "val"]}
-> xml -> json =>{"k": ["34", "true", "val"]}
That's fixed in this commit as is done for JSONObjects.
Second commit does proper conversions for following cases (multi array nesting is now possible):
[['val', 32]]
-> xml -> json =>[['val', 32]]
[32]
-> xml -> json =>[32]