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

[QTI] Editing a question keeps the interaction attributes the editor doesn't set

未关闭
  • 哪里不对？
#6,287 0 条评论 1 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@rtibblesbot 已经在做这个了。

开始于 2026年10月5日。

评估

这个 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 its interaction element with only the attributes its builder sets. Any other attribute is dropped.

  • Text entry: buildTextEntryInteractionXML writes only response-identifier and expected-length.
  • Every legacy input question converted by convert.py carries placeholder-text="Enter your answer here", which is lost.
  • Choice: the builder drops class, so class="qti-labels-upper-alpha" is lost.

Errors and logs

None.

Expected behavior

An edit keeps every attribute on the interaction element that the editor doesn't set.

User-facing consequences

Learners see a question that differs from the one uploaded, e.g. an answer field without its placeholder, or choices without their labels.

Steps to reproduce

  1. Open an exercise with a legacy input question that was converted to QTI.
  2. Click Edit and change a hint.
  3. Inspect the emitted raw_data: <qti-text-entry-interaction> has no placeholder-text.

Acceptance Criteria

  • Editing a converted text entry question keeps placeholder-text.
  • Editing a choice question keeps a class on <qti-choice-interaction>.
  • Tests cover both cases through parse, build and assemble.

AI usage

Claude Code found this while reviewing the #6225 branch and drafted this issue. Both losses were reproduced under Jest by parsing an item, rebuilding it with its descriptor and assembling it.

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

环境准备

  • 提供 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 摘要。