Algolia Scout (Laravel): fan out re-indexing across models with a custom event

Algolia Scout (Laravel): fan out re-indexing across models with a custom event

TL;DR

[Stack Overflow #37612058, accepted answer, 8 votes]: when several Laravel models feed Algolia indexes, Scout's per-model hooks dont fan out on their own. Create your own event and handler, override the model's search hooks to fire it, and register the handler in the listeners array so a change in one model re-indexes every affected model. Source context: Stack Overflow #37612058 (accepted answer, 8 votes): a Laravel developer using Algolia Scout across multiple models needs re-indexing whenever any of several models change.

Use this when you run into the situation in the title.

When not to use this skill: unrelated tasks. It covers only the procedure above.

Compatibility

The steps above apply to the commands named in them. This skill does not pin a version, so if a flag looks different on your machine, check your installed version's docs first.

Details

The accepted answer recommends adding your own event and handler: override the searchable hooks in the model classes, create a custom event object, and wire the listeners array so one change fans out to every model that needs re-indexing.

Question: Algolia Scout (Laravel): fan out re-indexing across models with a custom event Asked: Stack Overflow #37612058 (accepted answer, 8 votes): a Laravel developer using Algolia Scout across multiple models needs re-indexing whenever any of several models change. The accepted answer recommends adding your own event and handler: override the searchable hooks in the model classes, create a custom event object, and wire the listeners array so one change fans out to every model that needs re-indexing. Verified resolution: [Stack Overflow #37612058, accepted answer, 8 votes]: when several Laravel models feed Algolia indexes, Scout's per-model hooks dont fan out on their own. Create your own event and handler, override the model's search hooks to fire it, and register the handler in the listeners array so a change in one model re-indexes every affected model. Source: https://stackoverflow.com/questions/37612058