bjsi / bjsi/incremental-writing
Dismissing "next repetition" mess with which is the current repetition
- Dominant language
- TypeScript
- Stars
- 209
- Forks
- 16
- PR merge metrics
- No merged PRs in 30d
Description
version: 0.4
Let's say we have a queue like:
| Link | Priority | Notes | Interval | Next Rep |
|------|----------|-------|---------|----------|
| [[IW-test 3]] | 20 | | 1 | 2021-09-28 |
| [[IW-test 2]] | 24 | | 1 | 2021-09-28 |
| [[IW-test 1]] | 34 | | 1 | 2021-09-28 |
| [[IW-test 4]] | 12 | | 1 | 2021-09-28 |
The display bar shows "Rep: IW-test 4"
by the way, the ordering is strange (and undesirable) to me they where queued as 1, 2, 3, 4 but priority lead to 4, 3, 2, 1 i.e. latest queued is scheduled first. This is a LIFO queue and I would expect the reverse i.e. a FIFO queue. Is there a way to change this through configuration ?
Now Invoke "Next Repetition" **_but cancel it (with ESC)_**. This lead to this queue:
| Link | Priority | Notes | Interval | Next Rep |
|------|----------|-------|---------|----------|
| [[IW-test 3]] | 24.98 | | 1 | 2021-09-28 |
| [[IW-test 2]] | 49.95 | | 1 | 2021-09-28 |
| [[IW-test 1]] | 74.93 | | 1 | 2021-09-28 |
| [[IW-test 4]] | 99.9 | | 1 | 2021-09-28 |
Notice that priority changed even so the operation has been canceled.
Also is it expected to have decimal on the priority ?
The display bar still shows "Rep: IW-test 4"
Finally invoke "Dismiss Current Repetition". This lead to this queue:
| Link | Priority | Notes | Interval | Next Rep |
|------|----------|-------|---------|----------|
| [[IW-test 2]] | 49.95 | | 1 | 2021-09-28 |
| [[IW-test 1]] | 74.93 | | 1 | 2021-09-28 |
| [[IW-test 4]] | 99.9 | | 1 | 2021-09-28 |
notice that "IW-test 3" has been removed instead of "IW-test 4"
The display bar shows "Rep: IW-test 4" (which is indeed the result of the wrong removal)
Contributor guide
No contributing guide indexed for this repository
Research direction
Reproduce the documented queue with four links in version 0.4, then inspect the implementation of “Next Repetition” and “Dismiss Current Repetition.” Verify that cancelling does not change priorities and that dismissing removes the repetition shown in the display bar rather than a different queue entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100