microsoft / microsoft/azure-devops-go-api
ContinuationToken type mismatch between GetReleasesResponseValue and GetReleasesArgs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 223
- Forks
- 92
- PR merge metrics
- No merged PRs in 30d
Description
In the release client.go file, the type for ContinuationToken differs between the GetReleasesResponseValue (which returns the continuation token as a string) and the GetReleasesArgs which takes the continuation token as an *int.
I can work around this by converting the string before continuing the calls to get more releases, but I'm not clear if this is intended behaviour or if I am making a mistake?
client.go lines 1069-1073:
type GetReleasesResponseValue struct {
Value []Release
// The continuation token to be used to get the next page of results.
ContinuationToken string
}
client.go lines 1021-1045:
type GetReleasesArgs struct {
// other properties excluded...
// (optional) Gets the releases after the continuation token provided.
ContinuationToken *int
}
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 in azuredevops/release/client.go around GetReleasesArgs and GetReleasesResponseValue, then inspect the release API definition or related pagination tests. Confirm the expected continuation-token type and make the request and response representations consistent; done means callers can pass the returned token into the next GetReleases request without an ad hoc conversion.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100