Custom Error Conditions on Sign Up. I'm adding an ...
# generalk
kabal48
09/09/2023, 11:12 PMCustom Error Conditions on Sign Up. I'm adding an additional username field on account creation and saving that along with the userid, and email to my app db (separate from supertoken db). What I'm trying to figure out is if there is a prescribed way of handling errors in this scenario, and rolling back the entire creation on failure. I override emailPasswordSignUpPOST, to get the fields and persist, but how do I rollback transaction in event there is some error thrown by my custom logic
kabal48
09/09/2023, 11:14 PMr
rp_st
09/10/2023, 7:14 AMHey @kabal48 you could detect if there is an inconsistency during sign in, and do the same operation post sign in
rp_st
09/10/2023, 7:15 AMIf your logic during sign up fails, then the user won’t be logged in, and then they will have to sign in, during which you can do this custom logic
rp_st
09/10/2023, 7:15 AMIf you don’t have all the info available during sign in, you will have to ask them for it again post sign in.
rp_st
09/10/2023, 7:16 AMSo it might just be better to ask them the info post sign up / sign in anyway. And guard your frontend and backend to make sure that that info is submitted before allowing access to the app
k
kabal48
09/10/2023, 6:23 PMWhat about the operation to duplicate the user to my own db. Since that can also fail is there no way to rollback original signup in super tokens?
r
rp_st
09/10/2023, 6:24 PMWell, there is, you can call the delete user api, but again, that can fail too. Resulting in the same issue.
rp_st
09/10/2023, 6:25 PMSo therefore, whatever extra info you want to associate with the user, it’s best to ask post sign up / in.
rp_st
09/10/2023, 6:25 PMBut practically, this happens very rarely and most of the time doesn’t matter. Unless you have millions of users
6 Views