Re-anchor what an undo restores into a book that had no links
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 22/100
- Tipo de issue
- Error
- Claridad
- Bastante claro
- Estado de actividad
- Activo
- Stack tecnológico
- typescript
- Área
- backend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- TypeScript
- Estrellas
- 2
- Forks
- 0
- Merge medio
- 1 d 9 h
- PR fusionados (30 d)
- 78
Preparar el entorno
Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de sillsdev/interlinearizer-extension
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 68/100
sillsdev/interlinearizer-extension#552 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
sillsdev/interlinearizer-extension#548 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
sillsdev/interlinearizer-extension#543 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
sillsdev/interlinearizer-extension#537 ·
Los mantenedores suelen responder en 1 día
-
bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
sillsdev/interlinearizer-extension#515 ·
Los mantenedores suelen responder en 1 día
Todos los issues de sillsdev/interlinearizer-extension
Issues similares
-
Add: Disco Mix SDAbiertocheck:passed streams:add
Dificultad 2/5 1-3 horas Aptitud para principiantes 62/100
Los mantenedores suelen responder en 1 día
-
level2 nsoc26
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
GauravKarakoti/SecureFlow#1488 ·
Los mantenedores suelen responder en 1 día
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 72/100
deltachat/deltachat-desktop#6914 ·
Los mantenedores suelen responder en 2 días
-
area:cli bug P4
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
bug from-studio
Dificultad 2/5 1-3 horas Aptitud para principiantes 65/100
esengine/DeepSeek-Reasonix#14868 ·
Los mantenedores suelen responder en 1 día