Conversation
Remove redundant non-sparse index on user email field that prevented multiple guest users (who have no email) from being created. The sparse unique index from unique+sparse is sufficient. Also improve E11000 error handling in joinEventAsUser and joinEventAsGuest to distinguish between duplicate name vs duplicate email errors instead of assuming all duplicates are name conflicts.
- API_REFERENCE.md: Complete endpoint reference for all 20 implemented routes with request/response shapes, error codes, and curl quick-start examples - REALTIME_EVENTS_GUIDE.md: Pusher integration guide with client setup, channel naming, event payloads, and React/React Native code examples - DATABASE_SCHEMA.md: Schema reference for all 6 collections with field tables, indexes, pre-save hooks, and relationship diagram - EVENT_LIFECYCLE.md: Current state behavior and planned state machine with transitions and side effects
- Add table of contents to all 4 documentation files - Add quick-reference endpoint summary table to API_REFERENCE.md - Document the response format inconsistency across controllers with recommended client-side handling pattern
…e-email-index Fix guest join 409 error caused by duplicate email index
- Add gameType (enum: 'Name Bingo', required) and eventImg (optional) to Event schema
- Change currentState from free-form string to validated enum ('Upcoming', 'In Progress', 'Completed') with default 'Upcoming'
- Add PUT /api/events/:eventId/status endpoint for host-only status transitions
- Emit Pusher event-started/event-ended events on status changes
- Update API reference, database schema, event lifecycle, and real-time events docs
The catch block was returning 500 for all errors, including Mongoose ValidationError (e.g., missing or invalid gameType). Now checks for ValidationError by name and returns 400 instead.
Add event model updates and status transition API
Simplify route path to /connected-users, return 200 with empty array instead of 404 when no connections exist, remove dedup to preserve all connections with different descriptions, use populate to reduce DB queries, handle null userId gracefully, and restore nullable userId type on Participant interface.
…fo-by-participantId Get connected user's info by participant
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.