Repository navigation
feat(search): index registry discovery metadata - #164
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Related: fontsource/fontsource#1251.
Overview
Search records currently expose only legacy categories and subsets. Enrich the existing Algolia index with registry classifications, curated tags, and exact language IDs while preserving current font IDs and legacy fields.
Before deploying the website PR:
prod_NAMEand its existing sort replicas (prod_POPULAR,prod_NEWEST,prod_RANDOM), append ordinary facetsclassifications,tags, andlanguageIds. Preserve existing facets, ranking, rules, synonyms, and replica relationships.family,displayName,designer,classificationLabels,tagLabels, followed by any other existing searchable fields needed for compatibility.main, and verify the new fields and filters across all sort indexes before deploying the website.The writer uses the latest successfully archived registry revision. Algolia enforces the account's record limits; a rejected batch fails the workflow, but earlier batches may already have succeeded. Updates remain additive and do not delete out-of-source records.