Deleteuser#85
Merged
Merged
Conversation
- Add deleteUserAccount helper function to handle cascading deletions * Delete all groups owned by the user * Remove user from all groups they're a member of * Delete the user account itself - Add DELETE /:userParam endpoint for account deletion * Verify user can only delete their own account * Extract user by ID or email using existing getUserFilter logic * Clear authentication cookie on successful deletion to log out user * Return appropriate error responses (404 for not found, 403 for unauthorized) - Import AUTH_COOKIE_NAME and clearAuthCookieOptions from auth config - Ensures data integrity when users delete their accounts by cleaning up group associations
Contributor
Author
|
I ran a test when I connected it and all tests pass but please feel free to go in and check it out, should work once pushed to main |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
okay in order to test this before pushing to prod : Run the backend locally and point the frontend at it (temporarily change AZURE_URL to http://localhost:5050, or whatever your backend port is). The DELETE will succeed and clean up. This is the no-deploy way to verify. , the only way this would work is if we push to main since the main has that hardcoded Azure url , it should work but for testing I just ran the backend locally and pointed the frontend to it instead of that Azure url it has