Overwriting Delete logic

[HiradRoshandel]

My Algolia ObjectId is modified and not equal to primary key of my model. As a result when I call delete on my object Scout doesn't remove it from algolia. Is there a way to overwrite the delete logic, something similar to toSearchableArray.

[julienbourdeau]

Can you share what your ObjectId look like and why you modified it?

[HiradRoshandel]

@julienbourdeau My Laravel model's primary key is id which is an integer but because I needed my frontend to be able to filter on a unique field, I had to change the Algolia ObjectID to that unique field.
Imagine this example:

User{
id,
name
email
}

Algolia User 
{
objectID: email
name
}

I didn't want to mark that field as a facet because it has a unique value so I had to change the objectID since Algolia allows you to filter on ObjectID. If there was a way to overwrite the delete logic I could define the ObjectID value.

Right now as a hack I'm using Algolia SDK to manually delete that object from my index.

[julienbourdeau]

I think the easiest way is to create a custom driver (and extend the AlgoliaEngine).
https://www.algolia.com/doc/api-client/laravel/extending-scout#extending-algolias-driver