-
-
Notifications
You must be signed in to change notification settings - Fork 391
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 all comments when deleting account #1267
Conversation
Signed-off-by: Luke Vella <[email protected]>
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe changes implement an enhancement to the user router's comment deletion logic. Previously, comments were deleted solely based on the user's ID. The updated logic now also allows comments to be deleted if they are linked to specific polls identified by a Changes
Poem
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (invoked as PR comments)
Additionally, you can add CodeRabbit Configuration File (
|
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.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- packages/backend/trpc/routers/user.ts (1 hunks)
Additional comments not posted (1)
packages/backend/trpc/routers/user.ts (1)
67-67
: LGTM! Verify the impact of broader comment deletion logic.The updated logic for deleting comments based on both
pollId
anduserId
aligns with the PR objectives and enhances data integrity.However, ensure that this broader deletion logic does not unintentionally affect other parts of the application.
Run the following script to verify the usage and impact of the
delete
mutation:Verification successful
Broader deletion logic verified successfully.
The
delete
mutation is used in expected contexts, including tests and UI components, ensuring comprehensive user data deletion without unintended side effects.
- File:
packages/backend/trpc/routers/user.ts
- Direct usage in mutation logic.- File:
apps/web/tests/authentication.spec.ts
- Usage in tests, ensuring correctness.- File:
apps/web/src/app/[locale]/(admin)/settings/profile/delete-account-dialog.tsx
- Usage in UI component for account deletion.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify the usage and impact of the `delete` mutation. # Test: Search for the usage of the `delete` mutation. Expect: No unintended side effects. rg --type typescript -A 5 $'user.delete'Length of output: 74
Script:
#!/bin/bash # Description: Verify the usage and impact of the `delete` mutation. # Test: Search for the usage of the `delete` mutation. Expect: No unintended side effects. rg -A 5 'user.delete'Length of output: 1360
We need to delete all comments in polls belonging to a deleted user.
Summary by CodeRabbit