-Back-compat investigation:
+Known Bugs:
- - Get engines tested:
- - Catalyst-Engine-HTTP-Prefork
+ - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
+ 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)
+Compatibility warnings to add:
- - CatalystX-CRUD and CatalystX-CRUD-ModelAdapter-DBIC
- fail tests against 5.80 (karpet)
+ - $self->config should warn as config should only ever be called as a
+ class method.
- - 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
+Proposed functionality / feature additions:
-Cleanups:
+ - 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.
- - 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)
+ Simple example: Catalyst::Plugin::Log::Colorful should just be a
+ subclass of Catalyst::Log, no ::Plugin:: needed.
-Documentation:
+ See also: Catalyst::Plugin::Log::Dispatch and
+ http://github.com/willert/catalyst-plugin-log4perl-simple/tree
- - Manual / Tutorial updates
+ Fixes to component interfaces to deal with anon classes:
- - extends in components with attributes must be inside a BEGIN block.
+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
- - How to write Moosified Catalyst components.
+ The horrible hack for plugin setup - replacing it:
- - Catalyst/Upgrading.pod
+15:30 <@mst> t0m: have a look at the Devel::REPL BEFORE_PLUGIN stuff
+15:30 <@mst> I wonder if what we need is that combined with plugins-as-roles
-Profiling:
- - vs 5.70 and optimisation as needed.