Remember sidebar tree expansion and panel sizes across app restarts
Maintainers usually reply within 1 day
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- tauri, typescript
Research direction
Start by locating the sidebar tree expansion state and resizable log panel in the app, then trace how the app persists settings across launches. Implement restoration for existing expanded nodes and panel dimensions, while skipping missing nodes, avoiding lazy loads for collapsed nodes, and clamping sizes to the window. Done when those states survive a restart and the listed edge cases behave as described.
Written by the indexing model from the issue text.
Description
I really love Tabularis so far (coming from DataGrip), but one thing that annoys me is having to expand the database tree again every time I reopen Tabularis.
Request: Persist and restore UI layout state across launches:
- Which connections, databases, schemas and tables are expanded in the sidebar tree (ideally per connection).
- The size of the resizable log panel (height/width), so it reopens at the size I last set.
Why it matters: On larger servers, re-expanding the same nodes and resizing the log panel after every restart means repeated clicks. DataGrip keeps this state, which is what I'm coming from.
Edge cases: Nodes that no longer exist (dropped table, removed connection) should be skipped silently. Restored-collapsed nodes should not trigger lazy loading of their children. The panel size should be clamped to the current window size.
- Dominant language
- TypeScript
- Stars
- 5.1k
- Forks
- 335
- Avg merge
- 1d 11h
- Merged PRs (30d)
- 289
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from TabularisDB/tabularis
-
feature request good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
TabularisDB/tabularis#1395 ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 5/5 Over a week Newbie friendliness 38/100
TabularisDB/tabularis#1418 ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 5/5 Over a week Newbie friendliness 35/100
TabularisDB/tabularis#1417 ·
Maintainers usually reply within 1 day
-
[Feat]: Visual EXPLAIN: save plan snapshots and compare against a baselinePossibly taken @markankamaransheogarat-sys claimed this 1 day ago. Openfeature request help wanted
TabularisDB/tabularis#1416 · 2 comments · 1 assignee ·
Maintainers usually reply within 1 day
-
feature request help wanted
Difficulty 5/5 Over a week Newbie friendliness 45/100
TabularisDB/tabularis#1415 ·
Maintainers usually reply within 1 day
All issues in TabularisDB/tabularis
Similar issues
-
Add: ESP 2 ROOpenapproved check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day
-
ipaas: Configure form shows "Deploy to apply." and "Overrides selected Link" when they don't applyOpen
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
wso2/integration-control-plane#1118 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
UTDNebula/utd-notebook#311 ·
Maintainers usually reply within 2 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day