Add label printing functionality and error handling in stock and label flows

2026-04-10 22:08:01 +02:00
parent 1dc1bb4912
commit e1383c4d56
10 changed files with 627 additions and 21 deletions
@@ -177,6 +177,8 @@ Expected shapes today:
  Updates measured or descriptive stock state using `{ quantity }` or `{ level }`.
 - `POST /{database}/kitchen/items/{uuid_b64}/use`
  Marks an item used up (`gone`) via stock-event semantics.
+- `POST /{database}/kitchen/items/{uuid_b64}/print-label`
+  Prints label for an existing item; called from the save flow when `Print` is enabled.
 - `DELETE /{database}/kitchen/items/{uuid_b64}`
  Compatibility fallback when `/use` is not available on the backend.
 - `GET /{database}/kitchen/locations`
@@ -188,4 +190,4 @@ Expected shapes today:
 - Local storage only keeps non-sensitive app config, session payload, active kitchen, and label draft state.
 - Kitchen context now lives in the URL path instead of a custom header.
 - The API client now builds database-scoped kitchen routes by default; it always keeps bearer authentication handling separate from URL shaping.
- Label submit now uses upsert-first apply semantics; auto-print is intentionally deferred.
+- Label submit uses upsert-first apply semantics and an optional `Print` checkbox (default on for the current page session).