microsoft / microsoft/azure-devops-go-api
v6 + v7 pipelines module don't return continuationToken
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 223
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
When using the azure-devops-go-api/azuredevops/pipelines/client.go module, the ListPipelines function returns the continuationToken so that we can get multiple paged results.
In the v6 and v7 versions of pipelines module (azure-devops-go-api/azuredevops/v6/pipelines/client.go + azure-devops-go-api/azuredevops/v7/pipelines/client.go), there doesn't seem to be a way to get the continuationToken from the ListPipelines function. How do we get paginated results using the v6 and v6 vresions of the azure devops pipelines go api modules?
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
Compare ListPipelines in azure-devops-go-api/azuredevops/pipelines/client.go with the v6 and v7 implementations in azure-devops-go-api/azuredevops/v6/pipelines/client.go and azure-devops-go-api/azuredevops/v7/pipelines/client.go. Determine how the continuationToken is exposed in the non-versioned module and make the v6 and v7 functions support retrieving paginated results. Done means callers can obtain the continuationToken from both versioned ListPipelines functions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100