<div dir="ltr">Thanks for all the work on this guys. Things seem to be working well with one small issue and one big-ish one. The small one is that mixing load_components() and Moo's extends() doesn't work. Easy enough to fix and makes sense.<div><br></div><div>The larger issue is that now, with latest Moo, the method resolution order changes from 'c3' to 'dfs' which breaks a bunch of things for me. For example DBIx::Class::InflateColumn::DateTime, under c3, comes before DBIx::Class::Row, but with dfs it comes after and column inflation stops functioning.</div><div><br></div><div>Doing this in my result classes seems to fix it:</div><div><br></div><div>use Moo;</div><div>use mro 'c3';</div><div><br></div><div>I should be complete with my DBIC->Moo work within the next day or two and I'm hoping based on early success that all will be well.</div><div><br></div><div>Aran</div></div><br><div class="gmail_quote">On Sat, Dec 20, 2014 at 6:29 AM Peter Rabbitson <<a href="mailto:rabbit%2Bdbic@rabbit.us">rabbit+dbic@rabbit.us</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On 10/02/2014 04:21 AM, Aran Deltac wrote:<br>
> I've been converting a lot of @work's custom components, result, result<br>
> set, schema, and storage classes (yes, we even have custom storage<br>
> classes) to Moo roles and classes.<br>
><br>
<br>
Hi Aran,<br>
<br>
Just wanted to followup whether the current stable DBIC and Moo versions<br>
resolve your issues.<br>
<br>
Thanks!<br>
<br>
</blockquote></div>