Harkamal Randhawa
dec0986830
- FIXED: ChatService now uses customer.customerId instead of users.id for CUSTOMER role - getConversations(): Resolve Customer entity to get customerId for filtering - getConversation(): Verify ownership using customer.customerId - sendMessage(): Updated signature to accept role parameter for staff assignment logic - getMessages(): Verify conversation ownership using customer.customerId - ChatController: Updated sendMessage call to pass user.getRole() This fixes the domain bug where conversation.customerId (references customer table) was being incorrectly populated with users.id instead of customer.customerId. Phase 3B