X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=fd103b1274f7bd8c5173f515a86b3414445ecb6b;hb=647a251fa90fc925b194a8e1223a9d6706262ee5;hp=8715e8db8864fbafaf4f9f7373ac347d5ccf1445;hpb=44f879d3cd1c4a2152a0d95ee4ead9ed4814a55d;p=catagits%2FCatalyst-Runtime.git

diff --git a/TODO b/TODO
index 8715e8d..fd103b1 100644
--- a/TODO
+++ b/TODO
@@ -5,19 +5,12 @@ Back-compat investigation:
     - Catalyst-Engine-XMPP2
     - Catalyst-Engine-HTTPEngine
     - Catalyst-Engine-HTTP-Prefork
-    - Catalyst-Engine-SCGI
     - Catalyst-Engine-Wx
 
 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)
- 
      - 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)
 
@@ -31,26 +24,15 @@ Known issues:
      - Catalyst::Plugin::DebugCookie
        - Conflict with each other: $c->config->{debug}->{foo} = 'bar'
          now breaks, unsure why..
-         
-      - Catalyst::Component::ACCEPT_CONTEXT - Having a COMPONENT method
-        after Catalyst::Component::COMPONENT used to work, and will still
-        delegate (and warn), but then NEXT::COMPONENT will not dtrt if you
-        re-dispatch again (NEXT would seemingly go back to the start?)..
-        See Reaction test suite for example of this happening.
-        FIXME - Also don't think this correctly delegates - $c appears 
-        missing.
-
-  - Fix memory leaks (I already tried Devel::Leak::Object, but no joy).
-
-  -  In 5.70, you can have a component which doesn't inherit from ::Component, 
-     and has no new method, and it'll do the right thing for you. We should 
-     still support that, but warn for/deprecate it so it can go for 5.9X...
-     This obviously needs better tests :/
 
 Cleanups:
 
-  - Allow turning deprecated warnings off with use Catalyst 
-    qw/-NoDeprecationWarnings/
+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 
@@ -65,21 +47,15 @@ Cleanups:
 
 Documentation:
 
-   - extends in components with attributes must be inside a BEGIN block.
+   - Manual / Tutorial updates
 
-   - How to write Moosified Catalyst components.
+       - extends in components with attributes must be inside a BEGIN block.
 
-   - Manual / Tutorial updates
+       - How to write Moosified Catalyst components.
 
    - Fix the Roadmap to be less full of lies.
 
-   -  With 5.7 people did extends qw/Moose::Object Catalyst::Component/, now 
-      Catalyst::Component isa Moose::Object so now isa doesn't linearize 
-      anymore, docs of what doesn't work and why (rafl)
-      
-   - Document all other known failure cases / upgrade issues.
-   
-   - Tidy up / finish off incompatibility warnings etc.
+   - Catalyst/Upgrading.pod
 
 Reported bugs:
 
@@ -93,8 +69,6 @@ Profiling:
 Tests:
 
   - Moosified test application?
-
-  - Test warning from back-compat methods in Catalyst::Dispatcher
   
-  - Test warnings from plugin method on Catalyst
+  - Test & document warnings from plugin method on Catalyst