view release on metacpan or  search on metacpan

Changes  view on Meta::CPAN

5.90049_006 - 2013-11-04
  - Fixed case where test could fail when Starman was partly installed (n0body++)
  - Fixed missing date information in previous release

5.90049_005 - 2013-10-31
  - NEW FEATURE:  New Controller action attribute 'Consumes', which allows you
    to specify the content type of the incoming request.  This makes it easier
    to create actions that only handle certain content type POST or PUT, such
    as actions that only handle JSON or actions that only understand classic
    HTML forms.
  - NEW FEATURE: Request->body_data is now also populated from classic HTML 
    Forms using CGI::Struct to support nested data.  For non nested data you
    should use the classic ->body_parameters method.
  - Removed PSGI $env keys that are added on the 'plack.request.*' namespace
    since after discussion it was clear those keys are not part of the public
    API.  Keys removed: 'plack.request.query', 'plack.request.body', 
    'plack.request.merged' and 'plack.request.http.body'. Altered some test
    cases to reflect this change.

5.90049_004 - 2013-10-18
  - JSON Data handler looks for both JSON::MaybeXS and JSON, and uses
    whichever is first (preferring to find JSON::MaybeXS).  This should
    improve compatibility as you likely already have one installed.
  - Fixed a warning in the server script (bokutin++)
  - We now populate various Plack $env keys in order to play nice with
    downstream middleware or plack apps (and to reduce processing if
    those keys already exist).  Keys added:
      - plack.request.query
      - plack.request.body
      - plack.request.merged
      - plack.request.http.body
    (NOTE: REMOVED IN 5.90049_005)
  - If incoming input (from a POST or PUT) is not buffered, create the
    buffer and set the correct psgi env keys to note this for downstream
    psgi apps / middleware.  This should solve some issues where Catalyst
    sucks up the body input but its not buffered so downstream apps can't
    read it (for example FCGI does not buffer).  We now also try to make
    sure the body content input is reset to the start of the filehandle
    so that we are polite to downstream middleware /apps.
  - NEW FEATURE: Catalyst::Response can now pull response from a PSGI
    specification response.  This makes it easier to host external Plack
    applications under Catalyst.  See Catalyst::Response->from_psgi_response
  - NEW FEATURE: New configuration option 'use_hash_multivalue_in_request'
    will populate $request methods 'parameters', 'body_parameters' and
    'query_parameters' with an instance of Hash::MultiValue instead of a
    HashRef.  This is used by Plack and is intended to reduce the need to
    write defensive logic since you are never sure if an incoming parameter
    is a scalar or arrayref.
  - NEW FEATURE: We now experimentally support Net::Async::HTTP::Server
    and IO-Async based event loops.  Examples will follow.

5.90049_003 - 2013-09-20
  - Documented the new body_data method added in the previous release
  - Merged from master many important bugfixes and forward compatibility
    updates, including:
    - Use modern preferred method for Moose metaclass access and many other
      small changes to how we use Moose for better forward compat (ether++)
    - Killed some evil use of $@ (ether++)
    - spelling fixes and documentation updates (ether++), (gerda++)
    - use Test::Fatal over Test::Exception (ether++)
    - Misc. test case fixes to modernize code (ether++)
    - Added a first pass cpanfile, to try and make it easier to bootstrap
      a development setup (ether++)

5.90049_002 - 2013-08-20
  - Fixed loading middleware from project directory
  - Fixed some pointless warnings when middleware class lacked VERSION
  - NEW FEATURE: Declare global 'data_handlers' for parsing HTTP POST/PUT
    alternative content, and created default JSON handler.  Yes, now Catalyst
    handles JSON request content out of the box!  More docs eventually but
    for now see the DATA HANDLERS section in Catalyst.pm (or review the test
    case t/data_handler.t

5.90049_001 - 2013-07-26
  - Declare PSGI compliant Middleware as part of your Catalyst Application via
    a new configuration key, "psgi_middleware".
  - Increased lowest allowed module version for Module::Pluggable to be 4.7 (up
    from 3.4) to solve the fact this is no longer bundled with Perl in v5.18.

5.90042 - 2013-06-14
  - Removed more places where an optional dependency shows up in the test
    suite. Hopefully really fixed the unicode regression introduced in 5.90040
  - reverted the change we introduced in 5.90040 where a unicode conversion
    error warned instead of died.  Now it dies again, like in the stand alone
    plugin
  - More work to make sure nothing happens with encoding unless you explicitly
    ask for encoding
  - Code to hopefully fix an issue where file uploads using the unicode plugin
    caused trouble.

5.90041 - 2013-06-14
  - Bug fix release to fix regressions introduced in previous.  I would consider
    this a likely upgrade and if you are having trouble with the previous I hope
    this fixes all of them.
  - Fix regression with the cored Unicode plugin that broke systems where you are
    setting encoding type in an external configuration file
  - Fixed circular dependency introduced when we cored the unicode plugin tests
  - Fixed a longstanding problem with stats when locale uses , instead of . for
    number decimals
  - Fixed some docs that didn't properly date the previous release.

5.90040 - 2013-06-12
  ! Stricter checking of attributes in Catalyst::DispatchType::Chained:
    1) Only allow one of either :CaptureArgs or :Args
    2) :CaptureArgs() argument must be numeric
    3) :CaptureArgs() and :Args() arguments cannot be negative
  - Add Devel::InnerPackage to dependencies, fixing tests on Perl 5.17.11
    as it's been removed from core. RT#84787
  - New support for closing over the PSGI $writer object, useful for working
    with event loops.
  - lets you access a psgix.io socket, if your server supports it, for manual
    handling of the client - server communication, such as for websockets.
  - Fix waiting for the server to start in t/author/http-server.t
  - new config flag 'abort_chain_on_error_fix' that exits immediately when a
    action in an action chain throws and error (fixes issues where currently
    the remaining actions are processed and the error is handled at chain
    termination).
  - Cored the Encoding plugin.  Now get unicode out of the box by just setting
    $c->config->{encoding} = 'UTF-8'.  BACKCOMPAT WARNING: If you are using 
    the Encoding plugin on CPAN, we skip it to avoid double encoding issues, so