Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[QTI] Text entry answers are merged and reordered when the first answer has surrounding space

Aperta
  • Qualcosa non va?
#6,309 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
2/5
Tempo stimato
1-3 ore
Idoneità per principianti
15/100
Tipo di issue
Bug
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
javascript, xml
Ambito
frontend

Direzione di ricerca

The bug is in _extractAnswers in interactions/textEntry/parse.js, which compares the trimmed qti-value with the untrimmed first map-key. Reproduce it with a Jest test using the declaration from the issue, then check that the output is [[' Paris', false], ['Paris', true], ['Paris', false]] and that opening the item emits no update:rawData. The issue states it is not open for contribution, so confirm with maintainers before starting.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug DEV: frontend

❌ 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

  • A base-type="string" declaration whose map-keys are Paris (case-insensitive), Paris (case-sensitive), Paris (case-insensitive) opens in the Text entry editor as two answers: Paris, Paris.
  • The case-sensitive Paris answer is dropped; the next save writes the merged list.
  • Cause: _extractAnswers (interactions/textEntry/parse.js) compares the trimmed <qti-value> with the untrimmed first map-key, so the editor-shaped check fails and answers are read by value instead.

Expected behavior

  • Answers open as stored: Paris, Paris (case-sensitive), Paris, in that order.

User-facing consequences

  • An author who edits such a question loses an answer and its case-sensitivity without being told.

Steps to reproduce

  1. Call _extractAnswers on the declaration: 
    <qti-response-declaration identifier="RESPONSE" cardinality="single" base-type="string">
  <qti-correct-response><qti-value> Paris</qti-value></qti-correct-response>
  <qti-mapping default-value="0">
    <qti-map-entry map-key=" Paris" mapped-value="1" case-sensitive="false"/>
    <qti-map-entry map-key="Paris" mapped-value="1" case-sensitive="true"/>
    <qti-map-entry map-key="Paris" mapped-value="1" case-sensitive="false"/>
  </qti-mapping>
</qti-response-declaration>
  2. It returns [['Paris', false], [' Paris', false]] as [value, caseSensitive].

Acceptance Criteria

  • The declaration above reads as [[' Paris', false], ['Paris', true], ['Paris', false]].
  • Opening such an item in edit mode emits no update:rawData.

AI usage

Claude Code found this while self-reviewing #6282 and drafted the issue; the bug was reproduced against unstable with a Jest test.

Lingua principale
Python
Stelle
191
Fork
308
Merge medio
2g 6h
PR unite (30g)
65

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di learningequality/studio

Tutte le issue di learningequality/studio

Issue simili

Altre issue su Python

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.