Regenerate the mammon API client for the endpoint-convention changes #15

Closed
opened 2026-07-08 22:29:25 +02:00 by Sirttas · 0 comments
Owner

Summary

mammon is reshaping its market/reprocessing HTTP surface (mammon #37, #38, #39, #40). Once those land, regenerate the OpenAPI spec + client here and fix the call sites so the app still builds and works.

docs/mammon-api.yml and src/generated/mammon/ are generated (openapi-generator) — do not hand-edit; regenerate from the updated mammon spec.

Backend changes to absorb

mammon issue Change Client impact
#40 POST /market/types/parse/market/types/paste parseStacks op path changes (no current caller in gemory, but the generated op updates)
#37 new POST /market/prices/paste (raw appraisal) new op appears
#38 GET /market/prices gains marketLocationId currentPrices signature grows an optional param
#39 normal reprocess becomes GET /reprocessing (items as typeId:quantity pairs); /reprocessing/raw/reprocessing/paste reprocess op(s) change shape/name

Call sites to fix

  • src/market/appraisal/mammon.ts:10marketApi.currentPrices(types.map(t => t.id)). Still compiles after #38 (new param is optional); no change needed unless we start passing a location (that's the compare page, separate issue).
  • src/reprocess/reprocess.ts:18reprocessingApi.reprocessRawItems(characterId, items, locationId). Re-point to whatever the regenerated op is called for POST /reprocessing/paste; confirm arg order after regen.
  • Grep for any parseStacks usage (none today) after regen in case the op rename surfaces one.

Acceptance criteria

  • docs/mammon-api.yml regenerated from the updated mammon backend.
  • src/generated/mammon/ regenerated (not hand-edited).
  • All call sites updated so npm run build (vue-tsc) passes.
  • Existing reprocess flow still works end-to-end against the renamed endpoint.
  • No leftover references to the old op names/paths (/parse, /raw, old reprocess POST).

Depends on

mammon #37 / #38 / #39 / #40 being merged first.

## Summary mammon is reshaping its market/reprocessing HTTP surface (mammon #37, #38, #39, #40). Once those land, regenerate the OpenAPI spec + client here and fix the call sites so the app still builds and works. `docs/mammon-api.yml` and `src/generated/mammon/` are generated (openapi-generator) — **do not hand-edit**; regenerate from the updated mammon spec. ## Backend changes to absorb | mammon issue | Change | Client impact | |--------------|--------|---------------| | #40 | `POST /market/types/parse` → `/market/types/paste` | `parseStacks` op path changes (no current caller in gemory, but the generated op updates) | | #37 | new `POST /market/prices/paste` (raw appraisal) | new op appears | | #38 | `GET /market/prices` gains `marketLocationId` | `currentPrices` signature grows an optional param | | #39 | normal reprocess becomes `GET /reprocessing` (items as `typeId:quantity` pairs); `/reprocessing/raw` → `/reprocessing/paste` | reprocess op(s) change shape/name | ## Call sites to fix - `src/market/appraisal/mammon.ts:10` — `marketApi.currentPrices(types.map(t => t.id))`. Still compiles after #38 (new param is optional); no change needed unless we start passing a location (that's the compare page, separate issue). - `src/reprocess/reprocess.ts:18` — `reprocessingApi.reprocessRawItems(characterId, items, locationId)`. Re-point to whatever the regenerated op is called for `POST /reprocessing/paste`; confirm arg order after regen. - Grep for any `parseStacks` usage (none today) after regen in case the op rename surfaces one. ## Acceptance criteria - [x] `docs/mammon-api.yml` regenerated from the updated mammon backend. - [x] `src/generated/mammon/` regenerated (not hand-edited). - [x] All call sites updated so `npm run build` (vue-tsc) passes. - [x] Existing reprocess flow still works end-to-end against the renamed endpoint. - [x] No leftover references to the old op names/paths (`/parse`, `/raw`, old reprocess POST). ## Depends on mammon #37 / #38 / #39 / #40 being merged first.
Sirttas added the item-comparison label 2026-07-08 22:36:47 +02:00
Sirttas added a new dependency 2026-07-08 22:43:33 +02:00
Sirttas referenced this issue from a commit 2026-07-09 17:30:31 +02:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Blocks Depends on
You do not have permission to read 4 dependencies
Reference: eveal/gemory#15