PT9 import report doesn't say which words it dropped
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 51/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- react, typescript
调研方向
Start with src/components/modals/Pt9ImportModal.tsx at the report display around lines 310–311, then trace where import drops and formMismatch are recorded. The issue proposes recording verse references, cluster forms, and drop reasons, with a separate count for parses dropped while words are kept. Done means users can inspect those drops in the modal; the issue does not name the report-generation files or tests.
由索引模型根据 Issue 内容生成。
描述
The import modal lists how many clusters were dropped for each reason:
https://github.com/sillsdev/interlinearizer-extension/blob/be80462fab5af0adea8b379651242e2eeae2d22d/src/components/modals/Pt9ImportModal.tsx#L310-L311
It never says which verses or words they were, so a user can't find or redo what was lost.
Why it matters now
#637 drops a parse whose morpheme forms don't spell out its token, even when a word gloss at the same range keeps its gloss. Deliberate analyses can land there:
| Word | Parse | Why the forms differ from the word |
|---|---|---|
evler (Turkish) |
ev + -lar |
One suffix form used across vowel harmony |
running |
run + -ing |
The stem's citation form |
sheep (plural) |
sheep + -Ø |
Zero morpheme |
anak-anak (Indonesian) |
anak + ~ |
Reduplication marker |
Each of these only adds 1 to the formMismatch count:
- It looks the same as a stale or mistyped parse.
- The user isn't told that the word gloss survived without its morphemes.
Proposed
Drafted by Claude; not human-reviewed.
- Record each drop in the book report with its verse ref, the cluster's forms, and the drop reason.
- Count "parse dropped, word kept" separately from
formMismatch, since it is a partial loss. - List the drops in the modal (collapsed by default, or copyable), not only in the logged JSON.
Out of scope
report.senses(glosses whose lexeme or sense reference is missing fromLexicon.xml) is also not shown. A TODO already ties that to #280:
https://github.com/sillsdev/interlinearizer-extension/blob/be80462fab5af0adea8b379651242e2eeae2d22d/src/components/modals/Pt9ImportModal.tsx#L77
- 主要语言
- TypeScript
- 星标
- 2
- 派生
- 0
- 平均合并
- 1 天 1 小时
- 30 天内合并 PR
- 105
环境准备
这个项目没有提供开发容器、Dockerfile 或贡献指南，环境需要你自己搭建：先看它的 README，通用步骤见我们的新手贡献指南。
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
sillsdev/interlinearizer-extension 的其他 Issue
-
Update menu items可能已有人在做 @imnasnainaec 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 65/100
sillsdev/interlinearizer-extension#613 · 已指派 1 人 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
sillsdev/interlinearizer-extension#548 ·
维护者通常 1 天内回复
-
Make it clear that a stale analysis is re-applied to a word chosen in the text可能已有人在做 关联的 PR 仍在进行中或已合并。 未关闭
难度 2/5 1-3 小时 新手友好度 86/100
sillsdev/interlinearizer-extension#537 · 已指派 1 人 ·
维护者通常 1 天内回复
-
bug
难度 2/5 1-3 小时 新手友好度 76/100
sillsdev/interlinearizer-extension#515 ·
维护者通常 1 天内回复
-
Re-anchor a session's book when the view first opens it可能已有人在做 @alex-rawlings-yyc 今天认领。 未关闭
sillsdev/interlinearizer-extension#645 · 已指派 1 人 ·
维护者通常 1 天内回复
查看 sillsdev/interlinearizer-extension 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 78/100
维护者通常 1 天内回复
-
binding:python bug
难度 2/5 1-3 小时 新手友好度 82/100
维护者通常 1 天内回复
-
enhancement
难度 2/5 1-3 小时 新手友好度 78/100
coollabsio/orbit#72 ·
维护者通常 1 天内回复
-
Bug
难度 2/5 1-3 小时 新手友好度 67/100
维护者通常 1 天内回复
-
bug needs-triage potential-regression
难度 2/5 1-3 小时 新手友好度 78/100
aws/aws-sdk-js-v3#8408 ·
维护者通常 1 天内回复