How about marking the validation routine rather than the parameters, so you would have:

constraints => {
     image_name => [
     {
         constraint_method => 'file_format',
     },
     {
         constraint_method => 'file_max_bytes',
         params => [\100],
     },
     {
         constraint_method => 'image_max_dimensions',
         params => [\200,\200],
     },
 
     ],

[download]

you could either add a method to D::FV that allows you to find out the name of the field whose contraints are currently being checked (which would involve rewriting the validation subroutines), or make it a convention that the first two args are always the D::FV object and the name of the field being checked.

So:

     foo => { constraint_method => 'bar', params => \@args },

[download]

would translate to either:

     foo => { constraint => 'bar', params => [$dfv, @args]] },

[download]

or

     foo => { constraint => 'bar', params => [$dfv, 'foo', @args] },

[download]

(where $dfv is the D::FV object in question)

I'd prefer the former since you would then have a direct mapping to the Perl method calling convention:

bar($dfv, @args);
$dfv->bar(@args);

[download]

In reply to Re: RFC: Data::FormValidator params interface enhancement by adrianh
in thread RFC: Data::FormValidator params interface enhancement by markjugg

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.