-Pending patches:
- - meta test for MX::Emulate::CAF needed by Catalyst::Plugin::Cache::Curried
-
-Back-compat investigation / known issues:
-
- - Get engines tested:
- - Catalyst-Engine-Zeus
- - Catalyst-Engine-XMPP2
- - Catalyst-Engine-HTTPEngine
- - Catalyst-Engine-HTTP-Prefork
- - Catalyst-Engine-SCGI
- - Catalyst-Engine-Wx
-
- - CatalystX-Imports, Class::MOP doesn't consider anon subs in the symbol
- table as methods, tests + fix, or explanation and documentation?
- (rafl & phaylon)
-
- - Run another round of repository smokes against latest 5.80 trunk, manually
- go through all the things which are broken (t0m).
-
- - 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
- - All fixed by Scope::Upper
-
- - Catalyst-Log-Log4perl Deep recursion on subroutine "MockApp::setup"
- (rafl)
-
- - Catalyst-Plugin-Cache dies due to mk_accessors('meta')
-
- - CatalystX-CRUD fails tests against 5.80 (karpet)
+Known Bugs:
- - Catalyst-Plugin-Authorization-ACL fails as
- Catalyst::Dispatcher::_do_forward does not fix arguments if you throw
- an exception. Needs a test case (Caelum)
-
- - Catalyst::Plugin::Authentication::Store::DBIC relies on
- hooking the setup_finished class data method in a plugin
- (see t/cdi_backcompat_accessor_override.t).
- Is this insane / should we support this?
+ - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+ twice when called via ->go or ->visit.
- - Issues with TWMC not being loaded when it used to be in 5.70
- (Bill Moseley)
+ Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
- - Fix memory leaks (I already tried Devel::Leak::Object, but no joy).
- - In 5.70, you can have a component which doesn't inherit from ::Component,
- and has no new method, and it'll do the right thing for you. We should
- still support that, but warn for/deprecate it so it can go for 5.9X...
- This obviously needs better tests :/
+ - Certain errors in your application to do with using other code which does
+ not exist can cause an 'Unknown error' issue.
-Cleanups:
-
- - 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.
+ This is now fixed, by moving back to B::Hooks::EndOfScope, but this (used
+ to) cause issues with the following modules:
- - 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)
+ - 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..
- - Deprecate runtime plugins with warning.
+ - -restarter.t will fail if you don't have ::StashChange installed, and
+ also quite often at other times.
-Documentation:
- - 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)
- - Manual / Tutorial updates
+Compatibility warnings to add:
- - Fix the Roadmap to be less full of lies.
+ - $self->config should warn as config should only ever be called as a
+ class method.
- - With 5.7 people did extends qw/Moose::Object Catalyst::Component/, now
- Catalyst::Component isa Moose::Object so now isa doesn't linearize
- anymore, docs of what doesn't work and why (rafl)
+Proposed functionality / feature additions:
-Profiling:
+ - 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.
- - vs 5.70 and optimisation as needed.
+ Simple example: Catalyst::Plugin::Log::Colorful should just be a
+ subclass of Catalyst::Log, no ::Plugin:: needed.
-Tests:
+ See also: Catalyst::Plugin::Log::Dispatch and
+ http://github.com/willert/catalyst-plugin-log4perl-simple/tree
- - Moosified test application?
- - Test warning from back-compat methods in Catalyst::Dispatcher