Lightweight layout on asynchronous loading

[Augen2203]

Hello, this corrects the following points:

• Speeds up screen loading by not rendering empty layouts, which are subsequently replaced by an async request.

• We no longer need to predefine properties in the query() method that are equal to those that we would use in asynchronously loaded layouts.

Previously, for example, this was necessary if we used the canSee() method, like so:

->canSee($this->query->get('user')->exists).

Example:

We have an asynchronous modal window to which we pass the user model through the asyncGetUser() method, in this modal window there is a layout with a form in which, depending on whether the user exists or not, we want to hide one of the fields through a function ->canSee($this->query->get('user')->exists).

We'll get an error because when the screen first loads, $this->query->get('user') will be null,
Therefore, as one of the options, we needed to predefine it in the query() method, thus:

public function query(User $user)
{
       return [
              'user' => $user
       ];
}

In my particular case, when I use a lot of async modals, this gave me some pluses, in terms of memory, the number of layouts loaded and speed.

[tabuna]

I think it's a good idea. But let's put it in a separate method:

protected function reparation(): array
{
    if (...) {
        return [];
    }

    return collect($this->layouts)->...;
}

What do you think about it?

[Augen2203]

Thank you.

Yes, this is a good idea, thanks to this, the logic will be simplified and the code will become more readable.

[Augen2203]

During testing, I found that if we use asynchronous form loading and subsequently receive an error related to validation in it, it will not be displayed to us, since our asynchronous layout will not initially be loaded when the screen loads.

This error will be eliminated by adding an additional check.

if ($this->asyncMethod && !$this->async && !Session::get('errors')) {...

But in this case, again the null related error I mentioned earlier may occur.

For example, if you use something like:

$this->query->get('user')->exists

in our layout, since in case of receiving a validation error, we return to the past logic of behavior