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

Offen
#3,446 1 Kommentar 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
4/5
Geschätzter Aufwand
3-5 Tage
Anfängerfreundlichkeit
57/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
csharp
Bereich
frontend, web-dev

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

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).

Vorherrschende Sprache
C#
Sterne
567
Forks
107
Ø Merge
1 Std. 19 Min.
Gemergte PRs (30 T.)
353

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fluentcms/FluentCMS

Alle Issues in fluentcms/FluentCMS

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.