Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

Collection list view doesn't refresh after a save; requires a manual reload

Abierto
  • ¿Algo no está bien?
#1,633 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
58/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
typescript
Área
frontend

Línea de trabajo

Start with the admin UI collection list view and the Collection configuration described in config.d.ts; trace what happens when an entry is saved and the user returns to the list. Reproduce the reported create and title-change cases, including an active title search or sort, and verify that the list reflects the saved data without a manual reload.

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

Descripción

Installed: @keystatic/[email protected], @keystatic/[email protected].

Repro steps

  1. Open a collection's list view in the admin UI.
  2. Open an existing entry, or create a new one, and save it.
  3. Without reloading the page, return to the collection list view.

Expected: the saved/new entry appears in the list (and any active sort/filter reflects it) without a manual page reload.

Actual: the list still shows the pre-save state. A newly created entry is absent, or a title change isn't reflected, until the browser tab is manually reloaded. Observed during a live editing session: a newly created entry did not appear in the collection list, including under a title search, until the page was reloaded. No data was lost; the save had succeeded.

Note: this was observed in a live editing session, not reproduced in a separate local setup.

Why this looks like a genuine gap rather than app misconfiguration: the Collection config type (@keystatic/core 0.6.9, config.d.ts) exposes no onSave hook, no cache-invalidation option, and no config surface for the list view's data-fetching behavior at all (label, path, entryLayout, format, previewUrl, columns, template, parseSlugForSort, slugField, schema). There is nothing a consuming app could set to force a list refetch after a write.

Context: we run this on a multi-locale marketing site's editorial workflow, where a save appearing to "vanish" from the list made an editor reasonably (but wrongly) suspect data loss.

Related but distinct: #1594 (stale local draft shadows the file on disk) is about a stale draft overwriting on save; this report is only about the list view not refetching after a successful save.

Lenguaje dominante
TypeScript
Estrellas
2.5k
Forks
176
Merge medio
5 h 46 min
PR fusionados (30 d)
3

Preparar el entorno

Este proyecto no incluye contenedor de desarrollo, Dockerfile ni guía de contribución, así que la configuración corre por tu cuenta: empieza por su README y consulta nuestra guía para la primera contribución para los pasos generales.

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 Thinkmill/keystatic

Todos los issues de Thinkmill/keystatic

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.