getappmap / getappmap/appmap-js
UX obstacle: collapse button is not obvious (was: Feature request: can children branches be collapsible?
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 53
- Forks
- 18
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 8
Description
UPD: after talk with @ptrdvrk it was revealed that there is collapse/expand button, but I did not recognize it, because it did not change the cursor over it, thus "not inviting to click". This behaviour is contrary to behaviour of "N children" element which changes the cursor (and which I intuitively used to expand).
As a user
When I inspect the trace
And I expand the children branch to see what is in it and decide I am no more interested
I want to collapse the branch back so it's not occupying the workspace any more
It could be a small button somewhere around the parent node, near the branch root
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by opening the linked AppMap scenario in the trace view and inspecting the existing collapse/expand button near the branch root. Compare its pointer behavior with the “N children” element. Done means the existing collapse control is visibly inviting to click, while preserving the ability to collapse an expanded children branch.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100