inkandswitch / inkandswitch/vscode-hypermerge
Design document history better
Open
- Dominant language
- TypeScript
- Stars
- 30
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Our early user tests made it clear that the current design can be really confusing -- we don't have a clear plan for what to do instead yet.
Contributor guide
No contributing guide indexed for this repository
Research direction
The issue names no files, tests, or entry points; begin by reviewing the current document-history behavior in the VSCode plugin. A replacement design and acceptance criteria are not provided, so what counts as done still needs to be defined.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- design, desktop
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100