"As a course author, I always want search results to be up to date"
Building on #195.
Requirements:
When a new component/section/etc. is created, it should be added to the search index automatically.
When a component (in a course) is edited in Studio, its entry in the search index should be updated automatically.
When a course, section, subsection, unit, or parent block (e.g. library content block, split test block) is renamed, its entry in the search index should be updated automatically, and the location/breadcrumbs field of all child blocks should be updated automatically.
When something (component/subsection/etc) is moved to another place in the course, all relevant breadcrumbs should be updated.
If the "reindex all courses/libraries" command is currently running, make sure it doesn't undo these changes. (The changes should either (A) be applied to the new index [perhaps in addition to the old/current index] or (B) be queued until after the reindex is complete.)
Publishing content has no effect; this entire index and story refers only to 'draft' content (what authors see in Studio).
Ideally:
These things will happen asynchronously.
If the search engine (e.g. Meilisearch) is offline/down at the moment the change is made, the update will be queued; once the search engine is back online, the index will be updated. (Note there are at least two ways to do this: one is by maintaining a queue of updates and writing them to the index when you can; the other is maintaining a list of "blocks that need updating" and regularly queuing a task to work through the list)
The same code can be used to keep (v2) library blocks up to date in the index (only do it as part of this PR if easy and quick).
"As a course author, I always want search results to be up to date"
Building on #195.
Requirements:
Ideally: