Known Bugs:
- - Moose bug causes issues if you use Moose in your application, but want to
- use base classes which have not been converted to Moose yet.
- Tests in Moose for this are: http://tinyurl.com/c2k85c
+ - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
+ twice when called via ->go or ->visit.
- Note: This issue _does not affect_ components which have been converted to
- Moose, or applications which do not use Moose, and causes a
- compile-time error if present.
+ Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
- - Bugs with actions with Args or CaptureArgs being caled multiple times
- when called via ->go or ->visit.
+Compatibility warnings to add:
- Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
+ - $self->config should warn as config should only ever be called as a
+ class method.
- - Certain errors in your application to do with using other code which does
- not exist can cause an 'Unknown error' issue.
+Proposed functionality / feature additions:
- Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master
+ - 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.
- - Unattached Chained actions can cause issues starting the application.
- (Is this fixed already by rafl's work??)
+ Simple example: Catalyst::Plugin::Log::Colorful should just be a
+ subclass of Catalyst::Log, no ::Plugin:: needed.
-Compatibility warnings to add:
+ See also: Catalyst::Plugin::Log::Dispatch and
+ http://github.com/willert/catalyst-plugin-log4perl-simple/tree
- - $self->config should warn as config should only ever be called as a
- class method.
projects / catagits/Catalyst-Runtime.git / blobdiff