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

NoMongo : Implement Membership Mutations #3330

Open
khushipatil1523 opened this issue Mar 2, 2025 · 2 comments
Open

NoMongo : Implement Membership Mutations #3330

khushipatil1523 opened this issue Mar 2, 2025 · 2 comments
Assignees
Labels
feature request unapproved Unapproved for Pull Request

Comments

@khushipatil1523
Copy link

Is your feature request related to a problem? Please describe.
Currently, there are no GraphQL mutations to handle membership requests efficiently. Users cannot send a request to join a private organization, join a public organization instantly, or cancel a pending request. This limits the flexibility of user onboarding and membership management within the system.

Description
In this PR, I will be adding the following GraphQL mutations for managing organization memberships:

sendMembershipRequest(organizationId: ID!): Boolean – Allows users to request membership in a private organization.
joinPublicOrganization(organizationId: ID!): Boolean – Enables users to instantly join a public organization.
cancelMembershipRequest(organizationId: ID!): Boolean – Lets users cancel a pending membership request.
This implementation will follow existing GraphQL patterns, ensuring:

  1. Consistency with the current schema and resolver structure.
  2. Proper error handling and input validation.

Approach to be followed (optional)
Same as used for other mutations, adhering to the current schema and resolver structure to maintain consistency. 🚀

@khushipatil1523
Copy link
Author

@palisadoes can i work on this?

Copy link

This issue did not get any activity in the past 10 days and will be closed in 180 days if no update occurs. Please check if the develop branch has fixed it and report again or close the issue.

@github-actions github-actions bot added the no-issue-activity No issue activity label Mar 10, 2025
@Cioppolo14 Cioppolo14 removed the no-issue-activity No issue activity label Mar 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature request unapproved Unapproved for Pull Request
Projects
Status: Backlog
Development

No branches or pull requests

2 participants