fallback => 1;
use Scalar::Util qw(blessed refaddr);
+use Sub::Name qw(subname);
use base qw(Class::MOP::Object);
-our $VERSION = '0.71_01';
+our $VERSION = '0.93';
$VERSION = eval $VERSION;
our $AUTHORITY = 'cpan:STEVAN';
Moose->throw_error("Cannot coerce without a type coercion");
}
+ return $_[0] if $self->check($_[0]);
+
return $coercion->coerce(@_);
}
}
}
+sub assert_valid {
+ my ($self, $value) = @_;
+
+ my $error = $self->validate($value);
+ return 1 if ! defined $error;
+
+ require Moose;
+ Moose->throw_error($error);
+}
+
sub get_message {
my ($self, $value) = @_;
if (my $msg = $self->message) {
return $msg->($value);
}
else {
- $value = (defined $value ? overload::StrVal($value) : 'undef');
+ $value = (defined $value ? overload::StrVal($value) : 'undef');
return "Validation failed for '" . $self->name . "' failed with value $value";
- }
+ }
}
## type predicates ...
if ( $check == $null_constraint ) {
return $optimized_parent;
} else {
- return Class::MOP::subname($self->name, sub {
+ return subname($self->name, sub {
return undef unless $optimized_parent->($_[0]);
my (@args) = @_;
local $_ = $args[0];
# general case, check all the constraints, from the first parent to ourselves
my @checks = @parents;
push @checks, $check if $check != $null_constraint;
- return Class::MOP::subname($self->name => sub {
+ return subname($self->name => sub {
my (@args) = @_;
local $_ = $args[0];
foreach my $check (@checks) {
return $check if $check == $null_constraint; # Item, Any
- return Class::MOP::subname($self->name => sub {
+ return subname($self->name => sub {
my (@args) = @_;
local $_ = $args[0];
$check->(@args);
return $class->new(%opts, parent => $self);
}
-## this should get deprecated actually ...
-
-sub union { Carp::croak "DEPRECATED" }
-
1;
__END__
=head1 DESCRIPTION
-For the most part, the only time you will ever encounter an
-instance of this class is if you are doing some serious deep
-introspection. This API should not be considered final, but
-it is B<highly unlikely> that this will matter to a regular
-Moose user.
+This class represents a single type constraint. Moose's built-in type
+constraints, as well as constraints you define, are all store in a
+L<Moose::Meta::TypeConstraint::Registry> object as objects of this
+class.
-If you wish to use features at this depth, please come to the
-#moose IRC channel on irc.perl.org and we can talk :)
+=head1 INHERITANCE
+
+C<Moose::Meta::TypeConstraint> is a subclass of L<Class::MOP::Object>.
=head1 METHODS
=over 4
-=item B<meta>
+=item B<< Moose::Meta::TypeConstraint->new(%options) >>
-=item B<new>
+This creates a new type constraint based on the provided C<%options>:
-=item B<equals ($type_name_or_object)>
+=over 8
-This checks the current type against the supplied type (only).
-Returns false if the two types are not equal. It also returns false if
-you provide the type as a name, and the type name isn't found in the
-type registry.
+=item * name
-=item B<is_a_type_of ($type_name_or_object)>
+The constraint name. If a name is not provided, it will be set to
+"__ANON__".
-This checks the current type against the supplied type, or if the
-current type is a sub-type of the type name or object supplied. It
-also returns false if you provide the type as a name, and the type
-name isn't found in the type registry.
+=item * parent
-=item B<is_subtype_of ($type_name_or_object)>
+A C<Moose::Meta::TypeConstraint> object which is the parent type for
+the type being created. This is optional.
-This checks the current type is a sub-type of the type name or object
-supplied. It also returns false if you provide the type as a name, and
-the type name isn't found in the type registry.
+=item * constraint
-=item B<compile_type_constraint>
+This is the subroutine reference that implements the actual constraint
+check. This defaults to a subroutine which always returns true.
-=item B<coerce ($value)>
+=item * message
-This will apply the type-coercion if applicable.
+A subroutine reference which is used to generate an error message when
+the constraint fails. This is optional.
-=item B<check ($value)>
+=item * coercion
-This method will return a true (C<1>) if the C<$value> passes the
-constraint, and false (C<0>) otherwise.
+A L<Moose::Meta::TypeCoercion> object representing the coercions to
+the type. This is optional.
-=item B<validate ($value)>
+=item * optimized
-This method is similar to C<check>, but it deals with the error
-message. If the C<$value> passes the constraint, C<undef> will be
-returned. If the C<$value> does B<not> pass the constraint, then
-the C<message> will be used to construct a custom error message.
+This is a variant of the C<constraint> parameter that is somehow
+optimized. Typically, this means incorporating both the type's
+constraint and all of its parents' constraints into a single
+subroutine reference.
-=item B<name>
+=back
-The name of the type in the global type registry.
+=item B<< $constraint->equals($type_name_or_object) >>
-=item B<parent>
+Returns true if the supplied name or type object is the same as the
+current type.
-This type's parent type.
+=item B<< $constraint->is_subtype_of($type_name_or_object) >>
-=item B<has_parent>
+Returns true if the supplied name or type object is a parent of the
+current type.
-Returns true if this type has a parent type.
+=item B<< $constraint->is_a_type_of($type_name_or_object) >>
-=item B<parents>
+Returns true if the given type is the same as the current type, or is
+a parent of the current type. This is a shortcut for checking
+C<equals> and C<is_subtype_of>.
-Synonym for C<parent>.
+=item B<< $constraint->coerce($value) >>
-=item B<constraint>
+This will attempt to coerce the value to the type. If the type does
+have any defined coercions this will throw an error.
-Returns this type's constraint. This is the value of C<where> provided
-when defining a type.
+=item B<< $constraint->check($value) >>
-=item B<has_message>
+Returns true if the given value passes the constraint for the type.
-Returns true if this type has a message.
+=item B<< $constraint->validate($value) >>
-=item B<message>
+This is similar to C<check>. However, if the type I<is valid> then the
+method returns an explicit C<undef>. If the type is not valid, we call
+C<< $self->get_message($value) >> internally to generate an error
+message.
-Returns this type's message.
+=item B<< $constraint->assert_valid($value) >>
-=item B<get_message ($value)>
+Like C<check> and C<validate>, this method checks whether C<$value> is
+valid under the constraint. If it is, it will return true. If it is not,
+an exception will be thrown with the results of
+C<< $self->get_message($value) >>.
-Generate message for $value.
+=item B<< $constraint->name >>
-=item B<has_coercion>
+Returns the type's name, as provided to the constructor.
-Returns true if this type has a coercion.
+=item B<< $constraint->parent >>
-=item B<coercion>
+Returns the type's parent, as provided to the constructor, if any.
-Returns this type's L<Moose::Meta::TypeCoercion> if one exists.
+=item B<< $constraint->has_parent >>
-=item B<hand_optimized_type_constraint>
+Returns true if the type has a parent type.
-=item B<has_hand_optimized_type_constraint>
+=item B<< $constraint->parents >>
-=item B<create_child_type>
+A synonym for C<parent>. This is useful for polymorphism with types
+that can have more than one parent.
-=back
+=item B<< $constraint->constraint >>
-=head2 DEPRECATED METHOD
+Returns the type's constraint, as provided to the constructor.
-=over 4
+=item B<< $constraint->get_message($value) >>
+
+This generates a method for the given value. If the type does not have
+an explicit message, we generate a default message.
+
+=item B<< $constraint->has_message >>
+
+Returns true if the type has a message.
+
+=item B<< $constraint->message >>
+
+Returns the type's message as a subroutine reference.
+
+=item B<< $constraint->coercion >>
+
+Returns the type's L<Moose::Meta::TypeCoercion> object, if one
+exists.
+
+=item B<< $constraint->has_coercion >>
+
+Returns true if the type has a coercion.
+
+=item B<< $constraint->hand_optimized_type_constraint >>
+
+Returns the type's hand optimized constraint, as provided to the
+constructor via the C<optimized> option.
+
+=item B<< $constraint->has_hand_optimized_type_constraint >>
+
+Returns true if the type has an optimized constraint.
+
+=item B<< $constraint->create_child_type(%options) >>
-=item B<union>
+This returns a new type constraint of the same class using the
+provided C<%options>. The C<parent> option will be the current type.
-This was just bad idea on my part,.. use the L<Moose::Meta::TypeConstraint::Union>
-itself instead.
+This method exists so that subclasses of this class can override this
+behavior and change how child types are created.
=back
projects / gitmo/Moose.git / blobdiff