Fix issue where collapsed categories were not remembered after toggling a track #2208
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.
The title of this PR somewhat underestimates the issue scope but it is what the end user experiences
The collapsed category state was not stored in the widget model properly, and it was causing the code to forget the collapsed categories after a track is toggled (which causes the tree to get rerendered)
Note: Technically it might be somewhat expensive/not the best way to do things for for the tree to get recalculated after things like a track toggle or category collapse, but it seems to work fine afaik
This change is also good because it is nice for the collapsed categories to also be remembered in state e.g. across page refreshes
Fixes #2207