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

Optimistic store update is hidden after a local derived-store write inside an action

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

Línea de trabajo

The report provides a playground reproduction but names no source files or tests. Start by running the reproduction and tracing how createOptimisticStore handles the local derived-store write and the following optimistic write while the action is pending. Done means the view shows New / saving: true during the save and reconciles to the authoritative source after completion.

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

Descripción

Describe the bug

On experimental build 6f77b1b, writing a client-only flag to a writable derived store inside an action prevents a subsequent optimistic store update from appearing while that action is pending.

The optimistic store wraps the derived store. The local write only sets failed = false; the optimistic write changes title to "New" and sets saving = true. A direct JSX binding keeps showing "Old" and saving: false until the action completes.

const [cards, setOptimistic] = createOptimisticStore(local);

const save = action(function* () {
  setLocal(draft => { draft[0].failed = false; });
  setOptimistic(draft => {
    draft[0].title = "New";
    draft[0].saving = true;
  });
  yield completion;
});

Removing the setLocal call makes the optimistic update appear. The reproduction uses a normal component and direct text binding, without For, Show, routing, or external data loading.

Your Example Website or App

https://s.olid.uk/id/d27cf7de-2cc1-45a8-9144-6868e307a78f

Steps to Reproduce the Bug or Issue
  1. Open the playground and click Run once.
  2. During the two-second simulated save, observe Old / saving: false instead of the optimistic values.
  3. After completion, the display changes to New / saving: false. The report records both states.
  4. Reload and remove the marked setLocal call to compare: the optimistic values appear during the save.
Expected behavior

The optimistic view should immediately show New / saving: true while the action is pending, including when the action first writes to its underlying local store. After completion, it should follow the authoritative source with the temporary saving flag removed.

Platform
Additional context

The identical reproduction with published RC.13 is here: https://s.olid.uk/id/cf602874-eee9-400c-bd96-3022a77b7291

With the local flag write RC.13 6f77b1b
During the pending action New / saving: true Old / saving: false
After completion Old / saving: false New / saving: false

RC.13 shows the optimistic update correctly but suppresses the later source reconciliation discussed in #3733. The newer build reconciles correctly after completion, but loses the optimistic display while pending. Both playgrounds have Tailwind disabled.

Lenguaje dominante
TypeScript
Estrellas
36.1k
Forks
1.1k
Merge medio
11 h 42 min
PR fusionados (30 d)
326

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 solidjs/solid

Todos los issues de solidjs/solid

Issues similares

Más issues de TypeScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.