In the live demo, the response we saw on the console when Kevin tried to log in with a gmail account was a 500 server error. However, this should be a 400 Bad Request. I know that currently we are dealing with Log In/Register as the same thing, but I think in the future, we could just leave all the handling to the users POST route itself, since it returns a 409 Conflict if the user already exists, which we could display to the users on the frontend.
In the live demo, the response we saw on the console when Kevin tried to log in with a gmail account was a 500 server error. However, this should be a 400 Bad Request. I know that currently we are dealing with Log In/Register as the same thing, but I think in the future, we could just leave all the handling to the users POST route itself, since it returns a 409 Conflict if the user already exists, which we could display to the users on the frontend.