Collapse the Recent section in the left sidebar
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 76/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start in app/src/renderer/project/Sidebar/Sidebar.tsx and trace how the sidebar renders Recent and stores its collapsed state in ProjectView. Check how the floating sidebar shares that state and how Recent handles an empty list. Done means the section toggles with an accessible button and chevron, starts expanded, persists per project across restarts, and retains pages while collapsed.
Written by the indexing model from the issue text.
Description
Let the Recent section in the left sidebar (#184) collapse to its heading, so a long list of recent pages can be put away.
Why
Recent grows with every page opened. Someone who mostly uses Journal and All pages, or who just wants a quieter sidebar, has no way to hide it today.
What
- Clicking the "Recent" heading collapses or expands the list. The heading stays; the list (or the "Pages you open show up here." hint) hides under it.
- A chevron beside the heading shows which way it is: pointing right when collapsed, down when expanded.
- Expanded by default.
- Kept across restarts, per project, like the sidebar's own collapsed state (
Kept<{ collapsed: boolean }>inProjectView). - The floating sidebar (shown while pointing at the toggle) follows the same state.
- Collapsing hides, it doesn't forget. Pages opened while collapsed still go into Recent and show when it is expanded again.
- Keyboard and screen readers: the heading is a button with
aria-expandedandaria-controlson the list.
Not in this
- Collapsing Journal and All pages, or any other section that may come later.
- Changing how many pages Recent holds.
Code: app/src/renderer/project/Sidebar/Sidebar.tsx.
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 16m
- Merged PRs (30d)
- 107
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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 shovon/pbnotes
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Website for Pb NotesOpenenhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 45/100
Maintainers usually reply within 1 day
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
pending close triaging
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
anomalyco/opencode#62582 · 1 comment ·
Maintainers usually reply within 1 day
-
feature request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
callstack/react-native-paper#5189 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
live-codes/livecodes#1079 · 1 comment ·
Maintainers usually reply within 1 day
-
Add: ESP 2 ROOpenapproved check:passed streams:add
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
Maintainers usually reply within 1 day