X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FUpgrading.pod;h=58f827f88509b9020a9c408e58e47be297697e6b;hb=56089c3b1874315737efea071b798453dbb6c8eb;hp=35cee5de4bc9aff2ebbae001e10d25bc3afb8279;hpb=d76c88f37cf908aaff3f13532f7174ece1b0156b;p=catagits%2FCatalyst-Runtime.git diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod index 35cee5d..58f827f 100644 --- a/lib/Catalyst/Upgrading.pod +++ b/lib/Catalyst/Upgrading.pod @@ -85,7 +85,7 @@ you identify the ones in conflict, and resolve them. To be able to generate a linear @ISA, the list of superclasses for each class must be resolvable using the C3 algorithm. Unfortunately, when superclasses are being used as mixins (to add functionality used in your class), -and with multiple inheritence, it is easy to get this wrong. +and with multiple inheritance, it is easy to get this wrong. Most common is the case of: @@ -217,7 +217,7 @@ been called, and will not call them again. Using this now causes infinite recursion between MyApp::setup and Catalyst::setup, due to other backwards compatibility issues related to how -plugin setup works. Moose method modifiers like C<< before|after|around 'setup +plugin setup works. Moose method modifiers like C<< before|after|around setup => sub { ... }; >> also will not operate correctly on the setup method. The right way to do it is this: @@ -316,19 +316,19 @@ This warning, also affects tests. You should move actions in your test, creating a myTest::Controller::Root, like the following example: package MyTest::Controller::Root; - + use strict; use warnings; - + use parent 'Catalyst::Controller'; - + __PACKAGE__->config(namespace => ''); - + sub action : Local { my ( $self, $c ) = @_; $c->do_something; } - + 1; =head2 ::[MVC]:: naming scheme @@ -401,7 +401,7 @@ to B of the packages defined within that component. Calling the plugin method is deprecated, and calling it at run time is B. -Instead you are recommended to use L< Catalyst::Model::Adaptor > or similar to +Instead you are recommended to use L or similar to compose the functionality you need outside of the main application name space. Calling the plugin method will not be supported past Catalyst 5.81.