[6.0] Don't add soft delete query filter on hard delete models #321
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently, when the static
search
method from theSearchable
trait is called, a new scout query builder is instantiated and the$softDelete
flag is based only onconfig('scout.soft_delete')
.The builder should only apply soft deletes if the model that is being searched also uses them.
It seems that Algolia ignores the additional
__soft_delete
filter when it it passed in a search that doesn't use soft deletes, but other drivers have to go out of the way to fix this deficiency ( See this section in the tnt search driver as an example )This pull request fixes the searchable trait to only apply the soft delete filter when the model being searched actually uses soft deletes.