Currently if there's a keycloak error during the sign up flow about the recovery email matching an existing one it requires a submit to catch. We should add a rate limited api function that queries our db for existing recovery emails, and use a debounced function (similar to our username check) to see if this recovery email is already in use.
This is part of the feedback from the monday walkthrough.
Currently if there's a keycloak error during the sign up flow about the recovery email matching an existing one it requires a submit to catch. We should add a rate limited api function that queries our db for existing recovery emails, and use a debounced function (similar to our username check) to see if this recovery email is already in use.
This is part of the feedback from the monday walkthrough.