| Subject: | Documentation issues |
* The example should use parent instead of 'base'.
* "based on the requests content-type header" -> "based on the request's
[...]"
* A more fleshed out example for thing_PUT would be helpful, as it's not
obvious at all for a new user how to retrieve the PUT or POST request
data (that bit is explained in Catalyst::Action::Deserialize). Here's a
suggested example:
# Answer PUT requests to "thing"
sub thing_PUT {
$radiohead = $req->data->{radiohead};
$self->status_created(
$c,
location => $c->req->uri->as_string,
entity => {
radiohead => $radiohead,
}
);
The fact that deserialized data ends up in $c->req->data could be
appended to "The HTTP POST, PUT, and OPTIONS methods will all
automatically deserialize the contents of $c->request->body", as for
example: "The HTTP POST, PUT, and OPTIONS methods will all automatically
L<Catalyst::Action::Deserialize|deserialize> the contents of
$c->request->body into the $c->request->data hashref".
* Would be nice if Catalyst::Action::SerializeBase provided a $VERSION.