Preview pane: a late ready kept through a navigation, and a new token on the form's reload
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
- 47/100
Línea de trabajo
Read ContentPreview.razor and its LoadedAsync method, then inspect ContentForm.razor and the existing component tests for both behaviors. Trace how ready state and the pane token change across navigation and form reload; use the tests to check the acceptance cases, including the documented contract limit in section 4.12 if that approach is chosen.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
Two cases of the preview pane that the review of #3437 (#3403) left for later:
- A page that says
readyafter its own load keepsreadythrough a navigation to a page without the contract. The pane forgetsreadywhen the frame loads a page with noreadysince the previous load (ContentPreview.razor,LoadedAsync). For the order load 1,ready1, load 2 with noready, the flag is still true fromready1 when load 2 arrives, so the next save postsrefreshto a page that ignores it: nothing reloads and the Silent note never shows. Front ends that postreadyafter hydration or after a data fetch send it in that order. The rule cannot tell this from areadythat is merely delivered late, which #3403 settled; the component test and the end-to-end case cover onlyreadybefore the load. - Reloading the form re-creates the open pane, which mints again while its token lasts.
ContentForm.razorsets its read to null before the first await ofLoadAsync, so the pane's condition turns false and the pane is disposed; when the read ends a new pane mints as it opens. The conflict dialog's Reload and Try again, on the same entry and locale, so give a new token that cannot be revoked and reload the frame.
Proposal
- Tell the two orders apart, or ask a contract page to post
navigatedbefore a full navigation and say so in section 4.12; whichever is chosen, record the limit in 4.12. - Keep the pane, its answer and its token across a reload of the same entry, site and locale.
Acceptance
- A page that says
readyafter its load and then navigates to a page without the contract is reloaded on the next save, or section 4.12 states the limit and the contract asks fornavigated - The conflict dialog's Reload and Try again on the same entry and locale mint no token while the shown one lasts
- Component tests for both, and an end-to-end case for the first if the contract changes
From the second review of #3437 (#3403).
- Lenguaje dominante
- C#
- Estrellas
- 567
- Forks
- 107
- Merge medio
- 1 h 19 min
- PR fusionados (30 d)
- 353
Preparar el entorno
- Incluye un Dockerfile o un archivo de Docker Compose
- Tiene una plantilla de pull request
- Leer la guía de contribución
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de fluentcms/FluentCMS
-
area:localization plugin type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area:storage type:bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
Los mantenedores suelen responder en 1 día
-
area:testing type:bug
Dificultad 3/5 1-2 días Aptitud para principiantes 72/100
Los mantenedores suelen responder en 1 día
-
area:api area:publishing type:feature
Dificultad 4/5 3-5 días Aptitud para principiantes 55/100
fluentcms/FluentCMS#3473 · 1 comentario ·
Los mantenedores suelen responder en 1 día
-
area:storage plugin type:bug
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
Los mantenedores suelen responder en 1 día
Todos los issues de fluentcms/FluentCMS
Issues similares
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimePosiblemente ocupada @Goldziher la tomó hoy. Abierto
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
priority:P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
-
lompotc silently drops Java/C# class members past 128 instead of erroring, as its header claimsAbiertobug sev-5 vm
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 85/100
-
area:jobads-cv bug FE mvp P3
Dificultad 2/5 1-3 horas Aptitud para principiantes 77/100
klasolsson81/jobbliggaren#2271 ·
Los mantenedores suelen responder en 1 día