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

API: Get all memberships of user #550

Closed
Tracked by #549
rajdip-b opened this issue Nov 22, 2024 · 8 comments · Fixed by #586
Closed
Tracked by #549

API: Get all memberships of user #550

rajdip-b opened this issue Nov 22, 2024 · 8 comments · Fixed by #586
Assignees
Labels
difficulty: 2 good first issue Good for newcomers help wanted Extra attention is needed priority: urgent scope: api Everything related to the API type: feature Release drafter tag for tagging PRs related to adding new features

Comments

@rajdip-b
Copy link
Member

rajdip-b commented Nov 22, 2024

Description

Refer #549

Solution

  • Add a service layer function in workspace.service.ts to return a list of workspaces where the workspaceis invited to. Each item should contain the workspace details and the invitation date. The response should also have pagination support.
  • Add the endpoint in workspace.controller.ts. The path should be GET /api/workspace/invitations. This should be an authenticated path.
  • Add relevant tests in workspace.e2e.spec.ts
@mdimado
Copy link

mdimado commented Dec 3, 2024

Hi @rajdip-b , I’m interested in working on this issue. I have experience with creating service layer functions, handling pagination in API responses, and implementing authenticated routes. I’m familiar with the tech stack and confident I can add the required functionality in workspace.service.ts and workspace.controller.ts, along with writing the necessary tests in workspace.e2e.spec.ts. Looking forward to contributing to this feature

@rajdip-b
Copy link
Member Author

rajdip-b commented Dec 3, 2024

Hey there! Sure, go ahead and best of luck!

@rajdip-b rajdip-b moved this from Todo to In progress in keyshade-api Dec 3, 2024
@rajdip-b
Copy link
Member Author

rajdip-b commented Dec 3, 2024

Don't hesitate to reach out to us if you need any help :D

@rajdip-b
Copy link
Member Author

rajdip-b commented Dec 9, 2024

@mdimado any updates on this?

@Souvik9205
Copy link
Contributor

@mdimado Hi, if you are inactive, can I work on this issue?

@muntaxir4
Copy link
Contributor

@rajdip-b isn't this similar to #404 ?

@rajdip-b
Copy link
Member Author

@rajdip-b isn't this similar to #404 ?

Yes!

@rajdip-b
Copy link
Member Author

@Souvik9205 hey bro, i suggest you can take up the other sub issues for this. The API was need of the hour so we fast tracked it.

@rajdip-b rajdip-b moved this from In progress to Under review in keyshade-api Dec 10, 2024
@github-project-automation github-project-automation bot moved this from Under review to Done in keyshade-api Dec 13, 2024
@rajdip-b rajdip-b moved this from Done to Queued for release in keyshade-api Dec 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
difficulty: 2 good first issue Good for newcomers help wanted Extra attention is needed priority: urgent scope: api Everything related to the API type: feature Release drafter tag for tagging PRs related to adding new features
Projects
Status: Queued for release
Development

Successfully merging a pull request may close this issue.

4 participants