File Coverage

blib/lib/Kelp/Exception.pm

Criterion	Covered	Total	%
statement	13	13	100.0
branch	2	2	100.0
condition	2	3	66.6
subroutine	4	4	100.0
pod	1	2	50.0
total	22	24	91.6

use Kelp::Base;

use Carp;

attr -code => sub { croak 'code is required' };

attr 'body';

    my ($class, $code, %params) = @_;

    croak 'Kelp::Exception can only accept 4XX or 5XX codes'
        unless defined $code && $code =~ /^[45]\d\d$/;

    $params{code} = $code;
    return $class->SUPER::new(%params);
}

    my $class = shift;
    my $ex = $class->new(@_);
    die $ex;
}

1;


=pod

=head1 NAME

Kelp::Exception - Tiny HTTP exceptions

=head1 SYNOPSIS

    Exception->throw(400, body => 'The request was malformed');

    # code is optional - 500 by default
    Kelp::Exception->throw;

    # can control what user sees - even in deployment (unlike string exceptions)
    Kelp::Exception->throw(501, body => {
        status => \0,
        error => 'This method is not yet implemented'
    });

=head1 DESCRIPTION

This module offers a fine-grained control of what the user sees when an
exception occurs. Generally, this could also be done by setting the
result code manually, but that requires passing the Kelp instance around and
does not immediately end the handling code. Exceptions are a way to end route
handler execution from deep within the call stack.

This implementation is very incomplete and can only handle 4XX and 5XX status
codes, meaning that you can't do redirects and normal responses like this. It
also tries to maintain some degree of compatibility with L<HTTP::Exception>
without its complexity.

=head1 ATTRIBUTES

=head2 code

HTTP status code. Only possible are 5XX and 4XX.

Readonly.

=head2 body

Required. Body of the request - can be a string for HTML and a hashref /
arrayref for JSON responses.

A string will be passed to C<< $response->render_error >> to be rendered inside
an error template, if available. A reference will be JSON encoded if JSON is
available, otherwise will produce an exception.

Content type for the response will be set accordingly.

=head1 METHODS

=head2 throw

    # both do exactly the same
    Kelp::Exception->throw(...);
    die Kelp::Exception->new(...);

Same as simply constructing and calling die on an object.

=head1 CAVEATS

=over

=item

Code 500 exceptions will not be logged, as it is considered something that a
web developer know about. They are not thrown anywhere in Kelp internal code,
so only user code can fall victim to this.

=item

If there is no content type set, and the exception body is not a reference,
then a C<text/html> content type will be guessed and the body text will be
passed to an error template, if available.

=back

=cut