Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

[QTI] Editing a question keeps the item-level content the editor doesn't write

未关闭
#6,290 0 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@rtibblesbot 已经在做这个了。

开始于 2026年10月6日。

评估

难度
3/5
预计耗时
1-2 天
新手友好度
55/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
活跃
技术栈
javascript, python
领域
frontend

调研方向

Start with contentcuration/frontend/shared/views/QTIEditor/serialization/assembleItem.js, especially assembleItemXml, and trace how useQtiItem opens and emits the item. Add or locate tests that open an item containing each listed stylesheet, modal-feedback element, or root attribute, then inspect emitted raw_data. Done means all three are preserved after editing, with tests covering each case.

由索引模型根据 Issue 内容生成。

描述

bug

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Target branch: unstable

Observed behavior

The first edit to a QTI question rewrites <qti-assessment-item> with only what assembleItemXml writes: the root's identifier, title, language and fixed flags, response and outcome declarations, the body, the hint catalog and response processing. Anything else outside <qti-item-body> is dropped:

  • <qti-stylesheet>
  • <qti-modal-feedback>
  • root attributes such as xsi:schemaLocation

Errors and logs

None. The content is lost without a warning.

Expected behavior

An edit keeps every element and attribute of <qti-assessment-item> outside <qti-item-body> that the editor doesn't write, or the item shows unsupportedItemMessage$() read-only, as #6225 does for bodies the editor can't reproduce.

User-facing consequences

An item uploaded with ricecooker that carries a stylesheet or modal feedback loses it the first time an author changes anything, such as a hint. Learners then see the question unstyled, or get no feedback after answering.

Steps to reproduce

  1. Open an exercise containing a QTI choice item with <qti-stylesheet href="style.css" type="text/css"/> before <qti-item-body> and a <qti-modal-feedback> after it.
  2. Click Edit and remove a hint.
  3. Inspect the emitted raw_data: it has no <qti-stylesheet> and no <qti-modal-feedback>.

Acceptance Criteria

  • Editing an item with a <qti-stylesheet> doesn't lose it.
  • Editing an item with a <qti-modal-feedback> doesn't lose it.
  • Editing an item whose root carries xsi:schemaLocation doesn't lose it.
  • Tests cover each case above, from opening the item to the emitted raw_data.

AI usage

Claude Code found this while reviewing the #6225 branch and drafted this issue. The loss was reproduced under Jest on unstable by opening such an item through useQtiItem, removing a hint and reading the assembled XML.

主要语言
Python
星标
191
派生
308
平均合并
2 天 14 小时
30 天内合并 PR
57

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

learningequality/studio 的其他 Issue

查看 learningequality/studio 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。