Skip to content

Conversation

@vpomerleau
Copy link
Contributor

Because:

  • We don't want to hold on to unconfirmed secondary emails
  • Let's use Redis to store the temporary entry and only add to db once verified

This commit:

  • Update emails route handlers to use Redis
  • Add new error type
  • Update front end to hadnle the flow changes

Closes #FXA-12548

Because

This pull request

Issue that this pull request solves

Closes: (issue number)

Checklist

Put an x in the boxes that apply

  • My commit is GPG signed.
  • If applicable, I have modified or added tests which pass locally.
  • I have added necessary documentation (if appropriate).
  • I have verified that my changes render correctly in RTL (if appropriate).

Screenshots (Optional)

Please attach the screenshots of the changes made in case of change in user interface.

Other information (Optional)

Any other information that is important to this pull request.


await expect(settings.alertBar).toHaveText(/successfully deleted/);

await settings.secondaryEmail.addButton.click();
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Unconfirmed secondary emails will no longer be stored in the database, only temporarily in Redis --> if the setup is incomplete, there is no new "unconfirmed" entry in Settings.

Because:

* We don't want to hold on to unconfirmed secondary emails
* Let's use Redis to store the temporary entry and only add to db once verified

This commit:

* Update emails route handlers to use Redis
* Add new error type
* Update front end to handle the flow changes
* Update tests

Closes #FXA-12548
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants