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

Aberta
#6,341 0 comentários 0 reações 0 responsáveis Ver no GitHub

Mantenedores costumam responder em até 1 dia

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
2/5
Tempo estimado
1-3 horas
Facilidade para iniciantes
25/100
Tipo de issue
Refatoração
Clareza
Claramente especificada
Status de atividade
Ativa
Stack de tecnologia
python
Domínio
backend

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.

Linguagem predominante
Python
Estrelas
212
Forks
321
Merge médio
1d 7h
PRs com merge (30d)
14

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de learningequality/studio

Todas as issues de learningequality/studio

Issues semelhantes

Mais issues de Python

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.