microsoft / microsoft/azure-devops-go-api
Handling rate limits
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 223
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
Add the response for each API endpoint to make it possible to get headers from the response and manage the rate limits, because currently its impossible to check the headers/ how many requests left etc.
In the API itself this data is present.
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
Start by inspecting the API endpoint methods and their current return values, then check how response headers are represented in the Go client. Done means callers can access headers and rate-limit information for every endpoint; verify the approach against the API behavior described in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100