-
-
Notifications
You must be signed in to change notification settings - Fork 52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Delete account view #461
base: develop
Are you sure you want to change the base?
Delete account view #461
Conversation
This pull request is being automatically deployed with Vercel (learn more). 🔍 Inspect: https://vercel.com/code4romania/stam-acasa/mvqaiho9q |
|
||
const AccountApi = { | ||
deleteAccount: (user, password) => | ||
api.post("/DeleteAccount", { Username: user, Password: password }) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we pass the user and not taking it from the session ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
good point! Had a chat with @RaduCStefanescu and my takeaway was we need to ask for them to type the email and password. It might be that I got it wrong and we only need to ask for the password. @RaduCStefanescu can you clarify if there is a requirement to ask the user to put in the email?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Based on this comment I'm guessing he's on-board with the idea 😁
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
cool! I will update the PR accordingly
Co-authored-by: Nicu <[email protected]>
Closing #419
Couldn't test locally the integration with with the backend due to CORS issues.