Add test controller with its own meta method, still works

[catagits/Catalyst-Runtime.git] / TODO

diff --git a/TODO b/TODO
index bec19e9..605d275 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,25 +1,43 @@
-Known issues:
+Known Bugs:
 
-Documentation:
+   - Bug ->go or ->visit causes actions which have Args or CaptureArgs caled
+     twice when called via ->go or ->visit.
 
-   - Catalyst/Upgrading.pod needs brushing up
+     Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
 
-   - Warning when you pass $c->model("MyApp::Model::Foo") is the generic
-     warning for regex fall back. Should be more specific about what you
-     screwed up, and the docs for $c->model should be more explicit about
-     what is expected. This probably also applies to view/controller.
 
-   - Run more smokes
+   - Certain errors in your application to do with using other code which does
+     not exist can cause an 'Unknown error' issue.
 
-   - Test/document ->Class::MOP::Object::meta call in ::ClassData
+     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
 
-   - Change dispatcher and upgrade docs appropriately (no new method needed)
 
-   - Using anything ::[CMV]:: should warn (once, on boot).
+   - -restarter.t will fail if you don't have ::StashChange installed, and
+      also quite often at other times.
 
-   - TestApp should not use NEXT. There should be a TestAppNEXTCompat
-     which does but is standalone..
 
-Profiling:
+   - Catalyst::Test - bugs with Moosification (Khisanth/kane)
+
+   - Attribute called 'actions' in controllers - needs to be renamed to _actions.
+
+Compatibility warnings to add:
+
+   - $self->config should warn as config should only ever be called as a
+     class method.
+
+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.
+
+      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
+
 
-  - vs 5.70 and optimisation as needed on perl 5.8 (5.10 is already faster!).