Add some ways to work with user_email in remove_project_collaborator() and update_project_collaborator()

Open
#242 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
api

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.

Description

enhancement

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.

Dominant language
Python
Stars
23
Forks
12
Avg merge
2d 13h
Merged PRs (30d)
7

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from MerginMaps/python-api-client

All issues in MerginMaps/python-api-client

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.