Bug #87508 for MooseX-Constructor-AllErrors: conflicts with MooseX::RemoteHelper

https://github.com/xenoterracide/MooseX-RemoteHelper/blob/master/t/message-part.t https://github.com/xenoterracide/MooseX-RemoteHelper/blob/master/lib/MooseY/RemoteHelper/MessagePart.pm when I enabled Constructor-All Errors, class Test0 operations pass, but Test1 fails (seemingly that the attribute renaming (MX::Aliases like) that remote_helper does is negated ), disabled all pass. If I directly add use MooseX::Constructor::AllErrors to Test1, it passes. expected behavior is for MX::RemoteHelper to continue working, and MXC::AllErrors to be applied to all classes. my only thought on why this might be is that, having glanced at the code, MXC::AllErrors doesn't support all of Moose 2's MX changes, RemoteHelper only supported 2, but I seem to remember there being "Object" pm for Moose 1 and a bunch of others (that doesn't exist in AllErrors) for Moose 2. -- Caleb Cushing http://xenoterracide.com Calendar: https://www.google.com/calendar/embed?src=xenoterracide%40gmail.com&ctz=America/Chicago