-
Notifications
You must be signed in to change notification settings - Fork 212
Return Continuation Token in response #152
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Our http client code generator does not support this feature yet. We will get to it soon. |
@eyalag , Thanks, |
@eyalag , i am going to close this for now. If you are still having issues on version 0.1.21+, let me know and I will reopen this. Also let us know which method is not working for you. |
I'm having issues on version 1.22. Please reopen this ticket, as this bug makes retrieving large lists impossible. |
@phclark Can you provide more details? Which method are you having problems with? |
Sure, a basic example of what I'm trying to do:
There seems to be no way of retrieving a continuation token, which is returned as expected from the equivalent REST API call. |
Thank you. The client code generator needs to be updated to fix this method. |
i have the same issue with the method get_projects from core client. There is no way to retrieve the continuation token.
|
Interestingly, I'm also having issues with getting continuationTokens to work when using the raw REST API. When I make a GET request like,
The token, returned in the header field x-ms-continuationtoken does not vary when the returned continuationToken is included in the next request. |
@phclark Can you try the
|
Sorry, that was a typo. I am using $top. |
Duplicate to MicrosoftDocs/vsts-rest-api-specs#178, which sounds like it has been fixed in the service. |
reopening for the broader ContinuatuonToken issue, which should be fixed soon. |
Fixed in #258 Continuation Token example:
|
The continuation token cannot be retrieved from the response- which means that one cannot know if he got all the data.
The text was updated successfully, but these errors were encountered: