#130 - Add Support for Multiple User Emails

[gamesover]

This PR introduces the ability for users to associate multiple email addresses with their account. It addresses issue #130, which highlighted the need for this feature to prevent duplicate accounts and improve user experience, particularly for users who sign up with different emails (e.g., work and personal).

Key Changes:

• Model Changes:

  • Created a new Email model to store multiple email addresses associated with a user (belongs_to :user).
  • Modified the User model to has_many :emails (must be declared before devise multi_email_authenticatable).

• Devise Integration:

  • Added the devise-multi_email gem to leverage its features for managing multiple emails within Devise.

• Controller Changes:

  • Created a new My::EmailsController to handle:
    • Adding new email addresses.
    • Setting a primary email.
    • Deleting email addresses.
    • Sending confirmation emails upon adding a new email.
  • Updated ReactivationsController and MailingList::Sync to use the user's primary email from the Email model.

• Mailer Changes:

  • Added a trigger_after_confirmation callback to the Email model to handle email updates after confirmation.

• View Changes:

  • Added views for managing multiple emails in the my/emails directory.
  • Updated the my/details/show view to display the user's associated email addresses and their confirmation status.
  • Added links for setting a primary email and deleting email addresses (for confirmed emails only).

• Migration:

  • Created a migration to add the emails table.
  • Created a migration to temporarily remove the null: false constraint from the users.email column.

• Testing:

  • Added tests for the Email model, My::EmailsController, and other relevant components to ensure proper functionality.
  • Updated existing tests to work with the new multi-email setup.

Migration Strategy for Existing Users:

1. The users.email column will temporarily allow null values.
2. run User.without_emails.find_each(&:update_emails) in rails console
3. After the data migration, the users.email column will be removed or repurposed.

Further Considerations (Out of Scope for this PR):

• Implementing a "one-click" email association feature for a smoother user experience.
• Updating other parts of the application that might rely on User.email (e.g., notifications, other mailers).
• Adding a mechanism for users to choose which email to use for specific types of notifications.
• Finalizing the handling of the original email column in the User model.

** UI changes
add new email

list emails

delete email

[gamesover]

in my local and production, I can see below error in chrome console

using import to fix the error

[gamesover]

Remove the ability to edit the email field. Instead, users can add a new email or delete an existing one.

[leesheppard]

change 'ukpdated' to updated

[leesheppard]

change have to has

[leesheppard]

Remove is