Custom type objects aren't marshalled consistently with builtin type objects. about json-marshal HOT 5 CLOSED

Hi,
thanks, to be honest this was a scenario I hadn't even considered. I'll take a look this afternoon.

from json-marshal.

I also noticed that it probably wants to be fixed for Associative and Positional type objects as well. Thanks again.

from json-marshal.

Array[MyClass] is indeed what brought me here, but I figured it makes the most sense to start with the most basic bits. I wonder whether fixing this will also fix that case for free, since if I recall, Array[Int] works with undefined members. But I'm not sure I tested all the cases.

from json-marshal.

Hi,
that should fix; however in order to for everything to properly round-trip then a small change to JSON::Unmarshal will be required to deal with the unmarshal('null', Array) and unmarshal("null", Hash) cases correctly (it already works with the a custom class like unmarshal("null", class C { }).

from json-marshal.

@jonathanstowe Thanks a lot! I'll file that bug with JSON::Unmarshal, and also that it seems not to work with untyped null members. (They're unmarshalled as Mu instead of Any.)

from json-marshal.