X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?p=catagits%2FCatalyst-Runtime.git;a=blobdiff_plain;f=Changes;h=416e2b78359404d13d1f326d32fea9ca02857b70;hp=416620d25aadee8faf0bece0baf9eb57a39979a3;hb=d9f0a350554cca79adefd4e97b4982d431f8c914;hpb=f382b264b4c2b378c90970e5039502fd60e49a7f diff --git a/Changes b/Changes index 416620d..416e2b7 100644 --- a/Changes +++ b/Changes @@ -1,6 +1,60 @@ # This file documents the revision history for Perl extension Catalyst. -5.90083 - 2014-02-16 +5.90089_002 - 2015-04-03 + - Changed the way we check for presence of Type::Tiny in a test case to be + more explicit in the version requirement. Hopefully a fix for reported + test fail. + - When declaring type constraints in Args and CaptureArgs, if you want to + use a Moose builtin type (or a custom stringy type that you've already + defined and associated with the Moose::TypeRegistry) you must now quote + the type name. This is to clearly disambiguate between Moose stringy types + and imported types. + - Additional changes to type constraint detection to between determine when a + type constraint for reference types have a measured number of arguments or + not. clarify restriction on reference type constraints. + +5.90089_001 - 2015-03-26 + - New development branch synched with 5.90085. + - New Feature: Type Constraints on Args/CaptureArgs. Allows you to declare + a Moose, MooseX::Types or Type::Tiny named constraint on your Arg or + CaptureArg. + - When using $c->uri_for (or the derived $c->uri_for_action) and the target + action has type constrainted args (or captures), verify that the proposed + URL matches the defined args. In general $c->uri_for will be a bit more + noisy if the supplied arguments are not correct. + - New top level document on Route matching. (Catalyst::RouteMatching). This + document is still in development, but is worth review and comments. + +5.90085 - 2015-03-25 + - Small change to Catalyst::Action to prevent autovivication of Args value (dim1++) + - Minor typo fixes (Abraxxa++) + - Make sure than when using chained actions and when more than one action + matches the same path specification AND has Args(0), that we follow the + "in a tie, the last action defined wins" rule. There is a small chance + this is a breaking change for you. See Catalyst::Upgrading for more. + You may use the application configuration setting "use_chained_args_0_special_case" + to disable this new behavior, if you must for back-compat reasons. + - Added PATCH HTTP Method action attribute shortcut. + - Several new configuration options aimed to give improved backwards compatibility + for when your URL query parameters or keywords have non UTF-8 encodings. + See Catalyst::Upgrading. + +5.90084 - 2015-02-23 + - Small change to the way body parameters are created in order to prevent + trying to create parameters twice. + - Use new HTTP::Body and code updates to fix issue when POSTed params have + non UTF-8 charset encodings or otherwise complex upload parts that are not + file uploads. In these cases when Catalyst can't determine what the value of + a form upload is, will return an instance of Catalyst::Request::PartData with + all the information need to figure it out. Documentation about this corner + case. For RT https://rt.cpan.org/Ticket/Display.html?id=101556 + - Two new application configuration parameters 'skip_body_param_unicode_decoding' + and 'skip_complex_post_part_handling' to assist you with any backward + compatibility issues with all the new UTF8 work in the most recent stable + Catalyst. You may use these settings to TEMPORARILY disable certain new + features while you are seeking a long term fix. + +5.90083 - 2015-02-16 - Fixed typo in support for OPTIONS method matching (andre++) - Stop using $env->{'plack.request.query'} as a query parsing optimization since 1) it doesn't belong to us and 2) there's subtle differences in the