fix: #26126 use mergedData instead of pageData to decide whether to render bottom pagination or not #26133
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.
[中文版模板 / Chinese template]
🤔 This is a ...
🔗 Related issue link
close #26126
💡 Background and solution
Currently, when using backend pagination (meaning manually managing property pagination.total), if the last record on the last page is deleted, and pagination becomes invisible(which should not happen), since length of records is not 0.
Use mergeData.length to decide whether to render bottom pagination should fix the problem.
📝 Changelog
☑️ Self Check before Merge