You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
instead of another endpoint, could we use idempotency IDs on the backend for registration so that if the same idempotency ID appears, it just sends another email? On the frontend, this wouldn't change anything.
I don't know if I understand exactly what you mean? If a user resubmits a registration form under the same username, it will automatically override an unconfirmed user in the database. If they don't receive an email, they should be able to resend the email without filling the form again. This is more of a UX enhancement.
However, you are right that a new confirmation link is generated each register, which breaks old links. We might want to fix that too.
maybe we would have the resubmit button, this would have the frontend send the same info to the server with an ID. if that ID matches an unconfirmed user (meaning that its the same username, email, etc.), then it doesn't overwrite, it just sends another confirmation email. If I understand this correctly, it wouldn't require another endpoint.
That way, the user doesn't have to resubmit the form. Would probably require another backend API endpoint.
The text was updated successfully, but these errors were encountered: