Partial Reloads no longer work as documented in Inertia 2.0 - Unlisted breaking change

[ncphillips]

We have some pages that do partial reloads so we don't unmount certain parts of our UI.

For example, courses have many assignments. If we're switching from assignment to assignment we want to avoid reloading the course data.

function show($courseId, $assignmentId)
{
    return inertia('Assignment/Show', [
        'course' => fn() => Course::find($courseId),
        'assignment' => Assignment::find($assignmentId),
    ]);
}

In the Assignment/Show template we have a link using Ziggy:

<Link :href="route('courses.assignments.edit', { course: course.id, assignment: assignment.id })>Edit</Edit>

According to the docs course will always be sent on first request, but if the only prop is sent than it would be left out.

This works in Inertia 1.0

With the upgrade to 2.0 this stops working. Ziggy explodes telling me that course is undefined.

When I log out props.course then I see that the course is an empty proxy:

It seems to me like Inertia is now treating:

'course' => fn() => Course::find($courseId)

like this

'course' => Inertia::lazy(fn () => Course::find($courseId))

It's not the end of the world, but is a bit annoying.

[michaelklopf]

I have discovered the same behaviour, that fn() behaves like lazy. Is this a bug or the docs wrong?

[ncphillips]

I have no idea. Would love to hear from @joetannenbaum. We're super excited for Inertia 2.0 and we could get a ton of benefit, but with this still being an issue we're not quite willing to take the chance.

[ncphillips]

I think this issue might be resolved now. Still testing. @michaelklopf do you have any updates?

@joetannenbaum any recollection on this getting addressed?

[pascalbaljet]

I've rechecked your issue and it works fine with the latest version of the adapter. It’s probably fixed in #706, but I'm not 100% sure.

[michaelklopf]

@ncphillips
It appears to be fixed 🥇