Update TODO with more verbose descriptions of known issues

[catagits/Catalyst-Runtime.git] / TODO

diff --git a/TODO b/TODO
index d6505f8..a2a2093 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,20 +1,28 @@
-Known issues:
+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.
 
-     - Catalyst-Log-Log4perl Deep recursion on subroutine "MockApp::setup" due
-       to Adopt::NEXT not remembering which setup methods were already called
-       and which not, like NEXT does. Log::Log4perl needs to be fixed and the
-       problem should be described in Upgrading.pod. (rafl)
+     Tests in Moose for this are: http://tinyurl.com/c2k85c
 
-     - MX::Emulate::CAF - list assignment (see notes in Upgrading.pod and
-       branch in svn)
+     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::Session::State::Cookie - cookie_name is undefined
-       unless explicitly configured because setup_session isn't executed.
+   - Bugs with actions with Args or CaptureArgs being caled multiple times
+     when called via ->go or ->visit.
 
-Documentation:
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
-   - Catalyst/Upgrading.pod needs brushing up
+   - Certain errors in your application to do with using other code which does
+     not exist can cause an 'Unknown error' issue.
 
-Profiling:
+     Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master
+
+    - Unattached Chained actions can cause issues starting the application.
+      (Is this fixed already by rafl's work??)
+
+Compatibility warnings to add:
+
+   - $self->config should warn as config should only ever be called as a
+     class method.
 
-  - vs 5.70 and optimisation as needed.