-Back-compat investigation:
+Known Bugs:
- - Get engines tested:
- - Catalyst-Engine-HTTP-Prefork
+ - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+ twice when called via ->go or ->visit.
-Known issues:
+ Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
- - 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)
+ - Certain errors in your application to do with using other code which does
+ not exist can cause an 'Unknown error' issue.
- - Catalyst-Plugin-Authorization-ACL fails as
- Catalyst::Dispatcher::_do_forward does not fix arguments if you throw
- an exception. Needs a test case (Caelum)
-
- - Waiting on new releases:
- - Catalyst::Plugin::Authentication - 0.100092
- - Catalyst::Action::RenderView - 0.08
- - Catalyst::Plugin::DebugCookie - 0.999002
+ This is now fixed, by moving back to B::Hooks::EndOfScope, but this (used
+ to) cause issues with the following modules:
-Cleanups:
+ - Catalyst-Plugin-Session-State-Cookie
+ - Catalyst-Plugin-Session-Store-FastMmap
+ - Catalyst-Plugin-Session-PerUser
+ - Catalyst-Plugin-Session-Store-File
+ - Catalyst-Authentication-Credential-HTTP
+ - Catalyst-Plugin-SmartURI
- - 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)
+ according to comments in r8991. Retest these before shipping anything..
-Documentation:
+ - -restarter.t will fail if you don't have ::StashChange installed, and
+ also quite often at other times.
- - Manual / Tutorial updates
- - extends in components with attributes must be inside a BEGIN block.
+ - Attribute called 'actions' in controllers - needs to be renamed to _actions.
- - How to write Moosified Catalyst components.
+ - before finalize causes you to miserably fail to call plugins finalize
+ method (dmaki)
- - Catalyst/Upgrading.pod
+Compatibility warnings to add:
-Profiling:
+ - $self->config should warn as config should only ever be called as a
+ class method.
- - vs 5.70 and optimisation as needed.
+Proposed functionality / feature additions:
-Tests:
+ - 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
- - Moosified test application?