Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Libraries] [Collections] [Backend] store component-collection association in Studio Library Index #230

Closed
Tracked by #1084
bradenmacdonald opened this issue Jul 31, 2024 · 1 comment

Comments

@bradenmacdonald
Copy link
Contributor

bradenmacdonald commented Jul 31, 2024

This step implements the different moving parts of updating Collections data to Library Component documents in Meilisearch. To do that we need to:

  • Extend the search Fields class to include collections
  • Since there can be multiple collections, that field would be an array
  • Add an upsert_block_collections_index_docs function updates the collections data in documents for the given library block (similar to upsert_block_tags_index_docs)
  • Rename existing event CONTENT_OBJECT_TAGS_CHANGED to CONTENT_OBJECT_ASSOCIATIONS_CHANGED and add a data field to indicate which associations have changed (tags or collections).
    This event fires when the library component/object’s tags or collections change, and hence would call the new upsert function to update the tags and/or collections in the documents in meilisearch

Added to this issue:

@pomegranited
Copy link

Backend changes have been deployed to the sandbox; nothing to AC test here :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

2 participants