Validation errors are not passed as props

[iamohd-zz]

Validation errors are not passed as props

[bonzai]

Inertia doesn't automatically include validation errors, but you can use Inertia::share() method in your service provider to add them to your response:

Inertia::share([
    'errors' => function () {
        return Session::get('errors')
            ? Session::get('errors')->getBag('default')->getMessages()
            : (object) [];
]);

• https://github.com/inertiajs/pingcrm/blob/master/app/Providers/AppServiceProvider.php#L59-L62

[reinink]

Hello @mohd-isa! Thanks for your interest in Inertia. I think you will find this response I gave on Twitter helpful regarding error handling. 👍

Question:

So how do you handle a 422 response in Inertia when you're posting data? Do I need to add a custom header so inertia knows how to catch failed validation? Thanks for your feedback

Answer:

Great question! The trick is to not think of Inertia like a client-side framework, but rather a server-side framework.

So, with a client-side framework you'd catch the errors client-side, which would include some JSON error messages, and you'd update your view to show them.

With Inertia, you handle it like a server-side form submission.

You submit your form (POST). If there are errors, your server-side framework redirects back (GET) to your form page, and includes the errors in the session.

Then, you need to send those error messages to the view. Laravel automatically makes them available within the Blade views as $errors. However, we're not using Blade. So, we need to include the errors with our Inertia response, so they can be passed back to our page as a prop.

In my apps, I do this automatically on every request. If there are errors in the session, I include them as an errors prop.

You can see this here: https://github.com/inertiajs/pingcrm/blob/master/app/Providers/AppServiceProvider.php#L48-L50

This makes it work a lot like Blade, which always has access to the $errors object.

Your form page component has now received updated props, which include the errors prop, also accessible as $page.errors in Vue.js. Since Vue.js/React are reactive, the page will automatically update to show the form errors.

See here: https://github.com/inertiajs/pingcrm/blob/master/resources/js/Pages/Users/Create.vue#L10-L14

So, in summary:

1. Submit form via $inertia.post
2. If errors, server-side redirect back (GET) to form page
3. The errors are saved in the session
4. Errors are passed as shared data to Vue.js
5. Your page displays those errors, which happens reactively

This certainly requires a shift in thinking about things, but this whole approach works REALLY well.

It's just like how we used to do classic server-side form submissions. Except it's way nicer than that, since you're not reloading the whole page, or rehydrating form input.