Addresses user bug reports: settings pages needed real notification
preferences and account deletion, admin needed a way to flag a specific
photo independent of deleting it, and the pending-approval users list
needed to surface applicant photos for review.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
- User.Bio: a short (300 char) freeform profile bio, editable via
PATCH /profile/bio, shown on discover cards and candidate detail (richer
profiles beyond the fixed onboarding fields).
- User.StreakCount/LastActiveDate: POST /profile/checkin increments the
streak on consecutive days, resets after a gap, no-ops if already
checked in today. Backs a daily-return hook on the frontend.
- User blocking (with reason) now closes the auth gap immediately — a
blocked user's still-valid access token stops working on the next
request, not just on their next OTP/refresh.
- Admin-created reports (moderation notes) per user, viewable in a history
list independent of block status.
- GET /admin/users: full paginated, searchable user list with report counts.
- GET /admin/matches: all matches across the app ("friends" who mutually
liked each other), for admin visibility.
- GET/DELETE /admin/photos: paginated feed of every uploaded photo with
uploader info, so admins can review and remove content without going
user-by-user.
- Per-user activity: monitoring requests can now be filtered by user_id, so
a user's detail page can show their recent API activity.
- Batched the profile-selections query in fullProfilePayload (was 6 queries
per view, now 1) for consistency with the earlier N+1 fixes.
- Recovery middleware (no more crash-on-panic), request metrics/monitoring
store + admin API, in-memory TTL caching for read-heavy option/question/
category lookups, gzip + rate-limiting middleware, sanitized chat message
encoding, and pg_dump-based database backups with an admin API.
- Fix N+1 queries in the discover feed, candidate detail, and match list
endpoints by batching selection/photo/user/last-message lookups into
single queries instead of one-per-item loops.
- Tune DB connection pooling and add HTTP server timeouts + graceful
shutdown so the API degrades gracefully instead of falling over under load.
- Fix a null (vs empty array) JSON response for candidates/matches without
photos or interests, which crashed the web app's swipe card.
Photos are now step 2 of onboarding (right after basic info) instead
of only being manageable from the profile page later. Uploading still
goes through the existing /profile/photos endpoint; the new
POST /onboarding/photos just confirms at least one photo exists and
advances the step counter. Renumbered the OnboardingStep enum
accordingly (9 steps total now).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Multi-stage Dockerfile for the Go API, plus a docker-compose.yml that
runs postgres + backend + both frontends together for local
full-stack dev (frontends built from the sibling repo directories).
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Phone+OTP auth, staged onboarding, admin approval workflow, and a
full discovery/swipe/match/chat system with photo upload and
approximate distance (haversine) based on user location.
Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
mobiniqow