X-Git-Url: http://git.shadowcat.co.uk/gitweb/gitweb.cgi?a=blobdiff_plain;f=lib%2FCatalyst%2FAction%2FDeserialize.pm;h=5be60f3513ff0e35dde87584ee12a4e8df81f252;hb=9819a955ab18ead8943cc8a912dcddcacbade74b;hp=504fc30b78f8bad5e02388ee54c78f820adf33f3;hpb=a042dad01479cdd9e5e2c6e8581d2cdd0f604fa7;p=catagits%2FCatalyst-Action-REST.git diff --git a/lib/Catalyst/Action/Deserialize.pm b/lib/Catalyst/Action/Deserialize.pm index 504fc30..5be60f3 100644 --- a/lib/Catalyst/Action/Deserialize.pm +++ b/lib/Catalyst/Action/Deserialize.pm @@ -6,19 +6,33 @@ use namespace::autoclean; extends 'Catalyst::Action::SerializeBase'; use Module::Pluggable::Object; use MRO::Compat; - -our $VERSION = '0.83'; -$VERSION = eval $VERSION; +use Moose::Util::TypeConstraints; has plugins => ( is => 'rw' ); +has deserialize_http_methods => ( + traits => ['Hash'], + isa => do { + my $tc = subtype as 'HashRef[Str]'; + coerce $tc, from 'ArrayRef[Str]', + via { +{ map { ($_ => 1) } @$_ } }; + $tc; + }, + coerce => 1, + builder => '_build_deserialize_http_methods', + handles => { + deserialize_http_methods => 'keys', + _deserialize_handles_http_method => 'exists', + }, +); + +sub _build_deserialize_http_methods { [qw(POST PUT OPTIONS DELETE)] } + sub execute { my $self = shift; my ( $controller, $c ) = @_; - my @demethods = qw(POST PUT OPTIONS DELETE); - my $method = $c->request->method; - if ( grep /^$method$/, @demethods ) { + if ( !defined($c->req->data) && $self->_deserialize_handles_http_method($c->request->method) ) { my ( $sclass, $sarg, $content_type ) = $self->_load_content_plugins( 'Catalyst::Action::Deserialize', $controller, $c ); @@ -30,9 +44,9 @@ sub execute { $rc = $sclass->execute( $controller, $c ); } if ( $rc eq "0" ) { - return $self->_unsupported_media_type( $c, $content_type ); + return $self->unsupported_media_type( $c, $content_type ); } elsif ( $rc ne "1" ) { - return $self->_serialize_bad_request( $c, $content_type, $rc ); + return $self->serialize_bad_request( $c, $content_type, $rc ); } } @@ -64,11 +78,27 @@ Catalyst::Action::Deserialize - Deserialize Data in a Request =head1 DESCRIPTION -This action will deserialize HTTP POST, PUT, and OPTIONS requests. +This action will deserialize HTTP POST, PUT, OPTIONS and DELETE requests. It assumes that the body of the HTTP Request is a serialized object. The serializer is selected by introspecting the requests content-type header. +If you want deserialize any other HTTP method besides POST, PUT, +OPTIONS and DELETE you can do this by setting the +C<< deserialize_http_methods >> list via C<< action_args >>. +Just modify the config in your controller and define a list of HTTP +methods the deserialization should happen for: + + __PACKAGE__->config( + action_args => { + '*' => { + deserialize_http_methods => [qw(POST PUT OPTIONS DELETE GET)] + } + } + ); + +See also L. + The specifics of deserializing each content-type is implemented as a plugin to L. You can see a list of currently implemented plugins in L. @@ -87,6 +117,43 @@ Will work just fine. When you use this module, the request class will be changed to L. +=head1 RFC 7231 Compliance Mode + +To maintain backwards compatibility with the module's original functionality, +where it was assumed the deserialize and serialize content types are the same, +an optional compliance mode can be enabled to break this assumption. + + __PACKAGE__->config( + 'compliance_mode' => 1, + 'default' => 'text/x-yaml', + 'stash_key' => 'rest', + 'map' => { + 'text/x-yaml' => 'YAML', + 'text/x-data-dumper' => [ 'Data::Serializer', 'Data::Dumper' ], + }, + 'deserialize_default => 'application/json', + 'deserialize_map' => { + 'application/json' => 'JSON', + }, + ); + +Three extra keys are added to the controller configuration. compliance_mode, a +boolean to enable the mode. And a parallel set of content type mappings +'deserialize_default' and 'deserialize_map' to mirror the default/map +configuration keys. + +The module will use the default/map keys when negotiating the serializing +content type specified by the client in the Accept header. And will use the +deserialize_default/deserialize_map in conjunction with the Content-Type +header where the client is giving the content type being sent in the request. + +=head1 CUSTOM ERRORS + +For building custom error responses when de-serialization fails, you can create +an ActionRole (and use L to apply it to the +C action) which overrides C and/or C +methods. + =head1 SEE ALSO You likely want to look at L, which implements