in reply to
Re: Moose role with requirement consuming another role
in thread Moose role with requirement consuming another role
My second example (with gazpacho), was really just meant to show that I understand the importance of the with/has order when a class consumes a role. Perhaps I over-emphasized it.
The real problem is not with class<-role(requirement), but, similar to my first example, class<-role<-role<-role(requirements). Or to go into yet more detail, I have about 30 app classes which consume one of two specialized App roles, these both consume a generic App role, which consumes three further roles, MooseX::Getopt, MooseX::SimpleConfig plus our own app-logger role.
I can easily drop the requirement in the app-logger role and everything works fine. I'm just curious if there is a better solution.