Write that down

[catagits/Catalyst-Runtime.git] / TODO

diff --git a/TODO b/TODO
index 73b33b6..141b67b 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,58 +1,49 @@
-Back-compat investigation:
-
-  - Get engines tested:
-    - Catalyst-Engine-Zeus
-    - Catalyst-Engine-XMPP2
-    - Catalyst-Engine-HTTPEngine
-    - Catalyst-Engine-HTTP-Prefork
-    - Catalyst-Engine-Wx
-
-Known issues:
-
-     - 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)
-
-     - CatalystX-CRUD and CatalystX-CRUD-ModelAdapter-DBIC
-       fail tests against 5.80 (karpet)
-
-     - 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..
-
-Cleanups:
-
-  - 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)
-
-Documentation:
-
-   - Manual / Tutorial updates
-
-       - extends in components with attributes must be inside a BEGIN block.
-
-       - How to write Moosified Catalyst components.
-
-   - 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?
-
+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