added pagination options for listing requests #203
No reviewers
Labels
No Label
has/backport
has/pull
in progress
invalid
kind/breaking
kind/bug
kind/build
kind/deployment
kind/docs
kind/enhancement
kind/feature
kind/lint
kind/proposal
kind/question
kind/refactor
kind/security
kind/testing
kind/translation
kind/ui
need/backport
priority/critical
priority/low
priority/maybe
priority/medium
reviewed/duplicate
reviewed/invalid
reviewed/wontfix
skip-changelog
status/blocked
status/needs-feedback
status/needs-reviews
status/wip
upstream/gitea
No Milestone
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: gitea/go-sdk#203
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "spawn2kill/go-sdk:master"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Like discussed on #202, all
ListXXXXX
requests now supports pagination.ListXXXXXOptions
structs which includesListOptions
struct have been added to all methods. By default it gets the first page with 10 results.Gitea's API needs to be changed in order to support pagination in all requests.
@ -12,2 +12,4 @@
)
// AdminListOrgsOptions options for listing admin's organizations
type AdminListOrgsOptions struct {
What's the difference between
AdminListOrgsOptions
andListOrgsOptions
?I'm not sure what you are talking about... there isn't any struct called
ListOrgsOptions
. I just created an options struct for each request that lists something. About the AdminListOrgsOptions naming it's because it is sub route from/admin
: https://try.gitea.io/api/swagger#/admin/adminGetAllOrgsGood. But this is a break change. We may need to name it a v2 version.
We can release a v0.1.0 and this PR will be in v0.2.x
go-gitea/gitea#9452 adds support on Gitea's API to pagination in most of the requests.