Skip to content
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

Implement "Leave Community" Feature #11359

Open
2 tasks
dillchen opened this issue Mar 10, 2025 · 4 comments
Open
2 tasks

Implement "Leave Community" Feature #11359

dillchen opened this issue Mar 10, 2025 · 4 comments
Assignees

Comments

@dillchen
Copy link
Contributor

dillchen commented Mar 10, 2025

Description

Currently, users can join communities but lack a straightforward way to leave them. This ticket adds a "Leave Community" feature that removes users from communities they no longer wish to be part of. The implementation should ensure all relevant data associations are properly updated when a user leaves a community.

Project Owner

@dillchen

Acceptance Criteria

  • Users can leave a community via a clearly visible UI action
  • Users are properly removed from the community's member list
  • Users lose any community-specific roles/permissions upon leaving
  • Users receive confirmation when they successfully leave a community
  • The UI updates immediately to reflect the changed membership status
  • Users can rejoin a community after leaving if they choose to

Implementation Plan

  • Platform: DeleteAddress -> DeleteAddresses
    -- Update the route to delete subscriptions + downgrade roles of the soft-deleted addresses (just in case)
  • Client: Allow user to Leave Community from the sidebar (Join Community button will become Leave Community)

Technical Notes

  • Use a database transaction to ensure all related operations complete successfully
  • The feature may affect community statistics and member counts
  • Consider performance impacts for large communities
  • Ensure proper error handling and recovery
  • Document the feature for both users and developers
@dillchen
Copy link
Contributor Author

@Rotorsoft / @timolegros anything that we missed from the platform side that this ticket did not cover?

@timolegros
Copy link
Collaborator

Is the expectation for the new route that we remove all of a user's addresses from a community because we already have DeleteAddress.command which basically does "leave community" if you only have a single address left in that community?

Potential platform changes could be simply:

  • DeleteAddress -> DeleteAddresses
  • Update the route to delete subscriptions + downgrade roles of the soft-deleted addresses (just in case)

@dillchen
Copy link
Contributor Author

Yea we should do that:

Going to update the scope of this:

  • Platform: DeleteAddress -> DeleteAddresses
    -- Update the route to delete subscriptions + downgrade roles of the soft-deleted addresses (just in case)
  • Client: Allow user to Leave Community from the sidebar (Join Community button will become Leave Community)

@timolegros
Copy link
Collaborator

Turns out we already have DeleteAllAddresses which was added when the address management in edit profile was refactored. Only change required on platform is updating the side effects (subscriptions).

@dillchen dillchen added this to the UX Frictions v4 milestone Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants