Note C::Test issues kane is gonna fix.

[catagits/Catalyst-Runtime.git] / TODO

diff --git a/TODO b/TODO
index be81bbe..785c03b 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,82 +1,30 @@
-Back-compat investigation:
+Known Bugs:
+   - Moose bug causes issues if you use Moose in your application, but want to
+     use base classes which have not been converted to Moose yet.
 
-  - Get engines tested:
-    - Catalyst-Engine-Zeus
-    - Catalyst-Engine-XMPP2
-    - Catalyst-Engine-HTTPEngine
-    - Catalyst-Engine-HTTP-Prefork
-    - Catalyst-Engine-SCGI
-    - Catalyst-Engine-Wx
+     Tests in Moose for this are: http://tinyurl.com/c2k85c
 
-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)
+     Note: This issue _does not affect_ components which have been converted to
+           Moose, or applications which do not use Moose, and causes a 
+           compile-time error if present.
 
-     - Catalyst-Plugin-Authorization-ACL fails as 
-       Catalyst::Dispatcher::_do_forward does not fix arguments if you throw
-       an exception. Needs a test case (Caelum)
-     
-     - Catalyst::Plugin::Authentication new release.
-     
-     - Catalyst::Action::RenderView
-     - Catalyst::Plugin::DebugCookie
-       - Conflict with each other: $c->config->{debug}->{foo} = 'bar'
-         now breaks, unsure why..
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+     twice when called via ->go or ->visit.
 
-  - Fix memory leaks (I already tried Devel::Leak::Object, but no joy).
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
-Cleanups:
+   - Certain errors in your application to do with using other code which does
+     not exist can cause an 'Unknown error' issue.
 
-  - 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.
+     Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master
 
-  - Eliminate all instances of $instance->{$key}, I think the only thing
-    left is lib/Catalyst/Engine/HTTP.pm: $self->{inputbuf}, which I haven't
-    touched as it is used as an lvalue in a lot of places (t0m)
+   - -restarter.t will fail if you don't have ::StashChange installed, and
+      also quite often at other times.
 
-  - Find whatever in the test suite craps a file called GLOB(0xfoo) onto my 
-    disk and fix it. (Believed to be in the optional TEST_HTTP tests?) (t0m)
+   - Catalyst::Test - bugs with Moosification (Khisanth/kane)
 
-Documentation:
+Compatibility warnings to add:
 
-   - Manual / Tutorial updates
-
-       - extends in components with attributes must be inside a BEGIN block.
-
-       - How to write Moosified Catalyst components.
-
-   - Fix the Roadmap to be less full of lies.
-      
-   - Document all other known failure cases / upgrade issues.
-   
-   - Tidy up / finish off incompatibility warnings etc.
-   
-   - Catalyst/Upgrading.pod
-
-Reported bugs:
-
-   - Issues with TWMC not being loaded when it used to be in 5.70 
-     (Bill Moseley)
-
-Profiling:
-
-  - vs 5.70 and optimisation as needed.
-
-Tests:
-
-  - Moosified test application?
-
-  - Test & document warnings from back-compat methods in Catalyst::Dispatcher
-  
-  - Test & document warnings from plugin method on Catalyst
+   - $self->config should warn as config should only ever be called as a
+     class method.