MailEclipse drops Meilisearch/Laravel scout records

[vanrijs]

Describe the bug

Hi all,

Installed MailEclipse last week now I noticed that is drops my Meilisearch/Laravel scout index files.
Only loading MailEclipse drops the indexes to im 100% sure it has something to do with this.

Any ideas?

Reproduction steps

Steps to reproduce the behavior:

1. Go to /maileclipse
2. View your Meilisearch/Laravel Scout index files, they are empty

Laravel Version:

8.77

MailEclipse package version:

v3.5.3

[ReeceM]

Hi @vanrijs

Sorry to hear that the package is doing this, it clearly shouldn't be affecting other packages.

The only thing this sounds like is a possibility is that it is clearing db data for the mocking information.

If I could ask, could you do the following to establish where the bug is:

Use the maileclipse config and disable the usage of factories.

In all the mail ales, remove type hints to eloquent orm models. (It should be replaced with a dynamic object which will still show calls)

Generate your indexes

The visit the page again and please let me know what happens

[vanrijs]

Thanks @ReeceM. Im doing some tests now.
Disabled factory option but no results.
I model binded this:
public function __construct(Contract $contract) and this keeps dropping my records.
Removed this bind now and doing some additional tests. More in a few hours from now :)

[ReeceM]

Thank you, please keep me updated on what happens

[vanrijs]

Hi @ReeceM. It has to do with the model bind.
My code now looks like this:

public function __construct($contract)
    {

        // model is already passed: its coming from an event listener
        if($contract instanceof Contract) {
            $this->contract = $contract;
        } else {
            $this->contract = Contract::with('responsible')->find(99475); // for editing mode, get fixed contract
        }

        $this->responsible = $this->contract->responsible;
    }

Don't have time now to do more research on what's going on exactly but my indexes keep intact now..

[ReeceM]

Hi there @vanrijs,

So I would think that there would be a side effect from the package that when it creates a model using the factory. I am not sure if the scout package has a cascade side effect that drops data when the model is deleted as that is what the pacakge does after a factory is made...

What I'll have to do is to look though the other package to see what might be happening.

[ReeceM]

So I may have to give this a bit of thought to get an idea of what to do.

Looking at the code there is a ModelObserver in the scout package that watches for deletes. Then clears out the index for that model. I suspect that if you are loading relations and other things like that it is possibly dropping those indexed details.

Do you think that it is possible to spin up a simple repository to create a reproduction of this issue?