▸case-01 Can you write a Next.js App Router page component for our e-commerce product search? We need a search input box, product result hits, and sidebar filters for category and brand. Make sure it supports server-side rendering so initial search results hydrate cleanly without UI mismatches. | fail→pass | 28,782 | 20,284 | -30% | 1 | 1 | 0% | 6,150 | 9,579 | +56% | 0 | 0 | — |
▸case-02 I need a TypeScript module for our backend service to push product data to our search index. Provide helper functions to chunk large product lists for bulk uploading, a function for incremental updates to product stock or price, and a safe zero-downtime method to completely rebuild the index without disrupting live user searches. | fail→pass | 29,929 | 21,507 | -28% | 1 | 1 | 0% | 6,090 | 10,761 | +77% | 0 | 0 | — |
▸case-03 We are building a React search header component where bundle size is critical. How should we instantiate the Algolia client on the client-side to keep bundle overhead minimal, and which API key type should be passed to it? | pass→pass | 12,362 | 7,150 | -42% | 1 | 1 | 0% | 2,127 | 7,935 | +273% | 0 | 0 | — |
▸case-04 Our multi-tenant application requires filtering search results per user on the server before handing a token to the React frontend. How should we securely construct a temporary user-scoped key using the Node server SDK so users cannot alter search filters? | fail→fail | 16,846 | 16,971 | +1% | 1 | 1 | 0% | 3,022 | 9,787 | +224% | 0 | 0 | — |
▸case-05 We want to expose a public search endpoint for our open catalog without allowing scrapers to exhaust our query quota. How can we programmatically create an API key via the backend SDK with IP-based rate limiting and domain restrictions? | fail→pass | 16,202 | 11,157 | -31% | 1 | 1 | 0% | 2,744 | 8,493 | +210% | 0 | 0 | — |
▸case-06 Our search index is returning matches in product descriptions ahead of exact matches in product titles. How should we configure attribute search priority in the index settings script so titles take top precedence over secondary details? | pass→pass | 11,992 | 13,027 | +9% | 1 | 1 | 0% | 1,938 | 8,720 | +350% | 0 | 0 | — |
▸case-07 Text relevance alone is returning obscure out-of-stock items at the top of results. How should we configure index settings so tie-breaking prioritizes popular and highly-rated products? | pass→pass | 19,090 | 14,139 | -26% | 1 | 1 | 0% | 3,141 | 9,005 | +187% | 0 | 0 | — |
▸case-08 We added a brand checkbox filter to our InstantSearch UI, but the facet counts aren't returning from the backend search API. What configuration step in the index settings script is required to enable filtering and faceting on attributes? | pass→pass | 6,976 | 5,124 | -27% | 1 | 1 | 0% | 1,175 | 7,509 | +539% | 0 | 0 | — |
▸case-14 We want to allow users to sort search results by price low-to-high and price high-to-low using InstantSearch. How is dynamic sorting configured between InstantSearch widgets and index settings? | pass→pass | 12,726 | 10,461 | -18% | 1 | 1 | 0% | 2,319 | 8,584 | +270% | 0 | 0 | — |
▸case-09 We have internal backend attributes like inStock status that we filter on, but we never render them as visible facet refinement lists to users. How should we declare this attribute in index settings to optimize facet calculation overhead? | pass→pass | 10,925 | 8,262 | -24% | 1 | 1 | 0% | 1,655 | 7,935 | +379% | 0 | 0 | — |
▸case-10 During full catalog reindexing, we want to copy index settings, synonyms, and query rules to a temporary index before swapping. What parameters should be passed to the copy method to ensure non-record configurations migrate intact? | pass→pass | 8,088 | 10,486 | +30% | 1 | 1 | 0% | 1,373 | 8,464 | +516% | 0 | 0 | — |
▸case-11 We need to remove 500 discontinued items from our index in a night job. Our junior developer proposed using query-based deleteBy. Is this advisable, or what method should be used instead for bulk primary key deletion? | fail→pass | 14,434 | 10,114 | -30% | 1 | 1 | 0% | 2,267 | 8,362 | +269% | 0 | 0 | — |
▸case-12 We want to build a standalone search input modal in vanilla TypeScript/React that displays search query suggestions from a dedicated index alongside instant product hits. Which official Algolia packages and helper functions should be wired up? | pass→pass | 15,600 | 12,521 | -20% | 1 | 1 | 0% | 2,814 | 8,983 | +219% | 0 | 0 | — |
▸case-13 When a user views a product, we want to increment its viewCount attribute in the search index without fetching the current count or overwriting other attributes. How should the partial update payload be structured? | pass→pass | 10,791 | 5,764 | -47% | 1 | 1 | 0% | 1,822 | 7,628 | +319% | 0 | 0 | — |
▸case-15 Our recency sorting is failing because products indexed with ISO 8601 date strings ('2024-03-15T10:00:00Z') do not sort chronologically in custom ranking. How should dates be formatted in record payloads for numerical sorting? | pass→pass | 10,153 | 7,215 | -29% | 1 | 1 | 0% | 1,858 | 7,894 | +325% | 0 | 0 | — |
▸case-16 We need to build a custom React search UI without pre-styled InstantSearch UI widgets. Which hooks provided by React InstantSearch give direct access to search query input, results array, and network loading status? | pass→pass | 8,027 | 6,669 | -17% | 1 | 1 | 0% | 1,745 | 7,985 | +358% | 0 | 0 | — |
▸case-17 Users making typos on short 3-letter queries are getting unexpected zero-result pages, while long queries trigger too many loose matches. How do we configure word length thresholds for 1 and 2 typos in index settings? | pass→pass | 14,599 | 9,280 | -36% | 1 | 1 | 0% | 2,591 | 8,303 | +220% | 0 | 0 | — |
▸case-18 Our clothing search results display 10 color variants of the exact same shirt model. How should we configure index settings to group variants by family and show only one canonical result per product family? | pass→pass | 13,807 | 12,316 | -11% | 1 | 1 | 0% | 2,478 | 8,887 | +259% | 0 | 0 | — |
▸case-19 We want to set up automated search equivalence so searching for 'phone' matches 'mobile' and 'smartphone', and a query containing 'sale' automatically applies a filter for discounted items. Which index management API calls achieve this? | fail→pass | 11,371 | 9,621 | -15% | 1 | 1 | 0% | 2,126 | 8,505 | +300% | 0 | 0 | — |
▸case-20 Our Next.js search page is serving stale search results because Next.js aggressively cached the server component render. What route segment configuration directive must be exported from the page module to force fresh server rendering? | pass→pass | 3,007 | 3,553 | +18% | 1 | 1 | 0% | 561 | 7,284 | +1198% | 0 | 0 | — |
▸case-21 We want to implement full-text search directly inside our existing PostgreSQL database without using external cloud search providers. How do we set up a generated tsvector column with a GIN index on our products table and query it in SQL? | fail→fail | 13,040 | 12,377 | -5% | 1 | 1 | 0% | 2,444 | 8,950 | +266% | 0 | 0 | — |
▸case-22 We have a small static list of 50 FAQ items in our React application. We want to perform light client-side fuzzy search entirely in-memory in the browser without any API calls or backend indexing services. How do we set up Fuse.js for this? | pass→pass | 12,966 | 10,448 | -19% | 1 | 1 | 0% | 2,552 | 8,792 | +245% | 0 | 0 | — |
▸case-23 Our enterprise analytics pipeline stores log data in Elasticsearch. We need a Node.js function using @elastic/elasticsearch client to perform a boolean multi-match query filtering by status code and matching error message strings. How should the search payload be structured? | pass→pass | 15,250 | 11,846 | -22% | 1 | 1 | 0% | 3,044 | 8,949 | +194% | 0 | 0 | — |