Improve developer experience for handling server errors about inertia-laravel

[reinink]

I guess we could do something like this:

public function render($request, Exception $exception)
{
    return Inertia::renderErrorResponse(
        string $component,
        Response $response,
        array $codes
    );
}

For example:

public function render($request, Exception $exception)
{
    return Inertia::renderErrorResponse(
        'Error',
        parent::render($request, $exception),
        [500, 503, 404, 403]
    );
}

Again, not sure that this is worth adding to the framework, since it really doesn't require that much code to just do this yourself.

[reinink]

I just updated the docs with a pretty straight forward solution:

use Inertia\Inertia;

public function render($request, Exception $exception)
{
    $response = parent::render($request, $exception);

    if ($request->header('X-Inertia') && in_array($response->status(), [500, 503, 404, 403])) {
        return Inertia::render('Error', ['status' => $response->status()])
            ->toResponse($request)
            ->setStatusCode($response->status());
    }

    return $response;
}

Basically I decided it was an act of futility to try and figure out every possible exception that could get thrown. Instead, I just let Laravel generate the correct Response, and I use that decide whether I want to show an Inertia error page.

A corresponding error page component could look like this:

<template>
  <div>
    <h1>{{ title }}</h1>
    <div>{{ description }}</div>
  </div>
</template>

<script>
export default {
  props: {
    status: Number,
  },
  computed: {
    title() {
      return {
        503: '503: Service Unavailable',
        500: '500: Server Error',
        404: '404: Page Not Found',
        403: '404: Forbidden',
      }[this.status]
    },
    description() {
      return {
        503: 'Sorry, we are doing some maintenance. Please check back soon.',
        500: 'Whoops, something went wrong on our servers.',
        404: 'Sorry, the page you are looking for could not be found.',
        403: 'Sorry, you are forbidden from accessing this page.',
      }[this.status]
    },
  },
}
</script>

This gives developers tons of flexibility to create their own custom designed error pages.

I'm kind of happy with this as a final solution. I'm not sure this library needs to do anything more...although I'm still open to it.

[reinink]

Closing this, because I think the above solution is actually perfect. 👌

[kevnk]

I've implemented the solution outlined in the docs, but anytime I run into a 403, it's still showing laravel's stubbed 403 page... Any ideas why this might be happening?

[kevnk]

Never mind... 🤦 I was testing locally so I got rid of the !app()->environment(['local', 'testing']) condition and I can see everything now...

[cristian807]

Hello!

I have gotten an error when taking my app to production in a shared hosting (cpanel).

The error is that when I try to render a view, it does not render as such, but instead displays the data coming from the controller in a modal.

How can I solve this?

Thank you.