feat: add dashboard API v2 pagination endpoints#5351
Merged
Conversation
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (5 files)
Reviewed by gpt-5.5-2026-04-23 · 251,564 tokens |
dd89ebc to
6d509cf
Compare
fatedier
added a commit
that referenced
this pull request
Jun 1, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Summary
/api/v2while keeping legacy/apibehavior unchangeduserfor clients/proxies andclientIDfor proxiesEndpoints
GET /api/v2/usersGET /api/v2/clientsGET /api/v2/clients/{key}GET /api/v2/proxiesGET /api/v2/proxies/{name}Response shape
All v2 endpoints return the standard envelope:
{ "code": 200, "msg": "success", "data": {} }List endpoints return paginated data:
{ "total": 123, "page": 1, "pageSize": 50, "items": [] }Compatibility
/api/...routes are unchangedclientID,runID,clientIP, andwireProtocolphasein the v2 JSON responseValidation
go test ./server/http ./server/registry ./pkg/util/httpgolangci-lint run --build-tags nowebNote: direct full
go test ./.../ plaingolangci-lint runrequire generated web dist and binary artifacts (web/frpc/dist,web/frps/dist,bin/frpc,bin/frps) in this worktree, so the noweb lint path was used for final validation.