Ensure result of Data hydration is handleable by the Cascade

[marcorieser]

Fixes: #26

[jonathan-bird]

@marcorieser The ?? collect() fix prevents the crash, but it changes the behavior compared to the initial page load. On a normal Route::statamic() request, FrontendController::route() passes null to cascadeContent(), the Cascade's null guard returns early, and page never gets set. With this fix, Livewire updates would set page to an empty collection instead.

A more consistent fix would be to resolve the content eagerly and skip withContent() when there's nothing:

protected function hydrateContent(): void
{
    $content = Data::findByRequestUrl(Livewire::originalUrl());

    if ($content) {
        Cascade::withContent($content);
    }
}

This matches exactly what happens on the initial page load - when there's no content entry for the URL, the Cascade just doesn't get content set at all.

[marcorieser]

@jonathan-bird Yeah, I see that, but I don't want to hydrate the content if the Cascade is not used in the request. Need to think about it for a bit.

Once Jason merged this PR (statamic/cms#14502), I can remove ?? collect() and your case should be fixed, right?

[jonathan-bird]

@marcorieser Yeah I believe so, solves it further up the chain which is even better.