Docs
[catagits/Catalyst-Runtime.git] / TODO
CommitLineData
77d892df 1# Known Bugs:
cdb34619 2
3 - Bug ->go or ->visit causes actions which have Args or CaptureArgs called
4 twice when called via ->go or ->visit.
5
6 Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master
7
77d892df 8# Compatibility warnings to add:
9
10 - $self->config should warn as config should only ever be called as a
5d94e8f9 11 class method (TESTS).
77d892df 12
13# Proposed functionality / feature additions:
14
15## Log setup needs to be less lame
16
17So Catalyst::Plugin::Log::* can die
18in a fire. Having $c->log_class would be a good start. kane volunteered
19to do some of this.
20
21Simple example: Catalyst::Plugin::Log::Colorful should just be a
22subclass of Catalyst::Log, no ::Plugin:: needed.
23
24See also: Catalyst::Plugin::Log::Dispatch and
25http://github.com/willert/catalyst-plugin-log4perl-simple/tree
26
27# REFACTORING
28
29aba7b9 29## PSGI
30
102e063c 31### Blockers
32
fa38321d 33 * Ensure all PSGI related FIXMEs in docs or code are in this list
f05b654b 34 * Fix nginx middlewares so that they are generic, or can somehow
eddb80f7 35 be used by people with their own .psgi files
8110f44e 36 * Fix a sane / nicer way to do custom engines.
102e063c 37
50a65bb3 38#### Script survey
39
40##### myapp_web_fastcgi.pl
41
42Looks to me like we are mapping --deamon to --detach but I think the modern Plack FCGI handler prefers --deamonize
43
44Although --pidfile is supported --pid seems to be preferred, and if we are bothering to map, why not map for the future?
45
102e063c 46### Nice to have
47
f05b654b 48 * <@rafl> i've been thinking of maybe providing
49 MyApp->apply_default_middlewares($psgi_app)
8110f44e 50 * Capture arguments that the plack engine component was run with somewhere,
51 to more easily support custom args from scripts (e.g. Gitalist's
52 --git_dir)
29aba7b9 53 * throw away the restarter and allow using the restarters Plack provides
54 * remove per-request state from the engine instance
55 * be smarter about how we use PSGI - not every response needs to be delayed
56 and streaming
57
77d892df 58## The horrible hack for plugin setup - replacing it:
59
60 * Have a look at the Devel::REPL BEFORE_PLUGIN stuff
61 I wonder if what we need is that combined with plugins-as-roles
62
63## App / ctx split:
64
65 NOTE - these are notes that t0m thought up after doing back compat for
5d94e8f9 66 catalyst_component_class, may be inaccurate, wrong or missing things
77d892df 67 bug mst (at least) to correct before trying more than the first 2
68 steps. Please knock yourself out on the first two however :)
69
70 - Eliminate actions in MyApp from the main test suite
71 - Uncomment warning in C::C::register_action_methods, add tests it works
72 by mocking out the logging..
73 - Remove MyApp @ISA controller (ask metaclass if it has attributes, and if
74 so you need back compat :/)
75 - Make Catalyst::Context, move the per request stuff in there, handles from
76 main app class to delegate
77 - Make an instance of the app class which is a global variable
78 - Make new instance of the context class, not the app class per-request
79 - Remove the components as class data, move to instance data on the app
80 class (you probably have to do this for _all_ the class data, good luck!)
81 - Make it possible for users to spin up different instances of the app class
82 (with different config etc each)
83 - Profit! (Things like changing the complete app config per vhost, i.e.
84 writing a config loader / app class role which dispatches per vhost to
85 differently configured apps is piss easy)