yes, yes, the docs needed updating to strictures 2 too

diff --git a/Changes b/Changes
index ffb2c33..90c87b7 100644 (file)
--- a/Changes
+++ b/Changes
@@ -1,5 +1,7 @@
 Revision history for Package-Variant
 
+  - also switch the documentation to strictures 2 (slow clap for mst there)
+
 1.003000 - 2015-07-25
   - switch to strictures 2
   - add make_variant_package_name optional method

diff --git a/lib/Package/Variant.pm b/lib/Package/Variant.pm
index 966d5ad..e6bef72 100644 (file)
--- a/lib/Package/Variant.pm
+++ b/lib/Package/Variant.pm
@@ -139,7 +139,7 @@ Creation of anonymous variants:
 
   # declaring a variable Moo role
   package My::VariableRole::ObjectAttr;
-  use strictures 1;
+  use strictures 2;
   use Package::Variant
     # what modules to 'use'
     importing => ['Moo::Role'],
@@ -160,7 +160,7 @@ Creation of anonymous variants:
 
   # using the role
   package My::Class::WithObjectAttr;
-  use strictures 1;
+  use strictures 2;
   use Moo;
   use My::VariableRole::ObjectAttr;
 
@@ -174,7 +174,7 @@ And the same thing, only with named variants:
 
   # declaring a variable Moo role that can be named
   package My::VariableRole::ObjectAttrNamed;
-  use strictures 1;
+  use strictures 2;
   use Package::Variant importing => ['Moo::Role'],
     subs => [ qw(has around before after with) ];
   use Module::Runtime 'module_notional_filename'; # only if you need protection
@@ -201,7 +201,7 @@ And the same thing, only with named variants:
 
   # using the role
   package My::Class::WithObjectAttr;
-  use strictures 1;
+  use strictures 2;
   use Moo;
   use My::VariableRole::ObjectAttrNamed;