Databases
StackOverflow2013
Postsdbo
POWhat is the most efficient way to override an attribute in lots of my Moose based sub classes?
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWhat is the most efficient way to override an attribute in lots of my Moose based sub classes?
    primarykey
    data
    text
    <p>I am using <a href="http://search.cpan.org/perldoc/HTML::FormHandler" rel="nofollow noreferrer">HTML::FormHandler</a>. To use it one is supposed to subclass from it and then you can override some attributes such as <code>field_name_space</code> or <code>attribute_name_space</code>. </p> <p>However, I now have lots of forms all extending <code>HTML::FormHandler</code> or its DBIC based variant <a href="http://search.cpan.org/perldoc/HTML::FormHandler::Model::DBIC" rel="nofollow noreferrer">HTML::FormHandler::Model::DBIC</a> and therefore have these overidden attributes repeated many times.</p> <p>I tried to put them in a role but get an error that <code>+attr</code> notation is not supported in Roles. Fair enough.</p> <p>What is the best way of eliminating this repetition? I thought perhaps subclassing but then I would have to do it twice for <code>HTML::FormHandler</code> and <code>HTML::FormHandler::Model::DBIC</code>, plus I believe general thought was that subclassing is generally better achieved with Roles instead.</p> <p><strong>Update:</strong> I thought it would be a good idea to give an example. This is what I am currently doing - and it involves code repetition. As you can see one form uses a different parent class so I cannot create one parent class to put the attribute overrides in. I would have to create two - and that also adds redundancy. </p> <pre><code>package MyApp::Form::Foo; # this form does not interface with DBIC extends 'HTML::Formhandler'; has '+html_prefix' =&gt; (default =&gt; 1); has '+field_traits' =&gt; (default =&gt; sub { ['MyApp::Form::Trait::Field'] }); has '+field_name_space' =&gt; (default =&gt; 'MyApp::Form::Field'); has '+widget_name_space' =&gt; (default =&gt; sub { ['MyApp::Form::Widget'] }); has '+widget_wrapper' =&gt; (default =&gt; 'None'); ... package MyApp::Form::Bar; # this form uses a DBIC object extends 'HTML::Formhandler::Model::DBIC'; has '+html_prefix' =&gt; (default =&gt; 1); has '+field_traits' =&gt; (default =&gt; sub { ['MyApp::Form::Trait::Field'] }); has '+field_name_space' =&gt; (default =&gt; 'MyApp::Form::Field'); has '+widget_name_space' =&gt; (default =&gt; sub { ['MyApp::Form::Widget'] }); has '+widget_wrapper' =&gt; (default =&gt; 'None'); ... package MyApp::Form::Baz; # this form also uses a DBIC object extends 'HTML::Formhandler::Model::DBIC'; has '+html_prefix' =&gt; (default =&gt; 1); has '+field_traits' =&gt; (default =&gt; sub { ['MyApp::Form::Trait::Field'] }); has '+field_name_space' =&gt; (default =&gt; 'MyApp::Form::Field'); has '+widget_name_space' =&gt; (default =&gt; sub { ['MyApp::Form::Widget'] }); has '+widget_wrapper' =&gt; (default =&gt; 'None'); ... </code></pre>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. UScubabit
    1. UScubabit
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    2. PO
      singulars
      1. PTAnswer
    3. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POWhat is the most efficient way to override an attribute in lots of my Moose based sub classes?
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POWhat is the most efficient way to override an attribute in lots of my Moose based sub classes?
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POWhat is the most efficient way to override an attribute in lots of my Moose based sub classes?
      1. USqodeninja
      1. VTFavorite
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload