api-contract: GET /image/:key path pattern does not match real storage key shape #6

New issue

Closed

opened 2026-09-20 05:57:46 +00:00 by araemer · 0 comments

araemer commented

2026-09-20 05:57:46 +00:00

Owner

api-contract/src/images.ts models GET /image/:key with a single dynamic path segment. The real storage keys are multi-segment (recipes/{recipeId}/{imageId}.{ext}), served via a wildcard route in recipe-backend's ImageRestResource.ts — the contract's path pattern is inaccurate.

Found during the recipe-backend/recipe-app contract-onboarding audit (recipe-backend PR #13, docs/plans/onboarding-integration.md → Audit Results). Not actioned there since it is a contract-side fix, not a backend one.

Fix: correct the path pattern in api-contract/src/images.ts to reflect the real multi-segment key shape.

`api-contract/src/images.ts` models `GET /image/:key` with a single dynamic path segment. The real storage keys are multi-segment (`recipes/{recipeId}/{imageId}.{ext}`), served via a wildcard route in `recipe-backend`'s `ImageRestResource.ts` — the contract's path pattern is inaccurate. Found during the `recipe-backend`/`recipe-app` contract-onboarding audit (`recipe-backend` PR #13, `docs/plans/onboarding-integration.md` → Audit Results). Not actioned there since it is a contract-side fix, not a backend one. **Fix:** correct the path pattern in `api-contract/src/images.ts` to reflect the real multi-segment key shape.

araemer referenced this issue from araemer/recipe-backend

2026-09-20 06:01:07 +00:00

Onboard recipe-backend onto @recipe/contract #13

araemer referenced this issue from a commit

2026-09-20 08:14:42 +00:00

fix(contract) Correct GET /image/:key to reflect the real wildcard path

araemer referenced this issue from a pull request that will close it,

2026-09-20 08:14:53 +00:00

fix(contract) Correct GET /image/:key to reflect the real wildcard path #12

araemer closed this issue

2026-09-26 05:00:17 +00:00