Skip to content

Commit

Permalink
Browse files Browse the repository at this point in the history
quote response codes consistently
  • Loading branch information
kraih committed Oct 24, 2015
1 parent 74b60ae commit c65fa82
Show file tree
Hide file tree
Showing 2 changed files with 7 additions and 7 deletions.
2 changes: 1 addition & 1 deletion lib/Mojo/Transaction.pm
Expand Up @@ -287,7 +287,7 @@ in a subclass.
Returns the L<Mojo::Message::Response> object from L</"res"> if transaction was
successful or C<undef> otherwise. Connection and parser errors have only a
message in L</"error">, 400 and 500 responses also a code.
message in L</"error">, C<400> and C<500> responses also a code.
# Sensible exception handling
if (my $res = $tx->success) { say $res->body }
Expand Down
12 changes: 6 additions & 6 deletions lib/Mojolicious/Guides/Rendering.pod
Expand Up @@ -431,12 +431,12 @@ L<Mojolicious::Plugin::DefaultHelpers/"accepts">.

=head2 Rendering C<exception> and C<not_found> pages

By now you've probably already encountered the built-in 404 (Not Found) and 500
(Server Error) pages, that get rendered automatically when you make a mistake.
Those are fallbacks for when your own exception handling fails, which can be
especially helpful during development. You can also render them manually with
the helpers L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>exception"> and
L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>not_found">.
By now you've probably already encountered the built-in C<404> (Not Found) and
C<500> (Server Error) pages, that get rendered automatically when you make a
mistake. Those are fallbacks for when your own exception handling fails, which
can be especially helpful during development. You can also render them manually
with the helpers L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>exception">
and L<Mojolicious::Plugin::DefaultHelpers/"reply-E<gt>not_found">.

use Mojolicious::Lite;
use Scalar::Util 'looks_like_number';
Expand Down

0 comments on commit c65fa82

Please sign in to comment.