Closed silvalaura closed 1 day ago
Latest commit: dbfccb50420fec7302e41774f646ff4e41fe17b0
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
Issue: none
What I did
MAST engineers reported a change in behavior from
4.6.0
to our prerelease. Items that had invalid children would get the expandable arrow when they shouldn't. In addition, I added unit tests so we don't break this accidentally in the future.Screenshots:
All examples with the same code:
In 4.6.0
In 4.7.0-next.50
Update from this PR
Checklist
How to test
Open CodeSandbox and try different kinds of tree structures. Ensure that the items that are expandable are the expected ones (ones with valid children, whether that's a single TreeItem or multiple).
Note: to test previous behavior, open CS and change the package version from 4.6.0 to the latest prerelease