X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=TODO;h=03a4674b01969f54487455fa85d8f263b39c226f;hp=cdf6f34575a7c89ddce7f50ec0082ab61c1bcb00;hb=ef41ea15458d2d2beddee792deea598249df2852;hpb=0dcb835492485b0544de9d340ca8fbb37a43e14e diff --git a/TODO b/TODO index cdf6f34..03a4674 100644 --- a/TODO +++ b/TODO @@ -1,82 +1,87 @@ -Pending patches: - - meta test for MX::Emulate::CAF needed by Catalyst::Plugin::Cache::Curried - - - Bump MX::Emulate::CAF for fixes to t/double_apply.t - -Back-compat investigation / known issues: - - - Plugins with new methods. - - Moose 'not inlining new method' warnings need to be fixed. - - Warning in Moose could also be more helpful.. - - Why does the current test not fail / warn? - - Generally unhappy with the on_end_of_scope immutable approach, - try removing new method from plugins (and emitting warning). - - - Common engine test failures, look into and get tests into core. - - - CatalystX-Imports, Class::MOP doesn't consider anon subs in the symbol - table as methods, tests + fix, or explanation and documentation? - (rafl & phaylon) - - - Run another round of repository smokes against latest 5.80 trunk, manually - go through all the things which are broken (t0m). - - - Catalyst::Plugin::Authorization::ACL - - Catalyst::Plugin::Server - - Catalyst::Plugin::HTML::Widget - - Should hopefully be fixed now.. - - - Catalyst-Plugin-Cache dies due to mk_accessors('meta') - - - Catalyst-Action-REST appears to have real issues, investigate - - - Catalyst-Model-Search ditto - - - CatalystX-CRUD ditto - - - Catalyst-Engine-Apache - Deep recursion on subroutine - "Catalyst::Action::execute", investigate once all other tests pass - - - Issues with TWMC not being loaded when it used to be in 5.70 - (Bill Moseley) - - - Fix memory leaks (I already tried Devel::Leak::Object, but no joy). - - - In 5.70, you can have a component which doesn't inherit from ::Component, - and has no new method, and it'll do the right thing for you. We just - ignore that, we should still support that, but warn for/deprecate it so - it can go for 5.9X... - This all obviously needs better tests :/ - -Cleanups: - - - Update Test suite to not assume MyApp ISA Controller - - After that set up attr handlers that will output helpful error messages - when you do it as well as how to fix it. - - - Eliminate all instances of $instance->{$key}, I think the only thing - left is lib/Catalyst/Engine/HTTP.pm: $self->{inputbuf}, which I haven't - touched as it is used as an lvalue in a lot of places (t0m) - - - Find whatever in the test suite craps a file called GLOB(0xfoo) onto my - disk and fix it. (Believed to be in the optional TEST_HTTP tests?) (t0m) - -Documentation: - - - extends in components must be inside a BEGIN block. - - - How to write Moosified Catalyst components. - - - Manual / Tutorial updates - - - Fix the Roadmap to be less full of lies. - -Profiling: - - - vs 5.70 and optimisation as needed. - -Tests: - - - Moosified test application? - - - Test warning from back-compat methods in Catalyst::Dispatcher +# Known Bugs: + + - Bug ->go or ->visit causes actions which have Args or CaptureArgs called + twice when called via ->go or ->visit. + + Test app: http://github.com/bobtfish/catalyst-app-bug-go_chain/tree/master + +# Compatibility warnings to add: + + - $self->config should warn as config should only ever be called as a + class method (TESTS). + +# 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 + +# REFACTORING + +## PSGI + +### Blockers + + * lighttpd + * iis6 + * Add some tests for Catalyst::Test::local_request + * Docs + * Test all the options work on all of the scripts + * Test (and fix if needed) Engine::Stomp and ::Wx + * Document how to use your own .psgi (and how you need to do ReverseProxy yourself if you do) + * Document migration for setting engine in setup + * Document migration for setting engine in $ENV + * Document what to do if you're a Prefork person + * Test Catalyst::Engine::PSGI still works? + +### Nice to have + + * Do we need to do something else about middleware than let the user provide a .psgi? + What about the reverse proxy middleware + * Do we generate a .psgi by default? + * throw out Catalyst::Test's remote_request in favour of + Plack::Test::ExternalServer + * make sure we're running under a server that support psgi.streaming - maybe + just load the BufferedWrite middleware, although that might break things + relying on ->write doing an unbuffered write + * throw away the restarter and allow using the restarters Plack provides + * remove per-request state from the engine instance + * be smarter about how we use PSGI - not every response needs to be delayed + and streaming + +## The horrible hack for plugin setup - replacing it: + + * Have a look at the Devel::REPL BEFORE_PLUGIN stuff + I wonder if what we need is that combined with plugins-as-roles + +## App / ctx split: + + NOTE - these are notes that t0m thought up after doing back compat for + catalyst_component_class, may be inaccurate, wrong or missing things + bug mst (at least) to correct before trying more than the first 2 + steps. Please knock yourself out on the first two however :) + + - Eliminate actions in MyApp from the main test suite + - Uncomment warning in C::C::register_action_methods, add tests it works + by mocking out the logging.. + - Remove MyApp @ISA controller (ask metaclass if it has attributes, and if + so you need back compat :/) + - Make Catalyst::Context, move the per request stuff in there, handles from + main app class to delegate + - Make an instance of the app class which is a global variable + - Make new instance of the context class, not the app class per-request + - Remove the components as class data, move to instance data on the app + class (you probably have to do this for _all_ the class data, good luck!) + - Make it possible for users to spin up different instances of the app class + (with different config etc each) + - Profit! (Things like changing the complete app config per vhost, i.e. + writing a config loader / app class role which dispatches per vhost to + differently configured apps is piss easy)