Skip to content
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

Topic hierarchy doesn't retain expansion state #5093

Closed
joepavitt opened this issue Feb 10, 2025 · 0 comments · Fixed by #5114
Closed

Topic hierarchy doesn't retain expansion state #5093

joepavitt opened this issue Feb 10, 2025 · 0 comments · Fixed by #5114
Assignees
Labels
area:frontend For any issues that require work in the frontend/UI size:S - 2 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story.

Comments

@joepavitt
Copy link
Contributor

joepavitt commented Feb 10, 2025

The Borker topic hierarchy does not retain expansion state when you navigate away to somewhere else in the app and come back. With heavy topic hierarchies, this is a considerable paint point.

Proposa here is to use the UX vuex store to store expansion state, and restore that when navigating back to the Broker view.

@joepavitt joepavitt added area:frontend For any issues that require work in the frontend/UI size:S - 2 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story. labels Feb 10, 2025
@cstns cstns self-assigned this Feb 11, 2025
@cstns cstns moved this to In Progress in 🛠 Development Feb 12, 2025
@cstns cstns mentioned this issue Feb 12, 2025
10 tasks
@github-project-automation github-project-automation bot moved this from In Progress to Done in 🛠 Development Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:frontend For any issues that require work in the frontend/UI size:S - 2 Sizing estimation point task A piece of work that isn't necessarily tied to a specific Epic or Story.
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

2 participants