Continuation token functionality is unusable

[bworline]

Environment

Node version: 14.17.6
Npm version: 6.14.15
OS and version: WIn10 21H2
azure-devops-node-api version: 11.1.1

Issue Description

How does one get a continuation token out of an azure-devops-node-api API method to pass back into the same API method? Many methods imply that a token is returned but I don't see how.

Example: The comments for getBuilds() say,
@param {string} continuationToken - A continuation token, returned by a previous call to this method, that can be used to return the next set of builds.

The return type is a Promise<Build[]> array of builds, so it's unclear how a token would even be made available to the caller.

[max-zaytsev]

Hi bworline, Thanks for reporting this. Most of the code here is auto-generated from the server-side controllers.
In this case it might be worth hitting the endpoint directly through an http call (or using the typed-rest-client).

[max-zaytsev]

Close this for now. Please reopen if you still have any questions

[bworline]

Maxim Zaytsev (@max-zaytsev) Thank you; I do appreciate the potential workaround you've provided and will likely go that route.

But I want to make sure I understand the response. Are you saying that because of [implementation detail], this REST wrapper library produces an incorrect wrapper By Design, so I should not use the library? And there is nothing that can be done to update the auto-generation code to expose the continuation token?