Skip to content
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

bugfix: bitbucket paged results, use next page id versus incrementing… #29

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

twilly86
Copy link

@twilly86 twilly86 commented Mar 1, 2022

When making the request..

https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/#api-repositories-workspace-repo-slug-pullrequests-pull-request-id-comments-get

the next page id was alphanumeric id, grabbed from the "next" page url.

Update api client to parse out the "next" page parameter and use that versus incrementing the page id.

… integer to support bitbucket paged alphanumeric ids

… integer to support bitbucket paged alphanumeric ids
if (!isLastPage)
{
var myUri = new Uri(selectorResults.Next);
var nextPage = myUri.DecodeQueryParameters().FirstOrDefault(x => x.Key == "page");
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

parse out the page id from the "next" url and use that for the next pge versus auto incrementing

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants