This repository has been archived by the owner on Feb 2, 2023. It is now read-only.
[ASDisplayNode] Fix setNeedsLayout triggered from subnode will not trigger relayout #1902
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.
Current if
[ASDisplayNode invalidateCalculatedLayout]
and[ASDisplayNode setNeedsLayout]
called in a subclass (see[ASButtonNode setTitle:]
) the call actually does not trigger any relayout. It does not even bubble up the tree as it returns early in[ASDisplayNode __setNeedsDisplay]
After talking with @nguyenhuy about the initial intention why we are returning early there we found a better way for it.
This should resolve: #1865
@nguyenhuy @levi @appleguy Can I get a look over please