From: Karen Etheridge Date: Fri, 18 Mar 2011 16:43:46 +0000 (-0700) Subject: doc updates and changelog for less undef tolerance X-Git-Tag: 0.10~2 X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=commitdiff_plain;h=793ea91a4a503ad9a00b71eef74952e0719a37e4;p=gitmo%2FMooseX-UndefTolerant.git doc updates and changelog for less undef tolerance fix NEXT --- diff --git a/Changes b/Changes index 2807380..f24cd65 100644 --- a/Changes +++ b/Changes @@ -1,5 +1,10 @@ Revision history for MooseX-UndefTolerant +{{$NEXT}} + * No longer apply UndefTolerant behaviour to attributes with a type + constraint that handles undef (or those with no type constraint at all). + (Karen Etheridge) + 0.09 March 2, 2011 * Add missing test prereq on Test::Fatal. (Dave Rolsky) diff --git a/lib/MooseX/UndefTolerant.pm b/lib/MooseX/UndefTolerant.pm index feda0ea..12f4cec 100644 --- a/lib/MooseX/UndefTolerant.pm +++ b/lib/MooseX/UndefTolerant.pm @@ -67,6 +67,14 @@ attributes tolerant of undef. If you specify the value of undef to any of the attributes they will not be initialized, effectively behaving as if you had not provided a value at all. +You can also apply the 'UndefTolerant' trait to individual attributes. See See +L for details. + +There will be no change in behaviour to any attribute with a type constraint +that accepts undef values (for example C types), as it is presumed that +since the type is already "undef tolerant", there is no need to avoid +initializing the attribute value with C. + =head1 MOTIVATION I often found myself in this quandry: