3 - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
4 twice when called via ->go or ->visit.
6 Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
8 # Compatibility warnings to add:
10 - $self->config should warn as config should only ever be called as a
13 # Proposed functionality / feature additions:
15 ## Log setup needs to be less lame
17 So Catalyst::Plugin::Log::* can die
18 in a fire. Having $c->log_class would be a good start. kane volunteered
21 Simple example: Catalyst::Plugin::Log::Colorful should just be a
22 subclass of Catalyst::Log, no ::Plugin:: needed.
24 See also: Catalyst::Plugin::Log::Dispatch and
25 http://github.com/willert/catalyst-plugin-log4perl-simple/tree
31 ### To do at release time
33 - Release psgi branch of Catalyst-Devel
34 - Release new Task::Catalyst
38 * Fix nginx middlewares so that they are generic, or can somehow
39 be used by people with their own .psgi files
41 * I've noticed a small difference with Catalyst::Test. The latest stable
42 version include two headers, 'host' and 'https'. They are missing from
43 this version - Pedro Melo on list
44 ^^ Cannot replicate this? Mailed back to ask for tests..
48 * Test/WWW/Mechanize/Catalyst.pm stable throws a deprecation alert when
49 using Catalyst::Test changes introduced by Cataplack. Suggested fix is
50 in the repo: http://dev.catalystframework.org/svnweb/Catalyst/revision?rev=14059
52 * Capture arguments that the plack engine component was run with somewhere,
53 to more easily support custom args from scripts (e.g. Gitalist's
55 * throw away the restarter and allow using the restarters Plack provides
56 * remove per-request state from the engine instance
57 * be smarter about how we use PSGI - not every response needs to be delayed
60 ## The horrible hack for plugin setup - replacing it:
62 * Have a look at the Devel::REPL BEFORE_PLUGIN stuff
63 I wonder if what we need is that combined with plugins-as-roles
67 NOTE - these are notes that t0m thought up after doing back compat for
68 catalyst_component_class, may be inaccurate, wrong or missing things
69 bug mst (at least) to correct before trying more than the first 2
70 steps. Please knock yourself out on the first two however :)
72 - Eliminate actions in MyApp from the main test suite
73 - Uncomment warning in C::C::register_action_methods, add tests it works
74 by mocking out the logging..
75 - Remove MyApp @ISA controller (ask metaclass if it has attributes, and if
76 so you need back compat :/)
77 - Make Catalyst::Context, move the per request stuff in there, handles from
78 main app class to delegate
79 - Make an instance of the app class which is a global variable
80 - Make new instance of the context class, not the app class per-request
81 - Remove the components as class data, move to instance data on the app
82 class (you probably have to do this for _all_ the class data, good luck!)
83 - Make it possible for users to spin up different instances of the app class
84 (with different config etc each)
85 - Profit! (Things like changing the complete app config per vhost, i.e.
86 writing a config loader / app class role which dispatches per vhost to
87 differently configured apps is piss easy)