Known Bugs:
- - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+ - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
twice when called via ->go or ->visit.
Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+Compatibility warnings to add:
- - Certain errors in your application to do with using other code which does
- not exist can cause an 'Unknown error' issue.
+ - $self->config should warn as config should only ever be called as a
+ class method.
- Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master
- < rafl> 21:13:03 < vincent> hah, Class::MOP::Method::Generated->_eval_closure
- < rafl> 21:13:40 < vincent> right, shove a local $@ in there
- < rafl> i can do that and add tests in an hour or two
+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.
- - -restarter.t will fail if you don't have ::StashChange installed, and
- also quite often at other times.
+ 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
- - Catalyst::Test - bugs with Moosification (Khisanth/kane)
+TODO for brach namespace_handling_refactor:
-Compatibility warnings to add:
+- refactor code in
+ * Catalyst::Dispatcher::get_containers # No Idea
+ * Catalyst::Dispatcher::dispatch_type # DONE
- - $self->config should warn as config should only ever be called as a
- class method.
+ * Catalyst::Controller::_parse_ActionClass_attr # DONE
+ * Catalyst::Dispatcher::_load_dispatch_types # DONE
+ * Catalyst::setup_plugins # DONE
+ to use the same namespacing method
+- Ok, so can you add tests for ->config(actions => { foo => { ActionClass => '+Bar' }});