-
-
Notifications
You must be signed in to change notification settings - Fork 5.8k
Only use prev and next buttons for pagination on user dashboard #33981
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
Only use prev and next buttons for pagination on user dashboard #33981
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why a new unnecessary config option and why keep copying-pasting the code , and why math.MaxInt32
It should make a "Paginator" like this: Pages=nil, HasPrev=true, HasNext=true |
Did you mean reuse the original template? Then we still need to handle |
e2f13c0
to
19d11c3
Compare
19d11c3
to
69aa478
Compare
I believe yes. Otherwise, how could a user know which page they are viewing? |
f10dd0b
to
9271280
Compare
9271280
to
1f790ec
Compare
* giteaofficial/main: [skip ci] Updated translations via Crowdin Only use prev and next buttons for pagination on user dashboard (go-gitea#33981) update jwt and redis packages (go-gitea#33984) [skip ci] Updated translations via Crowdin Improve oauth2 error handling (go-gitea#33969) [skip ci] Updated translations via Crowdin Cover `go.mod` and `go.sum` in `.editorconfig` (go-gitea#33960) Drop timeout for requests made to the internal hook api (go-gitea#33947) Fix file name could not be searched if the file was not a text file when using the Bleve indexer (go-gitea#33959) Fix oauth2 auth and UI (go-gitea#33961) Allow filtering issues by any assignee (go-gitea#33343) Optimize total count of feed when loading activities in user dashboard. (go-gitea#33841) Extract code to their own functions for push update (go-gitea#33944) Optimize heatmap query (go-gitea#33853)
The pagination on the user dashboard sounds unnecessary, this will change it to a prev/next buttons. For instances with around
10 million
records in the action table, this option affects how the user dashboard is loaded on first visit.Before:
After: