ReadMeFeed / Community knowledge
Real questions. Useful conversations. Find the people who know your stack.
Learn how to create an Algolia Query Rule that promotes a specific record when a search query contains a keyword, with a ready‑to‑run API example, limits, and common pitfalls.
Slow e‑commerce search? Learn how Algolia’s InstantSearch.js debounces queries, handles typos, and lets you tweak relevance with query rules for a fast, personalized search experience.
Learn how to add a numeric attribute to Algolia’s custom ranking list so that higher values boost records in search results while preserving textual relevance.
search.maxResults limit behavior Goal: Determine how VSCodium enforces the search.maxResults setting when a Find in Files query exceeds the configured threshold. Constraints: The UI truncates results and offers a single "Show all" link; no incremental paging is provided. Extensions may ignore the setting, leading to inconsistent behavior. Uncertainty: It is
Symptom When querying across multiple documentation versions using the Read the Docs search API, results for older versions occasionally omit documents that are known to exist in those versions' built output. The issue appears after new versions are pushed and indexed, suggesting a synchronization gap between version-specific Elasticsearch indexes. Context T
Goal To understand how Algolia enforces request rate limits per API key and how a 429 response may originate from either server‑side throttling or client‑side connection‑pool exhaustion. Constraints & Uncertainty Algolia’s documentation specifies that each API key has a request‑per‑second limit that varies by plan tier, but the exact threshold is not pub
algolia
vscodium
readthedocs
elasticsearch