Moose深度强制 - 用户定义类型的ArrayRef

2 回答

• 2

  你使用的一切都应该工作正常 . 例如，考虑这个测试：

  my $customtype = Moose::Util::TypeConstraints::find_type_constraint('CustomType');
  print "'a' validates as customtype? ", ($customtype->check('a') ? 'yes' : 'no'), "\n";
  
  my $arraytype = Moose::Util::TypeConstraints::find_type_constraint('ArrayRefofCustomTypes');
  print "[ 'a' ] validates as array? ", ($arraytype->check([ 'a' ]) ? 'yes' : 'no'), "\n";
  
  {
      package Class;
      use Moose;
      has 'values' => ( is => 'ro', required => 1,
                        isa => 'ArrayRefofCustomTypes',
                        coerce => 1,
                      );
  }
  
  my $obj = Class->new(values => 'a');
  print $obj->dump(2);
  

  这打印：

  'a' validates as customtype? yes
  [ 'a' ] validates as array? yes
  $VAR1 = bless( {
                   'values' => [
                                 'a'
                               ]
                 }, 'Class' );
  

  结论：如果遇到问题，可以使用其他代码 . 你能粘贴一些不能按预期工作的代码吗？

  回复于 2024-05-05T23:06:07+08:00
• 2

  所以是的，强制需要从基类型明确定义到自定义类型，以便输入所有输入的排列 . 将强制和验证代码移出到子例程有助于防止代码重复，但不能完全消除它 . 以下代码按照我的预期运行，并附有TAP计划来证明它 .

  虽然它虽然有效，但我并不完全相信它是处理这类事情的预定方式 . 它正在进行大量从基类型到arrayref自定义类型的显式转换，如果访问器接受多种带强制的类型，我不确定它在更大的上下文中的效果如何 .

  编辑：实际上，此时 coerce 'ArrayRefofCustomTypes' => from 'CustomType' 完全没必要， => from 'Str' 将处理有效和无效输入 .

  { 
    package My::Class;
  
    use strict;
    use warnings;
  
    use Moose;
    use Moose::Util::TypeConstraints;
  
    subtype 'CustomType'
      => as 'Str'
        => where { validate_cust($_) }
      ;
  
    coerce 'CustomType'
      => from 'Str'
        => via { coerce_str_to_cust($_) }
      ;
  
    subtype 'ArrayRefofCustomTypes'
      => as 'ArrayRef[CustomType]'
      ;
  
    coerce 'ArrayRefofCustomTypes'
      => from 'CustomType'
        => via { [ $_ ] }
      => from 'ArrayRef[Str]'
        => via { [ map { coerce_str_to_cust($_) } @$_ ] }
      => from 'Str'
        => via { [ coerce_str_to_cust($_) ] }
      ;
  
    has 'values' => ( is => 'ro', required => 1,
                      isa => 'ArrayRefofCustomTypes', 
                      coerce => 1,
                    );
  
    sub validate_cust {
      my $val = shift;
      if ($val =~ /^\w+$/) {
        return 1;
      }
      return ();
    }
  
    sub coerce_str_to_cust {
      my $val = shift;
      my $coerced = $val;
      $coerced =~ s/\s/_/g;
  
      if (validate_cust($coerced)) {
        return $coerced;
      }
      else {
        return $val;
      }
    }
  }
  
  {
    package main;
  
    use strict;
    use warnings;
    use Test::More tests => 12;
    use Test::Exception;
  
    new_ok( 'My::Class' => [ values => [ 'valid' ] ]);
    new_ok( 'My::Class' => [ values => [ qw/valid valid still_valid/ ] ]);
    new_ok( 'My::Class' => [ values => 'valid' ]);
    new_ok( 'My::Class' => [ values => [ 'invalid and needs some coercion' ] ]);
    new_ok( 'My::Class' => [ values => 'invalid and needs some coercion' ]);
    new_ok( 'My::Class' => [ values => [ 'valid', 'valid', 'invalid and needs some coercion' ] ]);
    throws_ok { my $obj =  My::Class->new( values => [ q/can't be coerced cause it has &^%#$*&^%#$s in it/ ] ); } qr/Attribute \(values\) does not pass the type constraint because: Validation failed/, 'throws exception on uncoercible input';
  
    my $uncoercible = q/can't be coerced cause it has &^%#$*&^%#$s in it/;
    cmp_ok( My::Class::coerce_str_to_cust('invalid and needs some coercion'), 'eq', 'invalid_and_needs_some_coercion', 'properly coerces strings');
    cmp_ok( My::Class::coerce_str_to_cust($uncoercible), 'eq', $uncoercible , 'returns uncoercible strings unmodified');
    ok( My::Class::validate_cust('valid'), 'valid string validates');
    ok( My::Class::validate_cust(My::Class::coerce_str_to_cust('invalid and needs some coercion')), 'coerced string validates');
    ok( !My::Class::validate_cust('invalid and needs some coercion'), "invalid string doesn't validate");
  }
  

  回复于 2024-05-05T23:06:07+08:00