feat(android): warn when layout child limits are exceeded#223
Open
V3RON wants to merge 2 commits into
Open
Conversation
Surface development-only warnings before Jetpack Glance truncates Column or Row children.
Reuse shared payload types and consolidate traversal guards without changing warnings.
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
1 participant
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 is this?
This PR adds development-only warnings when Android
ColumnorRowlayouts have more than Jetpack Glance’s 10 direct rendered children. It also documents the platform limit in both versioned Android layout guides.How does it work?
Every Android rendering route now validates the final serialized payload, after JSX resolution. The validator traverses widget variants, live-update roots, single-variant payloads, and shared-element references, then warns once for each oversized
AndroidColumnorAndroidRow. It stays silent outside development and recommendsLazyColumnfor dynamic or scrollable collections.Why is this useful?