Search graceful api framework fallback#401
Merged
Merged
Conversation
When a query names a framework/version, we route on it (framework filter in transformItems, version facet rewrite) but previously left the token in the query text sent to Algolia. That platform word skewed textual relevance - e.g. "barcode capture flutter" lifted /sdks/flutter/agent-skills/ (which lists frameworks) above /sdks/flutter/barcode-capture/get-started/. Strip the detected framework tokens (and the version marker when it routes) from the query text only. Routing is unchanged - it's still derived from the original query (latestQueryRef and versionTagInQuery both read the original); only the text Algolia scores against differs, so the product's main guide surfaces instead of a framework-listing page. Keep the original query if the strip would empty it (e.g. a lone "ios"). Verified before/after on the framework/version query set: get-started and product intro pages now rank first where framework-listing / release-notes pages did before. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The docs-search widget filtered API-reference results to a single framework (the page's framework, or a hard "web" fallback on framework-less pages) to avoid spamming the user with the same symbol across every SDK. But native-only API symbols (Barcode Selection, Barcode Count, etc.) have no Web SDK page, so the web-only fallback returned zero results even though the symbol exists for 7-8 other frameworks. Replace the hard "web" fallback with a per-symbol graceful degradation: prefer web, else the next framework in a fixed priority order that actually has the page. Still exactly one hit per symbol (no cross-framework duplicates), but never empty when the symbol exists somewhere. The results footer now names the framework actually shown instead of a hardcoded "web". Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
lucatorella
approved these changes
Jul 21, 2026
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
2 participants
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.
No description provided.