[QTI] Remove the server wait for possibly stale cached assessment items

Aperta
#6,341 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
25/100
Tipo di issue
Refactoring
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
python
Ambito
backend

Direzione di ricerca

Read the startup cleanup and its tests from issue #6340, then identify the EditModal test that checks complete when loading fails. Remove the startup cleanup and its cleanup tests while preserving that EditModal behavior; done means startup no longer touches the assessment item table and the acceptance criteria pass. The issue says this work is not open for contribution, so find a suitable issue through the contributing guidelines.

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

Descrizione

DEV: frontend

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

Overview

This is a reminder. The checks from #6340 only matter while caches may hold legacy items, or edits from tabs still on the old assets. Both come from the weeks around the QTI release. Once active users have opened their exercises on the new assets, remove them.

Part of #6337. Ships in the cleanup release: the first hotfixes release after the QTI release has been in production for about a month.

Complexity: Low
Target branch: hotfixes

Context
  • #6340 makes loadAssessmentItems wait for the server on an exercise's first open after a page load, and when its cached items include a legacy one.
  • An exercise that isn't opened between the QTI release and the cleanup release keeps its cached legacy items. When it's opened, the background refresh updates IndexedDB but not the open exercise, so its legacy items show as unsupported until it's reopened.
The Change
  • Delete #6340's checks and their tests.
Acceptance Criteria
  • loadAssessmentItems no longer waits for the server on a first open after a page load, or when cached items are legacy
  • #6340's tests are removed

AI usage

I outlined the approach. Claude drafted the issue, which I then checked and corrected for accuracy.

Lingua principale
Python
Stelle
212
Fork
321
Merge medio
1g 7h
PR unite (30g)
14

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.