3 Catalyst::Delta - Overview of changes between versions of Catalyst
7 This is an overview of the user-visible changes to Catalyst in version 5.9.
11 =head1 PREVIOUS VERSIONS
17 Please see L<Catalyst::Upgrading> for a full description of how changes in the
18 framework may affect your application.
20 Below is a brief list of features which have been deprecated in this release:
24 =item ::[MVC]:: style naming scheme has been deprecated and will warn
26 =item NEXT is deprecated for all applications and components, use MRO::Compat
28 =item Dispatcher methods which are an implementation detail made private, public versions now warn.
30 =item MyApp->plugin method is deprecated, use L<Catalyst::Model::Adaptor> instead.
32 =item __PACKAGE__->mk_accessors() is supported for backward compatibility only, use Moose attributes instead in new code.
34 =item Use of Catalyst::Base now warns
44 =item Fix forwarding to Catalyst::Action objects.
46 =item Add the dispatch_type method
52 The development server restarter has been improved to be compatible with
53 immutable Moose classes, and also to optionally use
54 L<B::Hooks::OP::Check::StashChange> to handle more complex application layouts
57 =head3 $c->uri_for_action method.
59 Give a private path to the Catalyst action you want to create a URI for.
63 Log levels have been made additive.
65 =head3 L<Catalyst::Test>
69 =item Change to use L<Sub::Exporter>.
71 =item Support mocking multiple virtual hosts
73 =item New methods like action_ok and action_redirect to write more compact tests
77 =head3 Catalyst::Response
83 New print method which prints @data to the output stream, separated by $,.
84 This lets you pass the response object to functions that want to write to an
89 Added code method as an alias for C<< $res->status >>
93 =head3 Consequences of the Moose back end
99 Components are fully compatible with Moose, and all Moose features, such as
100 method modifiers, attributes, roles, BUILD and BUILDARGS methods are fully
101 supported and may be used in components and applications.
105 Many reusable extensions which would previously have been plugins or base
106 classes are better implemented as Moose roles.
110 L<MooseX::MethodAttributes::Inheritable> is used to contain action
111 attributes. This means that attributes are represented in the MOP, and
112 decouples action creation from attributes.
116 There is a reasonable API in Catalyst::Controller for working with
117 and registering actions, allowing a controller sub-class to replace
118 subroutine attributes for action declarations with an alternate
123 Refactored capturing of $app from L<Catalyst::Controller> into
124 L<Catalyst::Component::ApplicationAttribute> for easier reuse in other
129 Your application class is forced to become immutable at the end of compilation.
139 Don't ignore SIGCHLD while handling requests with the development server, so that
140 system() and other ways of creating child processes work as expected.
144 Fixes for FastCGI when used with IIS 6.0
148 Fix a bug in uri_for which could cause it to generate paths with multiple
153 Fix a bug in Catalyst::Stats, stopping garbage being inserted into
154 the stats if a user calls begin => but no end