This repository was archived by the owner on Nov 4, 2020. It is now read-only.
Adding pagination to Gitlab.getProjects #18
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@Itxaka although I haven't tested it yet I imagine that Here is an example of how I'm currently handling it with my fork of your project. |
|
@SAG47 Yep, it needs pagination as well. Let's see if I got some time this afternoon to code it :D Thanks for all the patches man ;) |
Itxaka
added a commit
that referenced
this pull request
Sep 14, 2013
Adding pagination to Gitlab.getProjects
Closed
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
It doesn't currently exist. I ran into a wall head long and it took a while to debug and figure out the cause. I thought returning only
20projects was too perfect of a number and it turns out it was. The API supports pagination so I'm adding it to yourgetProjectscall.