Chore: test email updates

[kiwicopple]

Mock up tests for #57

[kiwicopple]

This is one way we can resolve the strange behavior

we might even want to add an initial_email field which stores the email that the user first used during signup? I think it's even better to be added to the app_data

{
  "app_metadata": Object {
    "provider": "email",
    "initial_email": "user@email.com"
  },
  "email": "updated@email.com",         // original email
  "id": Any<String>,
  "role": "",
}

[Etheonor]

this solution seems great!

In a future version it would be cool to differentiate the email from the user login, and to be able to choose a username.

[asciidiego]

is this fixed yet?

[kangmingtay]

Hey @diegonyc, @Etheonor, as mentioned in #67:

i think this issue has been resolved already. You can update your email with supabase.auth.updateUser which will return a user object with the new_email field. You'll have to verify the email change confirmation link that's sent to your email before you can login with the new_email.

Also, this fix wouldn't be appropriate since the new_email isn't confirmed yet. By setting it to the user.email here, we're assuming that the user has already confirmed the new email address.