Again, the fine folks on #catalyst have helped my understanding. First off, what I'm trying to do is pretty wrong.
Instead of using $c->config, you just need to know that config values are rolled into the object hash during instantiation. So, $self->{foo} contains the config value. (Namespace collisions seem possible, and are on my list to investigate).
# in myapp.conf
<Controller Foo>
foo bar
</Controller>
# to use config in Foo.pm
package MyApp::Controller::Foo;
...
sub baz {
my ($self, $c) = @_;
# data from config
$c->log->debug( $self->{foo} ); # logs 'bar'
}
Optionally, with Moose accessors as suggested in the POD. (And I don't know much about Moose, so this may not be the best way.)
package MyApp::Controller::Foo;
...
# foo accessor
has 'foo' => (
is => 'ro',
isa => 'Str',
);
sub baz {
my ($self, $c) = @_;
# data from config
$c->log->debug( $self->{foo} ); # logs 'bar'
}
Update: and as I git cloned to suggest updates, I see updates to that section of the POD are already in the pipeline!
Update 2: The POD I should have read the whole time was Catalyst in the Cascading configuration section.
-
Are you posting in the right place? Check out Where do I post X? to know for sure.
-
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big>
<blockquote> <br /> <dd>
<dl> <dt> <em> <font>
<h1> <h2> <h3> <h4>
<h5> <h6> <hr /> <i>
<li> <nbsp> <ol> <p>
<small> <strike> <strong>
<sub> <sup> <table>
<td> <th> <tr> <tt>
<u> <ul>
-
Snippets of code should be wrapped in
<code> tags not
<pre> tags. In fact, <pre>
tags should generally be avoided. If they must
be used, extreme care should be
taken to ensure that their contents do not
have long lines (<70 chars), in order to prevent
horizontal scrolling (and possible janitor
intervention).
-
Want more info? How to link or
or How to display code and escape characters
are good places to start.