Catalyst::Dispatcher::_do_forward does not fix arguments if you throw
an exception. Needs a test case (Caelum)
- - Catalyst::Plugin::Authentication new release.
-
- - Catalyst::Action::RenderView
- - Catalyst::Plugin::DebugCookie
- - Conflict with each other: $c->config->{debug}->{foo} = 'bar'
- now breaks, unsure why..
+ - Waiting on new releases:
+ - Catalyst::Plugin::Authentication - 0.100092
+ - Catalyst::Action::RenderView - 0.08
+ - Catalyst::Plugin::DebugCookie' - 0.999002
Cleanups:
-18:01 <@mst> hmm. I think that warning should show what it found
-18:01 <@mst> and say "you probably called ->model("Sessions") when you meant ->model("DB::Sessions")" or whatever
-18:05 <@mst> unsafe_component_use_ok
-18:05 <@mst> like we did for BindLex
-
-
-
- - Update Test suite to not assume MyApp ISA Controller
- - After that set up attr handlers that will output helpful error messages
- when you do it as well as how to fix it.
-
- - Eliminate all instances of $instance->{$key}, I think the only thing
- left is lib/Catalyst/Engine/HTTP.pm: $self->{inputbuf}, which I haven't
- touched as it is used as an lvalue in a lot of places (t0m)
-
- 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)
- How to write Moosified Catalyst components.
- - Fix the Roadmap to be less full of lies.
-
- Catalyst/Upgrading.pod
Reported bugs:
Tests:
- Moosified test application?
-
- - Test & document warnings from plugin method on Catalyst