-
Notifications
You must be signed in to change notification settings - Fork 3.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Don't render children of collapsed blocks #4264
Conversation
I think I might have changed this because of #1967 but I can't exactly remember. |
ba3248e
to
cad7efa
Compare
40aec8d
to
c99384e
Compare
var parentInput = parentBlock.getInputWithBlock(childBlock); | ||
if (parentInput && !parentInput.isVisible()) { | ||
childBlock.rendered = true; | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm worried about whether this may have unintended side effects.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it looks good! Because if the block is top-level it should definitely be visible right? As long as the nested disconnection test is passing it should be fine.
I'm going to tag this with #4288 though cuz I know that .rendered
is kinda crazy wrt collapsed blocks.
The basics
The details
Resolves
Part of #4229
Proposed Changes
updateDisabled
on children inupdateDisabled
.Reason for Changes
Improves performance.
Test Coverage
Tested scenario descibed in #4229 and saw improvement in performance while testing with chrome performance tool.
Tested that issues #3784 was still fixed.
Tested issue #1967 in playground using xml:
And repro code:
Tested on:
Additional Information
n/a