Org Web Adapter

hungryroot/jira/be_6889_remove_references_to_deprecated_foods_and_recipes_routes.org

ID
7086172d-3413-4bf9-ad74-2cc9371cc69c

BE-6889 Remove references to deprecated /foods and /recipes routes

- source :: https://hungryroot.atlassian.net/browse/BE-6889

- tags :: Hungryroot API Project

- epic :: EP-411 Eng Parking Lot

- sprint :: HR BE Sprint 102

- status :: Status - Needs QA

Tasks

DONE Ask Cursor to review usage of the legacy endpoints

apiv1workhungryrootep411be6889choresprint102
ID
3f4f9758-094a-952e-0828-30a2e9079d22

DONE Open a pull request for BE-6889

apiv1workhungryrootep411be6889choresprint102
ID
a3e881ee-dc1a-e75a-afce-517450845a9a

Description

The legacy /foods and /recipes routes are now permanently redirected (301) to

their corresponding new pages in Production. We should remove any remaining

references to these deprecated routes across the codebase to avoid unnecessary

redirects, reduce technical debt, and ensure all internal navigation and links

point directly to the new canonical pages.

Scope / Tasks

Identify and remove references to /foods and /recipes in:

Backend code (routes, serializers, redirects, constants)

Frontend code (links, navigation, config, hardcoded URLs)

Templates, emails, and notifications

Tests, fixtures, and mocks

Documentation and comments, where applicable

Replace with the appropriate new canonical URLs.

Verify no internal requests or links rely on the 301 redirects.

Confirm in production monitoring (e.g., logs or Datadog) that traffic to /foods

and /recipes is no longer originating from first-party code after changes are

deployed.

Acceptance Criteria

No first-party code references /foods or /recipes.

All internal links route directly to the new pages without triggering 301

redirects.

Tests pass and no regressions are introduced.

Post-deployment verification shows a reduction or elimination of internal

traffic to the deprecated routes.