Hardcode email on registration if it is an invite
What does this MR do and why?
Hardcode email on registration if it is an invite
- less fields and allows changing of an email for an invite easily as that could lead to issues accepting the invite
- see #429936 (comment 1661352529) for discussion on how to handle error condition
- see #429936 (closed) for more details
Changelog: changed
Screenshots or screen recordings
| Before | After |
|---|---|
 |
 |
How to set up and validate locally
- Visit sign up page:
/users/sign_up - Notice current setup w/email and sign up.
- Visit sign up page with invite email as param:
/users/sign_up?invite_email=something@bb.com - Notice change in screenshots and sign up.
- Visit sign up page again with an invite email that is used by a user already:
/users/sign_up?invite_email=something@boub.com - Notice the error handling ability.
- Compare to master branch if desired.
MR acceptance checklist
This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.
-
I have evaluated the MR acceptance checklist for this MR.
Related to #429936 (closed)
Edited by Doug Stull