Fix: Transfer leadingScreensForBatching from pending state on node load#2130
Merged
rcancro merged 5 commits intoTextureGroup:masterfrom Nov 19, 2025
Merged
Conversation
|
Gianmarco seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account. You have signed the CLA already but the status is still pending? Let us recheck it. |
e7aab67 to
1d63a8c
Compare
GianmarcoFolchi
commented
Nov 18, 2025
rcancro
reviewed
Nov 18, 2025
rcancro
approved these changes
Nov 19, 2025
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.
Problem
When
leadingScreensForBatchingis set onASCollectionNodeorASTableNodebefore the node loads, the value is not properly transferred to the underlying view. This causes the property to retain the default value of2.0instead of the configured value.Root Cause
It looks like
leadingScreensForBatchingwas accidentally omitted when transferring the pendingState to the view in thedidLoadfunction.Examples
Broken Example
Result: leadingScreensForBatching stays at 2.0
Working Example
Result: leadingScreensForBatching is correctly set to 2.4 since the view had already been loaded.
leadingScreensForBatchingsetter: leadingScreensForBatching goes to pendingState if it exists else it goes to the underlying view. The pendingState value wasn't being transferred to the underlying view on view creation.