X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=cedd11d7e78eafef75240bf65e2ea05d8ffcb3b5;hb=a6eb852aea33990d3c00ae09f057c666670a67ca;hp=94ba5c1b5ac75a5e9239f4f64a06b314616bd522;hpb=0bc4c3ab80525051843dd85cb18f5d3762b0414c;p=catagits%2FCatalyst-Runtime.git diff --git a/TODO b/TODO index 94ba5c1..cedd11d 100644 --- a/TODO +++ b/TODO @@ -1,26 +1,29 @@ +Pre 0004: + + - Document method modifiers called on things before setup not working in your app class. + +Known Bugs: + + - 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 + +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 + - - 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: - * 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?