Detect redispatch exceptions by a class check, not by checking the exception message.

[catagits/Catalyst-Runtime.git] / TODO

diff --git a/TODO b/TODO
index 47a8013..7d34863 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,33 +1,36 @@
-  - Fix t/caf_backcompat_plugin_accessor_override.t
-  
-  - 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)
+Known Bugs:
 
-  - Common engine test failures, look into and get tests into core.
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
+     twice when called via ->go or ->visit.
 
-  - Catalyst-Plugin-Authorization-ACL, Can't locate object method "tree" via package "Catalyst::Dispatcher", fix the plugin as tree was never a public method.
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
-  - Catalyst-Model-Akismet, incorrectly inherits from Catalyst::Component::InstancePerContext, should compose as a role, fix the module.
+Compatibility warnings to add:
 
-  - CatalystX-Imports, Class::MOP doesn't consider anon subs in the symbol table as methods, tests + fix?
+   - $self->config should warn as config should only ever be called as a
+     class method.
 
-  - MooseX::Emulate::Class::Accessor::Fast
-    - Tests for uses of C::A::F from Catalyst repos. - t0m
-    - New release once these are done.
+Proposed functionality / feature additions:
 
-  - 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}
+    - 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.
 
-  - Catalyst-Log-Log4perl - deep recursion in the test suite, investigate
+      Simple example: Catalyst::Plugin::Log::Colorful should just be a
+      subclass of Catalyst::Log, no ::Plugin:: needed.
 
-  - Profiling vs 5.70 and optimisation as needed.
+      See also: Catalyst::Plugin::Log::Dispatch and
+      http://github.com/willert/catalyst-plugin-log4perl-simple/tree
 
-  - http://lists.scsys.co.uk/pipermail/catalyst-dev/2008-November/001546.html
-    - patch to list, andyg to look at?
+TODO for brach namespace_handling_refactor:
 
+- refactor code in
+  * Catalyst::Dispatcher::get_containers           # No Idea
+  * Catalyst::Dispatcher::dispatch_type            # DONE
+
+  * 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' }});