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
33 * Test all the options work on all of the scripts
34 * Fix a sane / nicer way to do custom engines.
38 * Capture arguments that the plack engine component was run with somewhere,
39 to more easily support custom args from scripts (e.g. Gitalist's
41 * throw away the restarter and allow using the restarters Plack provides
42 * remove per-request state from the engine instance
43 * be smarter about how we use PSGI - not every response needs to be delayed
45 * lighttpd, iis6, and nginx path-info fixers as proper middlewars as part of Plack
47 ## The horrible hack for plugin setup - replacing it:
49 * Have a look at the Devel::REPL BEFORE_PLUGIN stuff
50 I wonder if what we need is that combined with plugins-as-roles
54 NOTE - these are notes that t0m thought up after doing back compat for
55 catalyst_component_class, may be inaccurate, wrong or missing things
56 bug mst (at least) to correct before trying more than the first 2
57 steps. Please knock yourself out on the first two however :)
59 - Eliminate actions in MyApp from the main test suite
60 - Uncomment warning in C::C::register_action_methods, add tests it works
61 by mocking out the logging..
62 - Remove MyApp @ISA controller (ask metaclass if it has attributes, and if
63 so you need back compat :/)
64 - Make Catalyst::Context, move the per request stuff in there, handles from
65 main app class to delegate
66 - Make an instance of the app class which is a global variable
67 - Make new instance of the context class, not the app class per-request
68 - Remove the components as class data, move to instance data on the app
69 class (you probably have to do this for _all_ the class data, good luck!)
70 - Make it possible for users to spin up different instances of the app class
71 (with different config etc each)
72 - Profit! (Things like changing the complete app config per vhost, i.e.
73 writing a config loader / app class role which dispatches per vhost to
74 differently configured apps is piss easy)