doc updates and changelog for less undef tolerance

fix NEXT

diff --git a/Changes b/Changes
index 2807380..f24cd65 100644 (file)
--- 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 (file)
--- 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<MooseX::UndefTolerant::Attribute> for details.
+
+There will be no change in behaviour to any attribute with a type constraint
+that accepts undef values (for example C<Maybe> 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<undef>.
+
 =head1 MOTIVATION
 
 I often found myself in this quandry: