v3 - Is it normal for RelationManagers not to be initialized until they are visible on the viewport?

[emcarson]

Hello everyone,

I upgraded to v3 but now I'm having lot's of trouble with refreshing my Relation Managers.

If I update a record and the RelationManager is visible (ie: if I scrolled down enough for it to "initialize" I have no problems whatsoever).
But If I scroll just enough to reach the submit button but the RelationManager is not yet visible I get the following error:

"Filament\Resources\RelationManagers\RelationManager::$table must not be accessed before initialization"

Same happens If I trigger a custom action from the header of the View Page.

Anyone experienced something similar?

Thank you.

PS: Here is my code:

<?php

namespace App\Filament\Resources\OrderResource\Pages;

use App\Filament\Resources\OrderResource;
use Filament\Resources\Pages\EditRecord;

class EditOrder extends EditRecord
{
    protected static string $resource = OrderResource::class;

    protected function afterSave()
    {
        $this->dispatch('recordUpdated');
    }
}

<?php

namespace App\Filament\Resources\OrderResource\RelationManagers\InvoicesRelationManager;

use Filament\Resources\RelationManagers\RelationManager;

class InvoicesRelationManager extends RelationManager
{
    protected $listeners = [
        'recordUpdated' => '$refresh',
    ];
}

[emcarson]

I'm such an idiot, it's right there in the documentation:
https://filamentphp.com/docs/3.x/panels/resources/relation-managers#disabling-lazy-loading

protected static bool $isLazy = false;

[Stichoza]

Is there any other kind of fix for this except disabling lazy loading?