X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=TODO;h=785c03b23dfafba365c65cc91dfed62e08bf28eb;hb=29f9fdb69c65b20dd03b395a4e2aad199bc1ce54;hp=318654aa5eb1908cfed77830b156dc8968be9e95;hpb=dae2b0faaf2982bde81606ea0392c13fd9309cb1;p=catagits%2FCatalyst-Runtime.git diff --git a/TODO b/TODO index 318654a..785c03b 100644 --- a/TODO +++ b/TODO @@ -1,69 +1,30 @@ -TBD pre 5.8000_04 dev release: +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. - - Go through everything which used to use CAF, and ensure that it now uses MX::E::CAF + tests, - extending t/caf_backcompat.t and replacing t/custom_request.t (t0m) + Tests in Moose for this are: http://tinyurl.com/c2k85c - - Simple test for NEXT compat in core (t0m). + 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. - - Looks like stash is not available during prepare_path when running under - Catalyst::Test.. Run MojoMojo's t/01app.t and it will explode with - "Can't use an undefined value as a HASH reference" - test case for core - + fix maybe (marcus) + - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled + twice when called via ->go or ->visit. ---- + Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master - - Make the skipped test at the bottom of t/aggregate/live_engine_request_uri.t - pass / not be skipped. (From what C::P::SmartURI used to do) + - Certain errors in your application to do with using other code which does + not exist can cause an 'Unknown error' issue. - This can be fixed by the following patch: + Test app: http://github.com/bobtfish/catalyst-app-bug-unknown-error/tree/master -Index: lib/Catalyst/Request.pm -=================================================================== ---- lib/Catalyst/Request.pm (revision 8709) -+++ lib/Catalyst/Request.pm (working copy) -@@ -96,7 +96,7 @@ - lazy => 1, - default => sub { - my $self = shift; -- return $self->path if $self->uri; -+ return $self->{path} if $self->{uri}; - }, - ); + - -restarter.t will fail if you don't have ::StashChange installed, and + also quite often at other times. - But I'd like a 2nd opinion from someone who knows core better than me - about if that is the correct fix.. (t0m / Caelum) + - Catalyst::Test - bugs with Moosification (Khisanth/kane) - - Common engine test failures, look into and get tests into core. +Compatibility warnings to add: - - Catalyst-Plugin-Authorization-ACL, Can't locate object method "tree" via package "Catalyst::Dispatcher", fix the plugin as tree was never a public method. - - - Catalyst-Model-Akismet, incorrectly inherits from Catalyst::Component::InstancePerContext, should compose as a role, fix the module. - - - CatalystX-Imports, Class::MOP doesn't consider anon subs in the symbol table as methods, tests + fix? - - - Catalyst::Plugin::Cache::Curried - - Catalyst::Controller::WrapCGI - - Both import 'meta' into controller package - mst thinks this can be fixed?. - but @marcus> and the generated accessors even call $_[0]->meta, so I don't think we can remove it. - . Add a test for this in core. - . Fix core to use CMOP to look up metaclass, rather than ->meta method, and - namespace::clean the meta method out, fix generated accessors to do the same? - - - MooseX::Emulate::Class::Accessor::Fast - - Tests for uses of C::A::F from Catalyst repos. - t0m - - New release once these are done. - - - 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. (done already?) - - - Comments marked /Moose TODO/i in the code - - - Eliminate all instances of $instance->{$key} - - - Catalyst-Log-Log4perl - deep recursion in the test suite, investigate - - - Profiling vs 5.70 and optimisation as needed. - - - http://lists.scsys.co.uk/pipermail/catalyst-dev/2008-November/001546.html - - patch to list, andyg to look at? + - $self->config should warn as config should only ever be called as a + class method.