GitLab Fulfillment Demos, 15 Aug 2023

Previous Meeting

Next Meeting

⏯

youtube image

►

From YouTube: Devise mechanisms when updating email address

Description

Related to https://gitlab.com/gitlab-org/customers-gitlab-com/-/issues/6769

A

Hello, so this is a video short video about some device mechanism, some sort of a refresher, because in this issue here we are talking about unverified emails and I wanted to um to to give a sort of refresher so that we are all the reviewers are setting from the same points.

A

So let's consider this profile here this customer here that has the email uh read at example.com and let's have this email changed to Blue at example.com.

A

And you can see that message, which is an expected message given by device. So at this point we are going to check out that customer. So the customer email is still read the previous one.

A

Rather the example.com.

A

And you can see that this customer is confirmed, which is uh which is interesting, because we are changing the email address, but device Works in such a way that conference confirmed is uh set to false at the very beginning when we create the customer and until they get their very first email address confirmed, and we have a confirmed returning true, even though we have unconfirmed email, which is not new. That's the new email address.

A

Now, let's open letter, opener.

A

And we have the email address that says uh that email address was read at example.com and now it's blue. We need to confirm the account.

A

In some time, but in the meantime, Let's uh read all that object here and you can see that the email field is now set to the new email address. While the unconf and confirmed.

A

Email field is set to Neil.

A

The customer is still confirmed.

A

That's about it.