Performance: Request only visible row fields#242
Merged
Conversation
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 #172.
When a table view hides custom columns, row requests now send a
fields[]list so the API only formats the fields the view needs. Full/default views still fetch the full row, and client-mode views keep the full payload because local filters and calculations may need hidden fields.Why
Hidden rollups and relations can still be expensive to format. Skipping them keeps table loads cheaper without changing what the user sees.
How
fields[]and ignores stale or system keys.Testing Instructions
Screen recording
Grabacion.de.pantalla.2026-05-22.a.las.16.57.29.mov