X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=605d275d933be20444da8cb845e1cd0c4304243f;hb=ecd79a0112fccbcec1c7e8d82a8f8bcb605e9b37;hp=d6505f827b323b9dcbd557d158190f9f6a6406e0;hpb=8ada55c45d8683f362c8863cfe16cfd4f3d1ffd2;p=catagits%2FCatalyst-Runtime.git diff --git a/TODO b/TODO index d6505f8..605d275 100644 --- a/TODO +++ b/TODO @@ -1,20 +1,43 @@ -Known issues: +Known Bugs: - - 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) + - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled + twice when called via ->go or ->visit. - - MX::Emulate::CAF - list assignment (see notes in Upgrading.pod and - branch in svn) + Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master - - Catalyst::Plugin::Session::State::Cookie - cookie_name is undefined - unless explicitly configured because setup_session isn't executed. -Documentation: + - Certain errors in your application to do with using other code which does + not exist can cause an 'Unknown error' issue. - - Catalyst/Upgrading.pod needs brushing up + 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. + + + - Catalyst::Test - bugs with Moosification (Khisanth/kane) + + - Attribute called 'actions' in controllers - needs to be renamed to _actions. + +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 -Profiling: - - vs 5.70 and optimisation as needed.