-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Fixes TreeSliver collapsing not working #153438
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
Fixes TreeSliver collapsing not working #153438
Conversation
Piinks
left a comment
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.
Hi @Mairramer thanks for sending another PR!
It looks like this is trying to fix two issues. Would you be willing to separate them into two PRs? That way if one introduces a regression and we need to revert it, we won;t end up reverting the other fix as well.
|
We should also follow up on the TreeView side, the code is almost identical so we should make the same fix there. |
Ok, I'll check. |
|
Splited PR #153890 |
|
It looks like this pull request may not have tests. Please make sure to add tests before merging. If you need an exemption, contact "@test-exemption-reviewer" in the #hackers channel in Discord (don't just cc them here, they won't see it!). If you are not sure if you need tests, consider this rule of thumb: the purpose of a test is to make sure someone doesn't accidentally revert the fix. Ask yourself, is there anything in your PR that you feel it is important we not accidentally revert back to how it was before your fix? Reviewers: Read the Tree Hygiene page and make sure this patch meets those guidelines before LGTMing. The test exemption team is a small volunteer group, so all reviewers should feel empowered to ask for tests, without delegating that responsibility entirely to the test exemption group. |
Piinks
left a comment
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.
Unfortunately, we won't be able to merge this without test coverage.
|
@Piinks I tested it in several ways, and the problem turned out to be purely visual. The node is indeed collapsed, and the children are inactive, but when used in an app, they still appear on the screen despite not being able to interact with them. Would it be possible to write a golden test for this? Edit: |
No, this is not something that would be test exempt. Perhaps you can check that the render object paints the children as expected? |
…orking # Conflicts: # packages/flutter/test/widgets/sliver_tree_test.dart
Piinks
left a comment
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.
LGTM
justinmc
left a comment
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.
LGTM 👍
This change addresses bug #153418 by ensuring that nodes are handled correctly when closing their children.
Fixes #153418
Pre-launch Checklist
///).