Magnolia.K

The following code is the relevant part. https://github.com/json4s/json4s/blob/859cede89ff8b82da55464d21c9f88d06e9e7adb/core/src/main/scala/org/json4s/Extraction.scala#L191-L195 Wouldn't it be more appropriate to write a serializer because the proposed modification would cause incompatibilities in other code that uses Json4s?

Json4s uses runtime reflection to parse classes, which allows us to minimize the code for serialization. On the other hand, to be familiar with Json4s itself and the internal implementations...

In the current Json 4s, they are organized into an array only when all the same element names are lined up. As in the example above, if only some elements...

@tribbloid Is this issue still valid? Map seems to be supported.

Can anyone please provide a minimal set of code that reproduces this at this time? I can't reproduce this issue.

@spongebobZ First, there is no convention for converting XML to JSON This is why various libraries have their own implementations. The implementation of Json4s is based on the following rules....

Note that the second pattern can be converted to the following using Perl's XML::Simple. ```json {"a":{"b":"1"}} ``` Also, the following pattern conversions are different from the Json4s-XML conversions. ### xml...

@dwalend Although it became a very slow response, there is no plan to support SortedMap at this time, there is no other way but to prepare a CustomSerializer for SortedMap.

@mfulgo The removeField method performs recursive processing, so all objects that do not correspond to ("C", _) are deleted.

I don't have time to fix it now, but I'd really like to.