fix(panel): 从 KV 恢复终态条目时保留 endedAt(#26) - #28
Merged
Merged
Conversation
Owner
|
感谢你的BUG修复和新功能添加,我会尽快上线新版本,感谢你的支持 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
修复
从 KV 恢复终态条目时,
loadEntries()通过upsertSubEntry()重建 map,而后者把endedAt视为「本次 upsert 的时刻」:恢复路径没有existing,持久化的endedAt被写成Date.now(),渲染侧elapsed = (entry.endedAt ?? now()) - entry.startedAt于是随每次进入会话被重置并持续变大(实测21.14s → 10m28s)。SubEntryPatch允许透传endedAt?;upsertSubEntry:endedAt: existing?.endedAt ?? partial.endedAt ?? now——事件路径不携带endedAt,行为不变;恢复路径保留持久化值。引入自
0ccba2d(v1.6.0);仅影响内存显示,不污染持久化数据(落盘走mergeSubEntries,本就会保留原值),无需数据迁移。验证
endedAt: 500的终态条目后仍为500。npm run typecheck/npm run build/npm test:29 项测试全部通过。备注