[Catalyst-commits] r14478 - trunk/examples/CatalystAdvent/root/2013

jnapiorkowski at dev.catalyst.perl.org jnapiorkowski at dev.catalyst.perl.org
Fri Dec 6 16:22:38 GMT 2013


Author: jnapiorkowski
Date: 2013-12-06 16:22:38 +0000 (Fri, 06 Dec 2013)
New Revision: 14478

Modified:
   trunk/examples/CatalystAdvent/root/2013/6.pod
Log:
typo fix

Modified: trunk/examples/CatalystAdvent/root/2013/6.pod
===================================================================
--- trunk/examples/CatalystAdvent/root/2013/6.pod	2013-12-06 16:08:07 UTC (rev 14477)
+++ trunk/examples/CatalystAdvent/root/2013/6.pod	2013-12-06 16:22:38 UTC (rev 14478)
@@ -76,7 +76,7 @@
 required, and you can override the build in JSON parsing since we apply
 you customizations ontop of the defaults.
 
-So, how do you access this new parsed content?  We've added a new attributes
+So, how do you access this new parsed content?  We've added a new attribute
 to L<Catalyst::Request> called C<body_data>.  This attribute is lazy, so
 unless you actually ask for it, we don't attempt to parse any request content
 against the defined L<data_handlers>.  So if you wrote a ton of your own
@@ -88,7 +88,7 @@
 
     sub update_user : POST Path(/User) Consumes(JSON) {
       my $p = (my $c = pop)->req->body_data;
-      $c->res->body("My name is $posted->{name} and my age is $p->{age}");
+      $c->res->body("My name is $p->{name} and my age is $p->{age}");
     }
 
 Basically this is very similar to the request object's C<body_parameters>




More information about the Catalyst-commits mailing list