Week 072 — Item Saving Begins

The UI is wired. The save isn't working yet.

Week of April 6, 2026

Progress

The new API endpoint logic was started. The client-side code was updated to determine whether a save is a state transition (POST) or an item update (PATCH) based on whether the state has changed from what was loaded.

A sticky shrinking header was implemented — the header compresses as the user scrolls, giving more screen space to the item content. The welcome banner hides on scroll.

Tuesday and Wednesday were focused on identifying all the parts of the item page that should trigger the "something has changed" flag: reward amount, item name, image, QR code actions, state changes. All of these were connected to the save/cancel banner.

By end of week the update logic was partially wired but not functional — selectedState wasn't defined, which prevented the endpoint selection logic from running.

Next Week

Get a simple item property update to save successfully.