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

Abierto
#6,341 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
2/5
Tiempo estimado
1-3 horas
Aptitud para principiantes
25/100
Tipo de issue
Refactorización
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
python
Área
backend

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
Python
Estrellas
212
Forks
321
Merge medio
1 d 7 h
PR fusionados (30 d)
14

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de learningequality/studio

Todos los issues de learningequality/studio

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.