Refine home recipe browsing and version ingredient seed data #27

Merged
wantxapas merged 11 commits from codex/refine-ui-across-features into main 2026-07-22 11:03:59 +01:00
wantxapas commented 2026-07-22 11:01:41 +01:00 (Migrated from github.com)

What changed

This branch combines two related streams of work:

  • versioned ingredient seed generation and backend loading changes
  • home recipe browsing refinements on the frontend

On the backend, it centralizes ingredient category handling, adds versioned ingredient seed generation, introduces the new ingredients.v2.json seed dataset, and updates the supporting tests and install-time seed loading paths.

On the frontend, it changes the home recipe list from page-by-page navigation to infinite scroll, adds recipe sorting controls for date and alphabetical order, and tightens the home action controls and dropdown behavior so the sort menu layers correctly above recipe cards.

Why it changed

The seed/versioning work makes ingredient data evolution explicit and easier to maintain over time.

The home page changes simplify browsing large recipe collections and make the primary list controls faster to use.

Impact

Users get a smoother recipe browsing experience on the home page with infinite scrolling and inline sorting.

Developers and operators get a clearer path for evolving seeded ingredient data without overwriting previous seed versions.

Root cause

The home page previously depended on explicit pagination controls and had no way to reorder recipes in place.

Ingredient seed data was previously less structured for versioned evolution, which made iterative changes harder to manage safely.

Validation

  • gofmt -w backend/main.go
  • go test ./... in backend/ currently fails, but the failures are not isolated to the final UI-only commits on this branch. Current failures include:
    • TestVerifyTranslatedRecipeOutput_FlagsMixedLanguageSteps
    • TestVerifyTranslatedRecipeOutput_FlagsFatalIngredientFidelityErrors
    • TestResolveIngredientIDTxAliasMatchDoesNotCreateDuplicate
    • TestResolveIngredientIDTxMultilingualAliasDoesNotCreateDuplicate
    • TestUnknownIngredientCanStillBeExplicitlyCreated
    • TestCreateIngredientNormalizesCategoryVocabulary
    • TestParseRecipeFromGoustoPayload_LabelDrivenIngredients
  • Frontend build verification was not run in this environment because npm/installed frontend dependencies were unavailable.

Notes

This branch is currently behind main by 3 commits and ahead by 11 commits, so GitHub may require a merge/rebase before final merge.

## What changed This branch combines two related streams of work: - versioned ingredient seed generation and backend loading changes - home recipe browsing refinements on the frontend On the backend, it centralizes ingredient category handling, adds versioned ingredient seed generation, introduces the new `ingredients.v2.json` seed dataset, and updates the supporting tests and install-time seed loading paths. On the frontend, it changes the home recipe list from page-by-page navigation to infinite scroll, adds recipe sorting controls for date and alphabetical order, and tightens the home action controls and dropdown behavior so the sort menu layers correctly above recipe cards. ## Why it changed The seed/versioning work makes ingredient data evolution explicit and easier to maintain over time. The home page changes simplify browsing large recipe collections and make the primary list controls faster to use. ## Impact Users get a smoother recipe browsing experience on the home page with infinite scrolling and inline sorting. Developers and operators get a clearer path for evolving seeded ingredient data without overwriting previous seed versions. ## Root cause The home page previously depended on explicit pagination controls and had no way to reorder recipes in place. Ingredient seed data was previously less structured for versioned evolution, which made iterative changes harder to manage safely. ## Validation - `gofmt -w backend/main.go` - `go test ./...` in `backend/` currently fails, but the failures are not isolated to the final UI-only commits on this branch. Current failures include: - `TestVerifyTranslatedRecipeOutput_FlagsMixedLanguageSteps` - `TestVerifyTranslatedRecipeOutput_FlagsFatalIngredientFidelityErrors` - `TestResolveIngredientIDTxAliasMatchDoesNotCreateDuplicate` - `TestResolveIngredientIDTxMultilingualAliasDoesNotCreateDuplicate` - `TestUnknownIngredientCanStillBeExplicitlyCreated` - `TestCreateIngredientNormalizesCategoryVocabulary` - `TestParseRecipeFromGoustoPayload_LabelDrivenIngredients` - Frontend build verification was not run in this environment because `npm`/installed frontend dependencies were unavailable. ## Notes This branch is currently behind `main` by 3 commits and ahead by 11 commits, so GitHub may require a merge/rebase before final merge.
Sign in to join this conversation.
No description provided.