X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=141b67b4628d1b676f7c4364b9da5e37c6d209db;hb=139b894c380e870c0b25ea20749cc6f689d93fa0;hp=a049144a6b3ebf785c1665661dfdea4b6fbb6b3c;hpb=72737d6061fbe37d21502337ea5d21e8ac1f2915;p=catagits%2FCatalyst-Runtime.git

diff --git a/TODO b/TODO
index a049144..141b67b 100644
--- a/TODO
+++ b/TODO
@@ -1,33 +1,49 @@
-  - Get rid of Class::Inspector. Class::MOP has 'is_class_loaded' and
-    'load_class', which is all we use Class::Inspector for.
-
-  - Make Catalyst::Test use Sub::Exporter or maybe Moose::Exporter.
-
-  - Add Class::Accessor compats
-    * Catalyst::Request
-    * Catalyst::Response
-    * Catalyst::Dispatcher
-    * Catalyst::Request::Upload
-    * Catalyst::Action
-    * Catalyst::ActionChain
-    * Catalyst::ActionContainer
-
-  - Make classes immutable at setup() time
-
-
-  - GRODITI's list:
-    * Update Test suite to not assume MyApp ISA Controller
-      - After that I'll set up attr handlers that will output helpful
-        error messages when you do it as well as how to fix it.
-    * comments marked /Moose TODO/i in the code
-    * Fix the CDI compat hack so we can start moving to immutable
-    * Profile before and after immutable.
-    * Now would be a good time to lay ground for the App / Ctx split
-    * Howto mantain branch in sync with the latest checkins ?
-    * Eliminate all instances of $instance->{$key}
-    * MooseX::Emulate::CAF seems to be working like a charm :)
-    * General code cleanups can't hurt
-    * How do we move from NEXT to C3 ? I have never used either of them
-      - What does the lineraized mro look like when we are using moose 
-        method modifiers?
-        - Does they all get clumped together or what? Is it a non-issue?
+Known Bugs:
+
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
+     twice when called via ->go or ->visit.
+
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+
+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
+
+  Fixes to component interfaces to deal with anon classes:
+
+22:16 <@mst> t0m: explain what breaks
+22:16 <@mst> I'm not 100% sure we have the same problem in mind
+22:17 <@t0m> well, various shit in Catalyst utils to resolve app from MyApp::Controller::Foo breaks
+22:17 <@mst> Caelum: http://scsys.co.uk:8001/31240
+22:17 <@mst> t0m: the trick would be to not need to do that
+22:17 <@mst> t0m: $self->_application should be fine
+22:18 <@t0m> $action->class can't be fed back into $c->component() 
+22:18 <@t0m> which breaks ::REST
+22:18 <@mst> right
+22:18 <@mst> we need to
+22:19 <@mst> (a) add an ->_component_name or similar method to controllers
+22:19 <@mst> (b) pass action objects either that or the controller
+22:20 <@t0m> do you have a controller calling $action->dispatch? Course you must, the action lives in a controller..
+22:21 <@mst> and that doesn't matter anyway
+22:21 <@mst> dispatch has $c
+22:21 <@mst> it needs to do
+22:21 <@mst> $c->component($self->_component_name)
+22:21 <@mst> and that _component_name needs to come from the controller at register_actions time
+22:22 <@t0m> confound: Oi, please to be releasing my Action::REST fixes, I'm about to do more..
+22:22 <@t0m> mst: right, gotcha
+22:22 <@mst> note that needs to happen in core
+22:22 <@mst> then actions can use that instead of $self->class
+22:22 <@mst> and shit will work