Re^2: Framework for making Moose-compatible object from json

Replies are listed 'Best First'.
Re^3: Framework for making Moose-compatible object from json by nataraj (Sexton) on Sep 05, 2022 at 13:58 UTC
I'm curious about why MooseX::Storage (mentioned previously in this thread) wasn't up to the task? Because I consider that case "object inside object inside object" is common case, and should be solved without any Moose code, just by mentioning "This is a subobject of following type". Like this: `j_obj "icon" =>(class => "WebService::DreamWidth::Icon", is =>'ro');` [download] I even thinking about removing "is =>'ro'", making it default. In simple case developer should just list attributes and child objects. This is not case for MooseX::Storage	[reply] [d/l]

Replies are listed 'Best First'.

Re^3: Framework for making Moose-compatible object from json
by nataraj (Sexton) on Sep 05, 2022 at 13:58 UTC

I'm curious about why MooseX::Storage (mentioned previously in this thread) wasn't up to the task?

Because I consider that case "object inside object inside object" is common case, and should be solved without any Moose code, just by mentioning "This is a subobject of following type". Like this:

j_obj "icon" =>(class => "WebService::DreamWidth::Icon", is =>'ro');
[download]

I even thinking about removing "is =>'ro'", making it default. In simple case developer should just list attributes and child objects. This is not case for MooseX::Storage

[reply]
[d/l]