comment on

Looking at the Component configuration section in the Catalyst::Manual::ExtendingCatalyst POD, I see I should be able to access my component's config with $self->config. However, that's empty. Here's my setup, including variations I've tried.

package MyApp::Controller::Foo;
use Data::Dumper;
...
sub auto {
    my( $self, $c ) = @_;

    $c->log->debug( Dumper(__PACKAGE__->config) ); # yields { }
    $c->log->debug( Dumper($self->config) );       # yields { } (metho
+d I think I should work per doc)
    $c->log->debug( Dumper($c->config) );          # the whole config 
+tree, not just this component's

    #$c->config->{'Controller::Foo'}->... # the only way I've figured 
+out to access local config (fixed typo)
}

# MyApp.conf  variation 1
name MyAPP

<Controller Foo>
  foo bar
</Controller>

# MyApp.conf  variation 2  -- no difference in results from 1
name MyApp

<MyApp>
  <Controller Foo>
    foo bar
  </Controller>
</MyApp>
[download]

What am I doing wrong? Or, if I'm looking at the wrong docs, which should I be looking at?

In reply to Catalyst component config by Solo

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 How to display code and escape characters are good places to start.


Think about Loose Coupling
	PerlMonks