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
29 ## The horrible hack for plugin setup - replacing it:
31 * Have a look at the Devel::REPL BEFORE_PLUGIN stuff
32 I wonder if what we need is that combined with plugins-as-roles
36 NOTE - these are notes that t0m thought up after doing back compat for
37 catalyst_component_class, may be inaccurate, wrong or missing things
38 bug mst (at least) to correct before trying more than the first 2
39 steps. Please knock yourself out on the first two however :)
41 - Eliminate actions in MyApp from the main test suite
42 - Uncomment warning in C::C::register_action_methods, add tests it works
43 by mocking out the logging..
44 - Remove MyApp @ISA controller (ask metaclass if it has attributes, and if
45 so you need back compat :/)
46 - Make Catalyst::Context, move the per request stuff in there, handles from
47 main app class to delegate
48 - Make an instance of the app class which is a global variable
49 - Make new instance of the context class, not the app class per-request
50 - Remove the components as class data, move to instance data on the app
51 class (you probably have to do this for _all_ the class data, good luck!)
52 - Make it possible for users to spin up different instances of the app class
53 (with different config etc each)
54 - Profit! (Things like changing the complete app config per vhost, i.e.
55 writing a config loader / app class role which dispatches per vhost to
56 differently configured apps is piss easy)
62 - Moving setup_components etc into the container
64 - This is so that you can just load the container and get models etc from it,
65 without loading Catalyst.
67 - Finish moving setup_component
68 - $component->COMPONENT() is still called by setup_component
69 (should there be a Service::WithCOMPONENT to solve this?)
70 - make it a method, not function
72 - Break $instance->expand_modules() in setup_components and figure
73 out later how to bring it back
75 - Move expand_component_module
77 - Move locate_components
79 - Move contents of setup_components
81 - Finished documentation for ::IOC parts.
83 - Creating service()-like sugar for component
85 - Test cases for extending the container in an application.
86 - Using the sugar added in the previous item
87 - Test when Model::Foo depends_on Model::Bar
89 - Allowing people to change component lifecycles
91 - This is done by being able to use an alternate Service class..
93 I.E. We currently force everything to do Catalyst/IOC/Service/WithAcceptContext.pm, but
94 things without an ACCEPT_CONTEXT could just not bother, and it would be nice to have
95 one that cached the object in request scope (i.e. Catalyst::Component::InstancePerContext)
98 However we need to work out an interface for people to setup / configure this.
102 - Document current methods
103 - + $class->container->get_sub_container('model')->make_single_default;
104 + $class->container->get_sub_container('view')->make_single_default;