Nothing is drawn while a lazy assembly of the admin loads on a deep link or reload

Abierto
#3,446 1 comentario 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
57/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
frontend, web-dev

Línea de trabajo

Start in AdminApp.razor and trace how the router handles navigation and announces existing loading states. Check the end-to-end tests and their slow mode setup; add coverage for reloading an administration or half route and navigating to an unloaded assembly. Done means the shell and an announced loading state appear promptly in both cases until the page loads.

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

Descripción

area:admin type:bug

Problem

On a deep link or a reload of a route whose assembly loads lazily, the admin draws nothing until the shell's reads and the fetch of the assembly have ended: the router in AdminApp.razor has no Navigating content, so the header, the sidebar and a status are all absent meanwhile. A plugin half has behaved so since A3. With A-51 (#3429) the nine routes of core's administration area load lazily too, so an administrator on a slow connection who reloads /users looks at an empty page. On a navigation inside the app the page before stays on screen with no sign of progress while the file downloads, which invites a second click.

Proposal

Show the shell with a loading state while a navigation waits for a lazy assembly, on a first load and inside the app, and announce it as the other loading states are announced.

Acceptance

  • A reload of an administration route and of a half's route shows the shell and a loading state until the page is there
  • A navigation inside the app to a route whose assembly is not loaded shows progress at once
  • An end-to-end case in slow mode covers both

From the review of #3438 (#3429, A-51).

Lenguaje dominante
C#
Estrellas
567
Forks
107
Merge medio
1 h 19 min
PR fusionados (30 d)
353

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 fluentcms/FluentCMS

Todos los issues de fluentcms/FluentCMS

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.