X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=lib%2FCatalyst%2FUpgrading.pod;h=fe9da9c2a1e653d4ffd0404532f1e74ca5709094;hp=b0d37e26bf6199cbf0e500d2029c140f62f25e3a;hb=b8b29bac1f1da028ccc894b1e0d2992e120eed9a;hpb=949f330d1f0f7d5fc868ddeb6f338733a2dfa39f diff --git a/lib/Catalyst/Upgrading.pod b/lib/Catalyst/Upgrading.pod index b0d37e2..fe9da9c 100644 --- a/lib/Catalyst/Upgrading.pod +++ b/lib/Catalyst/Upgrading.pod @@ -2,6 +2,99 @@ Catalyst::Upgrading - Instructions for upgrading to the latest Catalyst +=head1 Upgrading to Catalyst 5.90080 + +UTF8 encoding is now default. For temporary backwards compatibility, if this +change is causing you trouble, you can disable it by setting the application +configuration option to undef: + + MyApp->config(encoding => undef); + +But please consider this a temporary measure since it is the intention that +UTF8 is enabled going forwards and the expectation is that other ecosystem +projects will assume this as well. At some point you application will not +correctly function without this setting. + +A number of projects in the wider ecosystem required minor updates to be able +to work correctly. Here's the known list: + +L, L, L, +L, L + +You will need to update to modern versions in most cases, although quite a few +of these only needed minor test case and documentation changes so you will need +to review the changelog of each one that is relevant to you to determine your +true upgrade needs. + +=head1 Upgrading to Catalyst 5.90060 + +Starting in the v5.90059_001 development release, the regexp dispatch type is +no longer automatically included as a dependency. If you are still using this +dispatch type, you need to add L into your build +system. + +The standalone distribution of Regexp will be supported for the time being, but +should we find that supporting it prevents us from moving L forward +in necessary ways, we reserve the right to drop that support. It is highly +recommended that you use this last stage of deprecation to change your code. + +=head1 Upgrading to Catalyst 5.90040 + +=head2 Catalyst::Plugin::Unicode::Encoding is now core + +The previously stand alone Unicode support module L +has been brought into core as a default plugin. Going forward, all you need is +to add a configuration setting for the encoding type. For example: + + package Myapp::Web; + + use Catalyst; + + __PACKAGE__->config( encoding => 'UTF-8' ); + +Please note that this is different from the old stand alone plugin which applied +C encoding by default (that is, if you did not set an explicit +C configuration value, it assumed you wanted UTF-8). In order to +preserve backwards compatibility you will need to explicitly turn it on via the +configuration setting. THIS MIGHT CHANGE IN THE FUTURE, so please consider +starting to test your application with proper UTF-8 support and remove all those +crappy hacks you munged into the code because you didn't know the Plugin +existed :) + +For people that are using the Plugin, you will note a startup warning suggesting +that you can remove it from the plugin list. When you do so, please remember to +add the configuration setting, since you can no longer rely on the default being +UTF-8. We'll add it for you if you continue to use the stand alone plugin and +we detect this, but this backwards compatibility shim will likely be removed in +a few releases (trying to clean up the codebase after all). + +If you have trouble with any of this, please bring it to the attention of the +Catalyst maintainer group. + +=head2 basic async and event loop support + +This version of L offers some support for using L and +L event loops in your application. These changes should work +fine for most applications however if you are already trying to perform +some streaming, minor changes in this area of the code might affect your +functionality. Please see L for more and for a +basic example. + +We consider this feature experimental. We will try not to break it, but we +reserve the right to make necessary changes to fix major issues that people +run into when the use this functionality in the wild. + +=head1 Upgrading to Catalyst 5.90030 + +=head2 Regex dispatch type is deprecated. + +The Regex dispatchtype (L) has been deprecated. + +You are encouraged to move your application to Chained dispatch (L). + +If you cannot do so, please add a dependency to Catalyst::DispatchType::Regex to your application's +Makefile.PL + =head1 Upgrading to Catalyst 5.9 The major change is that L, a toolkit for using the L @@ -45,7 +138,7 @@ to use L. The engines that are built upon the various iterations of mod_perl, L (for mod_perl 1, and Apache 1.x) and L (for mod_perl 2, and Apache 2.x), -should be seamless upgrades and will work using using L +should be seamless upgrades and will work using L or L as required. L, however, is no longer supported, as @@ -65,7 +158,7 @@ script is upgraded to use L. If you were using L there is no upgrade needed if your myapp_cgi.pl script is already upgraded to use L. -=head2 Upgrading the Preforking Engine +=head2 Upgrading Catalyst::Engine::HTTP::Prefork If you were using L then L is automatically loaded. You should (at least) change your C @@ -223,7 +316,7 @@ been made which could cause incompatibilities. If your application or plugin is using deprecated code, or relying on side effects, then you could have issues upgrading to this release. -Most issues found with pre-existing components have been easy to +Most issues found with existing components have been easy to solve. This document provides a complete description of behavior changes which may cause compatibility issues, and of new Catalyst warnings which might be unclear. @@ -281,7 +374,7 @@ replaces L with L, forcing all components to resolve methods using C3, rather than the unpredictable dispatch order of L. -This issue is characterised by your application failing to start due to an +This issue manifests itself by your application failing to start due to an error message about having a non-linear @ISA. The Catalyst plugin most often causing this is @@ -515,6 +608,13 @@ The correct fix is to re-arrange your class's inheritance hierarchy so that the COMPONENT method you would like to inherit is the first (left-hand most) COMPONENT method in your @ISA. +=head2 Development server relying on environment variables + +Previously, the development server would allow propagation of system +environment variables into the request environment, this has changed with the +adoption of Plack. You can use L to achieve the +same effect. + =head1 WARNINGS =head2 Actions in your application class