X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=7c6b268ee49264a1da3fe19056209bc1c3c8f710;hb=f46240732bc1e71e45211a471ffc00e571e026b3;hp=a2a2093611e55ab5f4063883c264fbee21d4d55e;hpb=f825519b38a6f50083f0507b198e34239ac674e5;p=catagits%2FCatalyst-Runtime.git

diff --git a/TODO b/TODO
index a2a2093..7c6b268 100644
--- a/TODO
+++ b/TODO
@@ -1,28 +1,41 @@
 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.
 
-     Tests in Moose for this are: http://tinyurl.com/c2k85c
-
-     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.
-
-   - Bugs with actions with Args or CaptureArgs being caled multiple times
-     when called via ->go or ->visit.
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+     twice when called via ->go or ->visit.
 
      Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
+
    - Certain errors in your application to do with using other code which does
      not exist can cause an 'Unknown error' issue.
 
      Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master
+     < rafl> 21:13:03 < vincent> hah, Class::MOP::Method::Generated->_eval_closure
+     < rafl> 21:13:40 < vincent> right, shove a local $@ in there
+     < rafl> i can do that and add tests in an hour or two
+
+
+   - -restarter.t will fail if you don't have ::StashChange installed, and
+      also quite often at other times.
+
 
-    - Unattached Chained actions can cause issues starting the application.
-      (Is this fixed already by rafl's work??)
+   - Catalyst::Test - bugs with Moosification (Khisanth/kane)
 
 Compatibility warnings to add:
 
    - $self->config should warn as config should only ever be called as a
      class method.
 
+Proposed functionality / feature additions:
+
+    - Log setup needs to be less lame, so Catalyst::Plugin::Log::* can die
+      in a fire. Having $c->log_class would be a good start. kane volunteered
+      to do some of this.
+
+      Simple example: Catalyst::Plugin::Log::Colorful should just be a
+      subclass of Catalyst::Log, no ::Plugin:: needed.
+
+      See also: Catalyst::Plugin::Log::Dispatch and
+      http://github.com/willert/catalyst-plugin-log4perl-simple/tree
+
+