michaelpb / michaelpb/whiteboard
False positives in trying to close without saving for deck
Open
Nobody has claimed this yet.
bug
- Dominant language
- JavaScript
- Stars
- 26
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Needs better diffing algo for determining if saved yet or not
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 locating the deck flow that checks whether a presentation can be closed without saving, then trace how its current diffing determines saved state. Reproduce a false positive and establish a comparison that distinguishes unchanged and unsaved decks; done means closing an unchanged deck no longer warns while actual changes still do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100