Hello list I got the basics of delegating an Attribute to a Hash stored in another attribute working (http://github.com/xabbu42/MooseX-Attribute-Delegated). But starting to write the module raised a lot of questions:
Should I rather implement this as a new attribute meta class instead of a role, considering I mostly overwrite methods and the module currently probably does not work well together with other extensions changing the way an attribute is saved in the object? I had to copy-paste two methods from Moose::Meta::Method::Constructor with very little changes. Any interest in changing Moose to avoid this? Any ideas how to do this properly? Should I avoid MooseX::Declare if I want to upload this to CPAN? I'd like to add delegation to another Moose object too. As I see it, this should respect all the settings (trigger, isa ...) for the attribute in the delegated object and all settings in the delegating attribute definition. For this to work I'll have to create an instance of the accessor meta class for the attribute delegated to, and use this to create an accessor with implements all settings from both attribute definitions. Is this correct? Any opinions on the correct behavior of the constructor? Greetings xabbu42
