use Scalar::Util 'blessed';
use Moose::Util::TypeConstraints ();
-our $VERSION = '0.60';
+our $VERSION = '0.93';
$VERSION = eval $VERSION;
our $AUTHORITY = 'cpan:STEVAN';
my $self = shift;
my $class = $self->class;
$self->hand_optimized_type_constraint(
- sub {
- blessed( $_[0] ) && $_[0]->isa($class)
+ sub {
+ blessed( $_[0] ) && $_[0]->isa($class)
}
);
}
# if anybody thinks this problematic please discuss on IRC.
# a possible fix is to add by attr indexing to the type registry to find types of a certain property
# regardless of their name
- Moose::Util::TypeConstraints::find_type_constraint($_)
- ||
+ Moose::Util::TypeConstraints::find_type_constraint($_)
+ ||
__PACKAGE__->new( class => $_, name => "__ANON__" )
- } $self->class->meta->superclasses,
+ } Class::MOP::class_of($self->class)->superclasses,
);
}
}
my $type = Moose::Util::TypeConstraints::find_type_constraint($type_or_name_or_class);
-
+
return unless defined $type;
if ( $type->isa(__PACKAGE__) ) {
}
}
+# This is a bit counter-intuitive, but a child type of a Class type
+# constraint is not itself a Class type constraint (it has no class
+# attribute). This whole create_child_type thing needs some changing
+# though, probably making MMC->new a factory or something.
+sub create_child_type {
+ my ($self, @args) = @_;
+ return Moose::Meta::TypeConstraint->new(@args, parent => $self);
+}
+
+sub get_message {
+ my $self = shift;
+ my ($value) = @_;
+
+ if ($self->has_message) {
+ return $self->SUPER::get_message(@_);
+ }
+
+ $value = (defined $value ? overload::StrVal($value) : 'undef');
+ return "Validation failed for '" . $self->name . "' failed with value $value (not isa " . $self->class . ")";
+}
+
1;
__END__
Moose::Meta::TypeConstraint::Class - Class/TypeConstraint parallel hierarchy
+=head1 DESCRIPTION
+
+This class represents type constraints for a class.
+
+=head1 INHERITANCE
+
+C<Moose::Meta::TypeConstraint::Class> is a subclass of
+L<Moose::Meta::TypeConstraint>.
+
=head1 METHODS
=over 4
-=item B<new>
+=item B<< Moose::Meta::TypeConstraint::Class->new(%options) >>
+
+This creates a new class type constraint based on the given
+C<%options>.
+
+It takes the same options as its parent, with two exceptions. First,
+it requires an additional option, C<class>, which is name of the
+constraint's class. Second, it automatically sets the parent to the
+C<Object> type.
+
+The constructor also overrides the hand optimized type constraint with
+one it creates internally.
+
+=item B<< $constraint->class >>
+
+Returns the class name associated with the constraint.
+
+=item B<< $constraint->parents >>
-=item B<class>
+Returns all the type's parent types, corresponding to its parent
+classes.
-=item B<hand_optimized_type_constraint>
+=item B<< $constraint->is_subtype_of($type_name_or_object) >>
-=item B<has_hand_optimized_type_constraint>
+If the given type is also a class type, then this checks that the
+type's class is a subclass of the other type's class.
-=item B<equals>
+Otherwise it falls back to the implementation in
+L<Moose::Meta::TypeConstraint>.
-=item B<is_a_type_of>
+=item B<< $constraint->create_child_type(%options) >>
-=item B<is_subtype_of>
+This returns a new L<Moose::Meta::TypeConstraint> object with the type
+as its parent.
-=item B<parents>
+Note that it does I<not> return a
+C<Moose::Meta::TypeConstraint::Class> object!
-Return all the parent types, corresponding to the parent classes.
+=item B<< $constraint->get_message($value) >>
-=item B<meta>
+This is the same as L<Moose::Meta::TypeConstraint/get_message> except
+that it explicitly says C<isa> was checked. This is to help users deal
+with accidentally autovivified type constraints.
=back
=head1 BUGS
-All complex software has bugs lurking in it, and this module is no
-exception. If you find a bug please either email me, or add the bug
-to cpan-RT.
+See L<Moose/BUGS> for details on reporting bugs.
=head1 AUTHOR
=head1 COPYRIGHT AND LICENSE
-Copyright 2006-2008 by Infinity Interactive, Inc.
+Copyright 2006-2010 by Infinity Interactive, Inc.
L<http://www.iinteractive.com>