[10.x] searchableSync / unsearchableSync #920
Merged
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.
In my projects, I always configure Scout to queue the jobs that make model(s) searchable or unsearchable. This works perfectly, but sometimes you want to make a model instantly unsearchable.
For example, in a project, I show a list that is based on a Scout search result. Each item has a delete button. Deleting an item and refreshing the list will mean the refreshed list has a high change of still containing the deleted item if the job that makes the item unsearchable has not finished yet.
This PR adds methods to easily make model(s) synchronously searchable/unsearchable even if Scout config will queue those actions by default.
The 'Sync' suffix for the method names is inspired by the 'dispatchSync' method on jobs in Laravel.