1 package CDICompatTestPlugin;
3 # This plugin specificially tests an edge case of C::D::I compat,
4 # where you load a plugin which creates an accessor with the same
5 # name as a class data accessor (_config in this case)..
7 # This is what happens if you use the authentication back-compat
8 # stuff, as C::A::Plugin::Credential::Password is added to the plugin
9 # list, and that uses base C::A::C::P class, does the mk_accessors.
11 # If a class data method called _config hasn't been created in
12 # MyApp ($app below), then our call to ->config gets our accessor
13 # (rather than the class data one), and we fail..
17 use base qw/Class::Accessor::Fast/;
19 __PACKAGE__->mk_accessors(qw/_config/);
25 $app->next::method(@_);
28 # However, if we are too enthusiastic about adding accessors to the
29 # MyApp package, then this method isn't called (as there is a local
32 # Note - use a different package here, so that Moose's
33 # package detection code doesn't get confused..
34 $CDICompatTestPlugin::Data::HAS_RUN_SETUP_FINISHED = 0;
38 $CDICompatTestPlugin::Data::HAS_RUN_SETUP_FINISHED = 1;
39 $app->next::method(@_);