MerginMaps / MerginMaps/python-api-client
Add some ways to work with user_email in remove_project_collaborator() and update_project_collaborator()
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 23
- Forks
- 12
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 7
Description
When using remove_project_collaborator() or update_project_collaborator() one needs user_id which is not exactly easy to get. It can be extracted from list_project_collaborators() which provides the info, but it is not really handy or intuitive.
Either remove_project_collaborator() and update_project_collaborator() should take also user_email besides user_id to allow editing collaborators for project. Or there could be new Endpoint and client function to get user_id from user_email.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading remove_project_collaborator(), update_project_collaborator(), and list_project_collaborators() to understand their current user_id handling. Clarify whether the intended outcome is email support in the existing functions or a user_id lookup endpoint, then define the API behavior and tests needed to show collaborator updates work with the chosen approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100