EventRepository
Component Detail
Data Layer
medium complexity
backend
0
Dependencies
0
Dependents
1
Entities
0
Integrations
Description
Data access layer responsible for persisting and retrieving event records from the database. Provides CRUD operations scoped to the events entity. Abstracts storage details from the service layer.
event-repository
Sources & reasoning
Line 297 defines the exact wizard structure for event creation and line 289 places it as a primary entry point in bottom-nav. The blueprint marks this MVP. The mobile architecture section treats event wizards as a core screen alongside activity wizards, confirming launch-critical status.
-
docs/source/likeperson.md · line 297Event wizard (multi-step: title → date → time → duration → location → summary)
-
docs/source/likeperson.md · line 289Bottom nav with 5 tabs: Home, Contacts, Add (modal launcher for Activity and Event wizards), Work, Notifications
Responsibilities
- Insert new event records with all wizard-collected fields
- Retrieve individual event records by ID
- Update existing event records when edits are made
- Delete event records as required by business operations
Interfaces
create(data: EventCreateInput): Promise<Event>
findById(eventId: string): Promise<Event | null>
update(eventId: string, data: Partial<EventCreateInput>): Promise<Event>
delete(eventId: string): Promise<void>