Create recent gamer entries only after email verification #1014

Open
opened 2026-11-05 11:10:52 -06:00 by Codex · 0 comments
Member

Newly registered users should not appear in the recent game update feed before completing email verification.

The implementation should use the existing Laravel verification state and preserve the feed’s current behavior for verified users.

Scope

  • Locate the registration and recent gamer entry creation path.
  • Defer recent gamer entry creation until the user’s email verification event succeeds.
  • Prevent duplicate entries when verification is repeated or the user already has a recent gamer entry.
  • Add focused feature coverage for unverified registration, successful verification, and existing verified-user behavior.

Acceptance Criteria

  • Registering a user with a null email_verified_at value does not create a recent gamer entry.
  • Successfully verifying the user’s email creates the expected recent gamer entry.
  • Repeated verification handling is idempotent and does not create duplicate entries.
  • Existing verified users continue to appear in the recent game update feed according to current behavior.
  • The behavior is covered by automated tests using the repository’s testing conventions.

Test Coverage Required

  • A feature test verifies that an unverified registration does not create a recent gamer entry.
  • A feature test verifies that email verification creates the entry once.
  • A feature test verifies repeated verification or duplicate handling does not create multiple entries.
  • A regression test verifies verified users retain the existing recent-feed behavior.

Progress Checklist

  • Identify the current recent gamer entry creation and feed query paths.
  • Identify the existing email verification event or listener path.
  • Move or gate entry creation on successful email verification.
  • Add regression tests for unverified, verified, and duplicate cases.
  • Run the focused feature tests and repository-standard formatting checks.
Newly registered users should not appear in the recent game update feed before completing email verification. The implementation should use the existing Laravel verification state and preserve the feed’s current behavior for verified users. ## Scope - Locate the registration and recent gamer entry creation path. - Defer recent gamer entry creation until the user’s email verification event succeeds. - Prevent duplicate entries when verification is repeated or the user already has a recent gamer entry. - Add focused feature coverage for unverified registration, successful verification, and existing verified-user behavior. ## Acceptance Criteria - Registering a user with a null email_verified_at value does not create a recent gamer entry. - Successfully verifying the user’s email creates the expected recent gamer entry. - Repeated verification handling is idempotent and does not create duplicate entries. - Existing verified users continue to appear in the recent game update feed according to current behavior. - The behavior is covered by automated tests using the repository’s testing conventions. ## Test Coverage Required - A feature test verifies that an unverified registration does not create a recent gamer entry. - A feature test verifies that email verification creates the entry once. - A feature test verifies repeated verification or duplicate handling does not create multiple entries. - A regression test verifies verified users retain the existing recent-feed behavior. ## Progress Checklist - [x] Identify the current recent gamer entry creation and feed query paths. - [x] Identify the existing email verification event or listener path. - [x] Move or gate entry creation on successful email verification. - [x] Add regression tests for unverified, verified, and duplicate cases. - [x] Run the focused feature tests and repository-standard formatting checks.
Codex changed title from Don't Add Recent Gamer Entry for Newly Registered User Until Their Account is Verified to Create recent gamer entries only after email verification 2026-11-05 11:11:13 -06:00
Codex self-assigned this 2026-11-10 13:24:40 -06:00
Sign in to join this conversation.
No milestone
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
MyVideoGameList/myvideogamelist.com#1014
No description provided.