mirror of
https://github.com/johannesjo/super-productivity.git
synced 2026-07-26 09:23:50 +00:00
7470c0d16d
The recent appendMissingTask fix (#6) compared payload.taskId against lastSeenTaskIds set to *every* id in taskCache. That treated "first time we see this task in this user's data" as the transition signal, which broke TODAY: - A task that already lives in another project is "known" globally the moment the cache loads. Later, when the user gives it the TODAY tag or sets a dueDay, ANY_TASK_UPDATE fires — but the id is still in lastSeenTaskIds, so wasKnown is true and the chip never appears in the TODAY doc. Same regression for TAG views. Scope lastSeenTaskIds to the *current context's* tasks instead: - PROJECT: tasks whose projectId matches the ctx - TODAY: tasks with the TODAY tag OR a dueDay OR a dueWithTime - TAG: tasks whose tagIds include the ctx id - Subtasks (task.parentId set) are excluded — they flow through insertSubtaskByParent, not through the top-level append path. Now a transition out-of-context → in-context triggers append while in-context updates (time-tracking ticks etc.) still don't replay the chip. The previous "globally new" check is replaced by a per-context set diff, computed via snapshotInContextTaskIds(ctx). |
||
|---|---|---|
| .. | ||
| scripts | ||
| src | ||
| .gitignore | ||
| package-lock.json | ||
| package.json | ||
| tsconfig.json | ||