Auth Web - validate account (business profile) email

[davemck513]

• [ ] remove "Confirm email address and related functionality"
• [ ] retain current UI email validation
• [ ] update validation so errors are not shown until Update button is clicked
• [ ] ~Auth API will further verify the email address and return error if invalid~ see ticket #16739
• [ ] ~display "invalid email" error from API~ future
• [ ] add/update unit tests

Sample page:

[severinbeauvais]

cc: @jdyck-fw @Mihai-QuickSilverDev

I looked into validating email in the UI previously and I concluded that validating it in the server (when the change is posted) is better because

• it would only be done once per flow (instead of every user keyclick)
• it would provide full validation in one place (instead of several places in the code)
• the UI would not need to know the MillionVerifier key (so it couldn't be stolen)

THIS ticket suggests that the validation should be done in the UI. We need to figure this out.

[severinbeauvais]

@JohnamLane I believe this is for your team, please and thanks. (Mihai said so ;) )

[severinbeauvais]

@janisrogers @yuisotozaki Any thoughts on removing the second (confirm) email input?

[janisrogers]

I am all for this idea, but I may be outnumbered. Let me bring it up in our design meeting.

[severinbeauvais]

I'm also looking for your thoughts on whether we could do email validation after the Update button is clicked (ie, validation done by API), instead of validation done in the UI when the user enters the email. The latter would make multiple calls to the (paid) MillionVerifier API, which is undesirable.