Performance: Calculate table footer totals on the server - #378
Merged
Conversation
priethor
marked this pull request as ready for review
June 26, 2026 15:10
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.
What
Closes #132.
Table calculation footers now request the rows endpoint for totals when the table uses server pagination. The footer shows totals for the full filtered and searched result set, not just the current page, and still falls back to the existing local calculation path when server-side totals are unavailable.
Why
This avoids fetching every page just to calculate footer values locally, which made the default table calculation path heavier than necessary.
How
counttotals.Testing Instructions
Screen recording
Grabacion.de.pantalla.2026-06-26.a.las.17.06.17.mov