Repository navigation
Store Resource APIs #5
Description
The most important operations are their retrieval and listing.
Will support POST, GET, LIST, PATCH, DELETE.
See more: https://docs.google.com/document/d/1HnRcB2SaG4f4QodOaaYZT4r4GYhibqBzA8wdl2zpID0?tab=t.h8qwaqvashle
Metadata
Metadata
Assignees
Labels
Type
Projects
- Status
Activity
[-]Store Resources APIs[/-][+]Store Resource APIs[/+]petrubraha commentedon Mar 7, 2026
Why is this necessary?
To deliver the MVP functionality, specifically solving the TSP problem, we must follow the defined user stories. These indicate that a client first selects the store they want to shop in, then chooses the products, and finally generates the shopping itinerary.
Therefore, these APIs are required to allow clients to list available stores and retrieve store details.
Why is this high priority?
The store is a foundational resource for several other entities, including floors, offers, and stands. During MVP development, the focus will be on implementing stands first, followed by floors. Since stands play a key role in the second step of generating the TSP solution, enabling store-related functionality early is essential.