v0.6.0

Automatic redirects

Since returning a Redirect::back() response is such a common pattern within an Inertia app, this adapter now does this automatically for you when no response is returned from a controller (#350).

For example, consider this teams controller which redirects back to the previous page after updating a team. With this new feature you can now omit the Redirect::back() response and it will happen automatically.

class TeamsController extends Controller
{
    public function update(Team $team)
    {
        $team->update(/* ... */);
-
-       return Redirect::back();
    }
}

You can disable this behavior, or even do something entirely different, by adding an onEmptyResponse method to your HandleInertiaRequests middleware:

use Illuminate\Http\Request;
use Symfony\Component\HttpFoundation\Response;

/**
 * Determines what to do when an Inertia action returned with no response.
 * By default, we'll redirect the user back to where they came from.
 *
 * @param  Request  $request
 * @param  Response  $response
 * @return Response
 */
public function onEmptyResponse(Request $request, Response $response): Response
{
    // Use the default Laravel "empty" response
    return $response;
}

Fixed

• Fixed namespace issue with Route::inertia() method (#368)
• Added session check when sharing validation errors (#380)
• Fixed docblock on facade render method (#387)

v0.5.4

Find release notes here.

v0.5.3

Find release notes here.

v0.5.2

Find release notes here.

v0.5.1

Find release notes here.

v0.5.0

Find release notes here.

v0.4.5

Find release notes here.

v0.4.4

Find release notes here.

v0.4.3

Find release notes here.

v0.4.2

Find release notes here.