[Catalyst-dev] RFC: Catalyst::Plugin::[Warnings|Advice|Critic|...]

Matt S Trout dbix-class at trout.me.uk
Fri Jul 13 16:45:40 GMT 2007


On Fri, Jul 13, 2007 at 02:24:08AM -0500, Jonathan Rockway wrote:
> I'm thinking of a writing module* that will provide runtime advice on the 
> user's Catalyst choices.  For exampe, if they use an old cache plugin, a 
> warning like "use of deprecated plugin Cache::Foobar" will show up.  It can 
> be disabled with a line like "no Catalyst::Warnings qw(deprecated::cache)" or 
> whatever.  (Another thing it should warn about is index/default/etc. instead 
> of the newer :Path :Args(0).)
> 
> Anyway, since mst can't be everywhere, this could be a good way of educating 
> the users that don't keep up with every IRC conversation... without causing 
> them trouble if they don't want it.  Sort of like "use strict" or 
> Perl::Critic.
> 
> Ideas?  Anything specific you want included?

A warnings::register implementation for the core to handle plugin deprecation.

Then a Perl::Critic policy and a helper for generating a test for the rest.

-- 
      Matt S Trout       Need help with your Catalyst or DBIx::Class project?
   Technical Director    Want a managed development or deployment platform?
 Shadowcat Systems Ltd.  Contact mst (at) shadowcatsystems.co.uk for a quote
http://chainsawblues.vox.com/             http://www.shadowcatsystems.co.uk/ 



More information about the Catalyst-dev mailing list