CX::Imports, TODO updates, note mst rant, add some docs

diff --git a/Makefile.PL b/Makefile.PL
index de27fe1..03851eb 100644 (file)
--- a/Makefile.PL
+++ b/Makefile.PL
@@ -126,6 +126,7 @@ check_conflicts();
 sub check_conflicts {
     my %conflicts = (
         'Catalyst::Plugin::Authentication' => '0.100092',
+        'CatalystX::Imports' => '0.03',
     );
 
     my $found = 0;

diff --git a/TODO b/TODO
index fa050f1..3f7cb08 100644 (file)
--- a/TODO
+++ b/TODO
@@ -9,14 +9,12 @@ Back-compat investigation:
 
 Known issues:
      - CatalystX-Imports, Class::MOP doesn't consider anon subs in the symbol 
-       table as methods, tests + fix, or explanation and documentation?
-       (rafl & phaylon)
- 
+       table as methods, new version of fixed plugin (rafl), explanation of 
+       the issue in Catalyst::Upgrading (groditi)
+       
      - Catalyst-Log-Log4perl Deep recursion on subroutine "MockApp::setup" 
        (rafl)
-     
-     - Catalyst-Plugin-Cache dies due to mk_accessors('meta')
-     
+
      - CatalystX-CRUD and CatalystX-CRUD-ModelAdapter-DBIC
        fail tests against 5.80 (karpet)
 
@@ -33,6 +31,13 @@ Known issues:
 
 Cleanups:
 
+18:01 <@mst> hmm. I think that warning should show what it found
+18:01 <@mst> and say "you probably called ->model("Sessions") when you meant ->model("DB::Sessions")" or whatever
+18:05 <@mst> unsafe_component_use_ok
+18:05 <@mst> like we did for BindLex
+
+
+
   - Update Test suite to not assume MyApp ISA Controller
     - After that set up attr handlers that will output helpful error messages 
       when you do it as well as how to fix it.
@@ -68,8 +73,6 @@ Profiling:
 Tests:
 
   - Moosified test application?
-
-  - Test & document warnings from back-compat methods in Catalyst::Dispatcher
   
   - Test & document warnings from plugin method on Catalyst
 

diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod
index 4c8a28d..d7a3266 100644 (file)
--- a/lib/Catalyst/Upgrading.pod
+++ b/lib/Catalyst/Upgrading.pod
@@ -79,12 +79,40 @@ in components, instead, you should inherit the new method from Catalyst::Compone
 to perform any construction work necessary for your sub-class.
 
 
-=head Methods in Catalyst::Dispatcher
+=head1 WARNINGS
+
+=head2 Methods in Catalyst::Dispatcher
+
+The following methods in Catalyst::Dispatcher are likely to change 
+significantly in the 5.8X release series, and therefore their use is highly
+deprecated.
+
+=over
+
+=item tree 
+
+=item dispatch_types 
+
+=item registered_dispatch_types 
+
+=item method_action_class  
+
+=item action_hash 
+
+=item container_hash
+
+=back
+
+The first time one of these methods is called, a warning will be emitted:
 
     Class $class is calling the deprecated method Catalyst::Dispatcher::$public_method_name,\n"
     . "this will be removed in Catalyst 5.9X"
 
-FIXME
+You should B<NEVER> be calling any of these methods from application code.
+
+Plugins authors and maintainers whos plugins need to call these methods 
+should email the development list to discuss your use-case, and what a 
+better API should look like.
 
 =head2 Confused multiple inheritence with Catalyst::Component::COMPONENT