[Catalyst] My experience porting to CataMoose

Tomas Doran bobtfish at bobtfish.net
Tue May 12 12:00:18 GMT 2009


Daisuke Maki wrote:
> I've switched an application of mine to CataMoose. Thanks for the hard
> work, it's seems surprisingly stable for such a massive overhaul.

Great, thanks a lot, and thanks for the feedback below!

> I've observed a few glitches / gotchas, they seem like things that
> probably should be documented, but I'd like to share with the list
> before writing them up:

> path_to will return something like "/whatever" instead of
> "/path/to/MyApp/whatever", because home isn't set. to get around it, you
>  would need to force setup_home() to be called, or say
> 
>   package MyApp;
>   use Moose;
>   use Catalyst; # so import() gets called
> 
>   extends 'Catalyst';
> 
>   __PACKAGE__->config(...);
>   __PACKAGE__->setup(...);

Right, that's a documentation bug.. Fixed in r10091.

> 2. Hooking to methods that Plugins use via method modifiers breaks
> method dispatch
> 
> I got bit by this while depending on Catalyst::Plugin::Unicode, and
> trying to hook a custom error handling mechanism at finalize().

<snip explanation>

Hmm, that certainally looks like a bug to me..

Any chance that I could get you to write a test case or two for this issue?

Cheers
t0m



More information about the Catalyst mailing list