Re-anchor what an undo restores into a book that had no links
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 22/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- typescript
- 领域
- backend
调研方向
The re-anchor pass and its recording live in the host undo/redo path, and BookService re-anchors splits as it serves segments, so start there and trace where a pass is recorded per book. Reproduce with the two examples in the body (delete GEN's only links, edit GEN in Paratext, undo) and confirm the restored links keep old token positions. Done when restored links and splits in a book with no recorded pass are re-anchored to its current text, and books with neither links nor splits before or after the step are untouched.
由索引模型根据 Issue 内容生成。
描述
An undo or redo re-anchors what it restores to each book re-anchored since the step was captured. A re-anchor pass is recorded only over books the draft links into or holds boundary edits in, so a book holding neither at pass time records none. An undo that restores links or splits into such a book leaves them anchored to the text as it stood when the step was captured. Restored links catch up once that book is opened or read again, which happens on the next Scripture save. Restored splits show correctly, because BookService re-anchors splits as it serves segments, but the stored splits stay stale for boundary commands and Save until the book's next pass.
Examples, each while GEN isn't open:
- Delete the only links into GEN, which holds no splits, edit GEN's text in Paratext, then undo. The restored links point at GEN's old tokens.
- Merge away GEN's only split, in a GEN with no links, edit GEN's text in Paratext, then undo the merge. The restored split points at GEN's old token.
The WebView path has the same gap, but #455 removes that path, so only the host needs the fix.
Done when: an undo or redo that restores links or splits into a book with no recorded pass re-anchors them to that book's current text, without re-anchoring books that have neither links nor splits before or after the step.
- 主要语言
- TypeScript
- 星标
- 2
- 派生
- 0
- 平均合并
- 1 天 13 小时
- 30 天内合并 PR
- 73
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南,环境需要你自己搭建:先看它的 README,通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue,再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库,在一个分支上完成修改。
- 提交 Pull Request,并在描述里引用这个 Issue 编号。
sillsdev/interlinearizer-extension 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
sillsdev/interlinearizer-extension#552 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
sillsdev/interlinearizer-extension#548 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 82/100
sillsdev/interlinearizer-extension#543 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 86/100
sillsdev/interlinearizer-extension#537 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
sillsdev/interlinearizer-extension#515 ·
维护者通常 1 天内回复
查看 sillsdev/interlinearizer-extension 的全部 Issue
相似的 Issue
-
bug
难度 1/5 1 小时以内 新手友好度 86/100
awslabs/visual-asset-management-system#937 ·
维护者通常 1 天内回复
-
t0ggles
难度 1/5 1 小时以内 新手友好度 82/100
nolimits4web/swiper#8255 · 1 条评论 ·
维护者通常 15 天内回复
-
render: --variables-file (and --variables <path>) fails with "io.readFile is not a function" since 0.8.212可能已有人在做 @miguel-heygen 今天认领。 未关闭bug triage/needs-triage
难度 2/5 1-3 小时 新手友好度 76/100
heygen-com/hyperframes#6830 ·
维护者通常 1 天内回复
-
bug launch local use
难度 2/5 1-3 小时 新手友好度 65/100
维护者通常 1 天内回复
-
account: profile bug
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 5 天内回复