Add a Bar to a Venue
As a Host, I want to add a new bar to my venue, so that I can manage the different physical locations where I serve drinks within that venue.
Acceptance Criteria
Section titled “Acceptance Criteria”- Given I have an existing venue
- When I want to add a new bar to that venue
- Then I can provide the bar’s Name (e.g., “Main Bar”, “Kitchen Counter Bar”)
- And I can optionally provide a Description of the bar (e.g., “Main bar with full service”, “Small bar in the kitchen”)
- And I can optionally specify Features that describe the bar’s capabilities (e.g., “Full Service”, “Wine Bar”, “Coffee Station”)
- And the system records the bar within the venue
- And the new bar is immediately available for use in:
- Bar setups for events (bars can be inferred from event’s venue)
- Inventory location assignments
Implementation Status
Section titled “Implementation Status”✅ UI AND MOCK DATA IMPLEMENTED (December 2025)
Implementation Details
Section titled “Implementation Details”UI Components:
- Add bar form on venue detail screen with Name, Description, and Features fields
- Features input supports comma-separated values
- Features displayed as badges on bar cards
- Real-time UI updates after adding a bar
Data Layer:
- Bar type updated to include
features?: string[] addBarToVenue()function added to mock data layer- GraphQL mutation updated to include features field
Files Modified:
shaker/app/(tabs)/venues/[id].tsx- Venue detail screen with add bar functionalityshaker/data/venues/index.ts- Added Bar.features and addBarToVenue functionshaker/graphql/mutations/AddBar.graphql- Updated to include features
Next Steps:
- Integrate with GraphQL backend when
AddBarmutation is available - Replace mock data function call with actual GraphQL mutation
- Add error handling for backend failures
- ⚠️ Bar Setup Integration: Currently bar setups require manual bar name entry. Consider adding a bar picker to select from venue’s bars when creating bar setups. Note: Recipes don’t need bar assignment - menus are defined for events, and events occur at venues with bars, so the bar relationship is inferred.
Audit Status: See Add Bar Audit for detailed implementation review (January 2025)
Priority
Section titled “Priority”High - Foundation for venue and bar management
Related Entities
Section titled “Related Entities”- Venue (parent aggregate)
- Bar (entity with BarId, Name, Description, VenueId, Features)
Related Commands
Section titled “Related Commands”AddBar(C59) - Add a bar to an existing venue