Team API v2 wishlist
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 363
- Forks
- 369
- Avg merge
- 1d 54m
- Merged PRs (30d)
- 59
Description
Things we should improve if we create a second version of the Team API:
- Remove GitHub usernames from the permissions, keeping only the GitHub IDs (authorizing by username is insecure)
- Replace
_with-in the permission names and paths
Contributor guide
No contributing guide indexed for this repository
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
No files, tests, or entry points are named. First locate the Team API permissions and path definitions, then determine whether a v2 design exists; done means the API uses GitHub IDs rather than usernames and uses hyphens instead of underscores in permission names and paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100