Fix Pagination Previous Button Behavior #22007
Merged
Conversation
This file contains 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.
Description
The calculation for currentPage in GetPreviousButtonAsync assumes that the TagHelper.Model.CurrentPage is always valid. If TagHelper.Model.CurrentPage becomes 0 or -1, the disabled class will not be applied correctly, leading to the Previous button being enabled even when it should be disabled.
Currently, the logic to disable the Previous button only considers whether CurrentPage == 1. There is no safeguard for invalid page values (e.g., 0, -1).
This bug only occurs on routes with an ID parameter, such as homepage.com/movie/{id}/reviews?currentPage=1, where {id} is used to fetch reviews for a specific movie. However, on the "movie" index route (homepage.com/movie?currentPage=1), the pagination renders correctly.