X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=TODO;h=2dc0bfdbdd3cef5a623da46229e576ecf1f2b1f9;hp=c8c6b5dbd0268f30a1eda489775cef370dd6b010;hb=3db3a59fefa0cd2859282f7a3e0429a7152637c5;hpb=f78c4567119fbb78dfedbff6d493f0c1216bc4e7 diff --git a/TODO b/TODO index c8c6b5d..2dc0bfd 100644 --- a/TODO +++ b/TODO @@ -1,33 +1,39 @@ -Back-compat investigation: +Pre 0004: - - Get engines tested: - - Catalyst-Engine-HTTP-Prefork + - Certain errors in your application to do with using other code which does + not exist can cause an 'Unknown error' issue. -Known issues: + This is now fixed, by moving back to B::Hooks::EndOfScope, but this (used + to) cause issues with the following modules: - - 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) + - Catalyst-Authentication-Credential-HTTP + + according to comments in r8991. Retest these before shipping anything.. - - CatalystX-CRUD and CatalystX-CRUD-ModelAdapter-DBIC - fail tests against 5.80 (karpet) + - Document method modifiers called on things before setup not working in your app class. - - Waiting on new releases: - - Catalyst::Plugin::Authentication - 0.100092 - - Catalyst::Action::RenderView - 0.08 - - Catalyst::Plugin::DebugCookie - 0.999002 +Known Bugs: -Documentation: + - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled + twice when called via ->go or ->visit. - - Manual / Tutorial updates + Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master - - extends in components with attributes must be inside a BEGIN block. +Compatibility warnings to add: - - How to write Moosified Catalyst components. + - $self->config should warn as config should only ever be called as a + class method. - - Catalyst/Upgrading.pod +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.