Add no_nonmoose option

[smith153]

When combined with use_moose, doesn't add MooseX::NonMoose to result classes

[karenetheridge]

Why would you want to do that? That would break DBIx::Class functionality.

[smith153]

@karenetheridge Don't know, but was a requirement for an existing project.

[karenetheridge]

Did you try setting use_moose to false?

[jbakerdev]

@karenetheridge @smith153 If the result classes inherit from a result_base_class that is already moosified, then there is no need for MooseX::NonMoose, no?

I moosified the base class in an attempt to silence warnings like this:

Not inlining 'new' for MyApp::Schema::Result::Thing since it is not inheriting the default Moose::Object::new
If you are certain you don't need to inline your constructor, specify inline_constructor => 0 in your call to MyApp::Schema::Result::Thing->meta->make_immutable

I thought I was being clever with this (instead of adding "inline_constructor => 0" to all my result classes) but then I remembered that I shouldn't be modifying the generated classes... and here I am...

Thoughts/suggestions?

[karenetheridge]

f the result classes inherit from a result_base_class that is already moosified, then there is no need for MooseX::NonMoose, no?

Loader could be smarter and examine the base class(es) to see if MooseX::NonMoose is necessary. It looks like the code for that is at about line 2065 of DBIx/Class/Schema/Loader/Base.pm.