Tree screens should start collapsed, and cache their state
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 68/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- frontend
Research direction
Start by locating the tree view component and the state used when it opens. Change the initial state so the tree is collapsed, then verify that opening the view shows collapsed nodes while existing expansion behavior still works.
Written by the indexing model from the issue text.
Description
On start all tree items are expanded, and on a refresh or when switching beamlines, everything re-expands. There are likely way too many subscreens for this to be desirable.
I believe the behaviour should be:
- on startup with no cache everything is all collapsed
- on refresh/beamline switch - cached state of tree expansion, if nothing cached fall back to all collapsed
Currently on b01-1:
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 1
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 5
Getting set up
- Ships a Dockerfile or Docker Compose file
- No pull request template
- No 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 DiamondLightSource/daedalus
-
Difficulty 3/5 1-2 days Newbie friendliness 62/100
-
Add error handlingOpen
Difficulty 5/5 Over a week Newbie friendliness 25/100
All issues in DiamondLightSource/daedalus
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 72/100
cline/mcp-marketplace#2932 ·
-
community first-timers-only good first issue hacktoberfest help wanted low hanging fruit up-for-grabs
Difficulty 1/5 Under an hour Newbie friendliness 82/100
lingdojo/kana-dojo#32188 · 1 comment · 5 reactions ·
Maintainers usually reply within 1 day
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
Portkey-AI/gateway#1844 ·
Maintainers usually reply within 1 day
-
needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 61/100
rjsf-team/react-jsonschema-form#5495 ·
Maintainers usually reply within 2 days