Commit graph

7 commits

Author SHA1 Message Date
sno
d208a1206f Updating www/p5-Catalyst-Action-REST from 0.81 to 0.83
Upstream changes:
Mon  8 Feb 2010 22:17:12 GMT - Release 0.83
  Make it possible to deserialize a request with a DELETE method. This probably
  breaks 'strict' REST guidelines, but is useful for being able to delete multiple
  resources from a single call by providing a batch delete method.

  Remove JSONP from the list of default serializers (RT#54336)

  Fix MANIFEST (RT#54408)

Thu  4 Feb 2010 22:31:57 GMT - Release 0.82
  Integrated Catalyst::Request::REST::ForBrowsers as
  Catalyst::TraitFor::Request::ForBrowsers. (Dave Rolsky)

  Clarified docs so that they encourage the use of the request traits, rather
  than using Catalyst::Request::REST. (Dave Rolsky)

  When Catalyst::Action::REST or Controller::REST automatically add the trait,
  your request class will no longer end up getting set to
  Catalyst::Request::REST. Instead, creates an anon class with the appropriate
  role. (Dave Rolsky)

  Shut up log output from the tests. (Dave Rolsky)

  Added a $VERSION to every module, mostly to make sure that when people
  install Catalyst::Request::REST::ForBrowsers, they get the version in this
  distro. (Dave Rolsky)

  Change Catalyst::Action::Serialize, Catalyst::Action::Deserialize and
  Catalyst::Action::SerializeBase to be more Moose like.

  Fix JSON and JSON::XS to encode_blessed. (fREW)

  Fix Catalyst::Action::Serialize to use objects instead of classes. (fREW)

  Fix doc nits. (RT#53780)
2010-03-10 11:02:23 +00:00
sno
2a8ddece40 Updating www/p5-Catalyst-Action-REST from 0.78 to 0.81
pkgsrc changes:
- Adjusting dependencies
- Adjust module type

Upstream changes:
Thu 14 Jan 20:56:00 GMT 2010 - Release 0.81
  Add a JSONP serialization type.

Sat 19 Dec 14:54:00 GMT 2009 - Release 0.80
  Convert all classes to Moose

  Change Catalyst::Request::REST to be a mostly empty class, with
  all the functionality in Catalyst::TraitFor::Request::REST

  Simplify _get_allowed_methods method (aristotle)

  Rework serializer return so that serializers throw an exception in
  the case of issues serializing the data (hobbs).

Fri 11 Dec 01:08:00 GMT 2009 - Release 0.79
  Cope with invalid (missing required q parameter) header like:
  application/json; charset="utf-8"

  Fix documentation to not mention deprecated things and generally be
  in better style.

  Make author information consistant and only in one module.
2010-02-02 11:43:13 +00:00
rhaen
ed7745af8a Fixed a typo in DEPENDS - Moose is required 2009-10-16 11:32:35 +00:00
rhaen
48d51d30a4 - updated to 0.78
ChangeLog:
Mon 28 Sep 15:01:03 BST 2009 - Release 0.78

  Require Moose for the tests (RT#50066).
2009-10-16 11:20:32 +00:00
sno
15707ea5a1 Bumping revision of packages which depend direct or indirect on
devel/p5-Class-MOP. A late detected incompible change forced it.
2009-09-24 06:50:10 +00:00
sno
39bd04e831 Updating www/p5-Catalyst-Action-REST from 0.76 to 0.77
pkgsrc changes:
  - Module::Pluggable is in version 3.6 include in Perl 5.10.0
    --> using this one as dependency

Upstream changes:
Thu 27 Aug 02:21:09 BST 2009 - Release 0.77

  Allow dispatching to Catalyst Actions, for use with ActionClasses
  etc - fREW

  Fix test if CATALYST_DEBUG environment variable is set
2009-09-13 20:28:08 +00:00
abs
e38940460b Added www/p5-Catalyst-Action-REST version 0.76
This Action handles doing automatic method dispatching for REST
requests. It takes a normal Catalyst action, and changes the dispatch
to append an underscore and method name.

For example, in the synopsis above, calling GET on "/foo" would
result in the foo_GET method being dispatched.

If a method is requested that is not implemented, this action will
return a status 405 (Method Not Found). It will populate the "Allow"
header with the list of implemented request methods. You can override
this behavior by implementing a custom 405 handler like so:

   sub foo_not_implemented {
      ... handle not implemented methods ...
   }

If you do not provide an _OPTIONS subroutine, we will automatically
respond with a 200 OK. The "Allow" header will be populated with
the list of implemented request methods.

It is likely that you really want to look at Catalyst::Controller::REST,
which brings this class together with automatic Serialization of
requests and responses.
2009-08-27 10:37:24 +00:00