Fix/59 fridge recipe matches #60
Merged
+1,392
−57
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
Add indexed PostgreSQL search with fuzzy matching and ingredient aliases. Support debounced suggestions, caching, keyboard navigation and error feedback. Test matching, index usage and catalog refresh with 50,000 synthetic entries. Closes #55
davidhne
approved these changes
Oct 15, 2026
davidhne
pushed a commit
that referenced
this pull request
Oct 15, 2026
Replaces frontend/src/mocks/recipes.ts with Apollo Client queries against the backend, so search, category/rating filtering, sorting and "Load more" paging all run server-side over the whole dataset, as required. - Apollo Client chosen as the GraphQL client; its cache also satisfies the assignment's state-management requirement for server data (Zustand, merged separately via #60, covers local Fridge UI state) - Vite dev proxy for /project2/graphql mirrors the Apache proxy in production, and honors VITE_GRAPHQL_URL like IngredientSearch.tsx does - Fixed a real bug found while wiring this up: RecipeFilter's category values were lowercase ("beef"), but the server does a case-sensitive array-contains match against Title Case data ("Beef") - every category filter would have silently returned zero results - "My Fridge" ingredient matching still happens client-side on the loaded page only; the backend has no ingredient filter yet (follow-up issue). The any-ingredient-matches semantics and "Back to Fridge" link are from #60, rebased on top of here together with their HomePage/test changes - Loading and error states, aria-live reads the server's totalCount Closes #58 AI usage: Claude Code wrote the implementation and tests in this commit, driven by a reviewed plan; manually verified end-to-end in a browser against a local backend/Postgres with the real dataset (search, category filter, pagination, detail page, Fridge flow), both before and after rebasing onto #60's merged ingredient-autocomplete/Fridge-persistence work. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
This was referenced Oct 15, 2026
Sign in
to join this conversation on GitHub.
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.
Closes #55
Closes #57
Closes #59
What and why
How to test
npm run ingredients:refreshagainst an existing recipe database.tomatoein My Fridge and selecttomato.Validation: 40 frontend tests pass, including matching and persistence tests. Database tests cover fuzzy matching and index usage with 50,000 synthetic entries. Lint, typecheck, formatting and production build pass.
Screenshots: not attached.
AI usage
AI assisted with implementation, documentation and automated tests. Manual code review and browser verification remain before merge.
Checklist