Bug #57373 for CatalystX-ExtJS: Global configuration doesn't work as documented

Tue May 11 09:46:14 2010 jasonk [...] cpan.org - Ticket created

Subject:

Global configuration doesn't work as documented

The documentation says: Global configuration for all controllers which use CatalystX::Controller::ExtJS::REST: MyApp->config( { CatalystX::Controller::ExtJS::REST => { key => value } } ); However, the code says: my $parent_config = $c->config->{'ControllerX::ExtJS::REST'} || {}; -- www.jasonkohles.com

Sun May 16 00:14:22 2010 onken [...] netcubed.de - Correspondence added

Am Di 11. Mai 2010, 09:46:14, JASONK schrieb: Show quoted text

> The documentation says: > > Global configuration for all controllers which use > CatalystX::Controller::ExtJS::REST: > > MyApp->config( { > CatalystX::Controller::ExtJS::REST => > { key => value } > } ); > > However, the code says: > > my $parent_config = $c->config->{'ControllerX::ExtJS::REST'} || {};

Hi, I'd prefer to stick to the key mentioned in the documentation (CatalystX::Controller::ExtJS::REST). It is about the controller after all... Since this would break backwards compat, I'd merge CatalystX::Controller::ExtJS::REST and CatalystX::ExtJS::REST (with former having precedence). Which key do you prefer?

Sun May 16 00:14:23 2010 The RT System itself - Status changed from 'new' to 'open'

Sat Jun 05 22:14:03 2010 onken [...] netcubed.de - Correspondence added

This has been fixed in version 1.101570. It now honors both configurations with ControllerX::Controller::ExtJS::REST having precedence over ControllerX::ExtJS::REST. Cheers, moritz

Sat Jun 05 22:14:04 2010 onken [...] netcubed.de - Status changed from 'open' to 'resolved'