[catagits/Catalyst-Runtime.git] / TODO

# 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

##  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)
Commit	Line	Data
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
	17	So Catalyst::Plugin::Log::* can die
	18	in a fire. Having $c->log_class would be a good start. kane volunteered
	19	to do some of this.
	20
	21	Simple example: Catalyst::Plugin::Log::Colorful should just be a
	22	subclass of Catalyst::Log, no ::Plugin:: needed.
	23
	24	See also: Catalyst::Plugin::Log::Dispatch and
	25	http://github.com/willert/catalyst-plugin-log4perl-simple/tree
	26
	27	# REFACTORING
	28
	29	## The horrible hack for plugin setup - replacing it:
	30
	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
	33
	34	## App / ctx split:
	35
	36	NOTE - these are notes that t0m thought up after doing back compat for
5d94e8f9	37	catalyst_component_class, may be inaccurate, wrong or missing things
77d892df	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 :)
	40
	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)