On 28 Feb 2011, at 13:36, will trillich wrote:
Doesn't it depend on which __PACKAGE__ you're in?
Yes, config will be namespaced according to what component you're in.
But for plugins, there isn't a specific component .pm in your
application, so the only choice is the top level MyApp.pm (o
Doesn't it depend on which __PACKAGE__ you're in?
On Mon, Feb 28, 2011 at 7:33 AM, Charlie Garrison wrote:
> Good morning,
>
> On 28/02/11 at 7:10 AM -0600, John M. Dlugosz
> wrote:
>
> > A module documented to put
> >
> >disposition hostless
> >
> >in the myapp.conf file. But, what is
Good morning,
On 28/02/11 at 7:10 AM -0600, John M. Dlugosz wrote:
> A module documented to put
>
>disposition hostless
>
>in the myapp.conf file. But, what is the equivalent __PACKAGE__->config(
>syntax for the MyApp.pm
>file? I can't find documentation on how the names are mapped,
A module documented to put
disposition hostless
in the myapp.conf file. But, what is the equivalent __PACKAGE__->config( syntax for the
MyApp.pm file? I can't find documentation on how the names are mapped, and I've even seen
different syntax in different guides.
What's the correc
Hello!
Does anyone use these plugins together?
Catalyst::Plugin::Unicode::Encoding doesn't decode parameter when it is
prepared by Catalyst::Plugin::Params::Nested (sub prepare_parameters)
I've made a simple patch for Catalyst::Plugin::Unicode::Encoding, so I think
it should work properly.
PS