Lazy loading of the admin per plugin assembly, gated by enablement and access
Les mainteneurs répondent en général sous 1 jour
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 5/5
- Temps estimé
- Plus d'une semaine
- Accessibilité débutants
- 35/100
- Type d'issue
- Fonctionnalité
- Clarté
- Clairement spécifiée
- Activité
- Active
- Stack technique
- csharp
- Domaine
- backend, developer-experience, frontend
Piste de recherche
Read docs/planning/admin-technical-spec.md sections 2.6, 5.1, and 10.4, along with prerequisite A-18. Start by mapping the admin app build, plugin manifest, navigation, and field, widget, and service registries; the issue names no source files or tests for these entry points. Done means the media admin half loads only when enabled and accessible, passes the listed component and end-to-end coverage, and preserves the first-download size budget.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
Problem
Decision 29 asks that each plugin admin half is one assembly, loaded the first time one of its contributions is used, and row 8.15 that a plugin disabled in a site shows nothing there. The app loads every assembly at start, the sidebar and the registries know the core's contributions only, and nothing reads GET /plugins to gate a contribution.
Proposal
- The app's build gathers the
fluentcms-admin.jsonof every half it references into one file, and lists each half asBlazorWebAssemblyLazyLoad. The shell reads the file at start with one request. - The shell shows a contribution from the manifest only while its server plugin is enabled in the site (
GET /plugins, read once per site) and the caller holds its permission (IAdminAccess). Both are re-read on a site switch. - A half is loaded with
LazyAssemblyLoaderat the moment the table of 2.6 names: its route in the router'sOnNavigateAsync, its field editor or list cell when a form or list with that field type opens, its widget when the home page shows it, its service when it is first asked for. The lookups of the field editor, list cell and filter registries become asynchronous for a type a manifest names; core types stay as they are. Configureruns once per half, into a provider of the half that falls back to the admin's services; the half's components reach it throughIAdminPluginServices(AQ4).- A half whose
AdminRangedoes not hold the running version is not loaded and is listed on an error page; a half that fails to load shows an error state with a retry, not a blank page. - Create
FluentCMS.Plugins.Media.Adminunderadmin/src/plugins/with its manifest, its manifest test and an empty/mediapage with its menu item, so that the loading is proven on a real half and A-20, A-21 and A-22 start from it. A half's project takes the component library withPrivateAssets="compile"or what gives the same result, so that a half cannot name the library's types (#3178).
Acceptance
- The first download of the app does not hold the media half; the network shows it fetched on the first visit of
/media, and once - In a site where the media plugin is disabled the menu item is absent,
/mediaanswers the not-found page, and the half is never fetched - A caller without the page's permission sees no menu item, and the route answers the no-access state
- A service registered in
Configureis injected into a component of the half, and is not in the app's container - A half outside the admin range is listed on the error page, and the rest of the admin works
- The download size budget of A-06 still holds for the first download
- Component tests cover the gating and the registries; an end-to-end case covers the lazy fetch and the disabled site
Design: docs/planning/admin-technical-spec.md, sections 2.6, 5.1 and 10.4 (A-19). Rows 8.15, decision 29. Needs A-18. Size: M.
- Langage dominant
- C#
- Étoiles
- 569
- Forks
- 107
- Merge moyen
- 2 h 49 min
- PR mergées (30 j)
- 397
Préparer son environnement
- Fournit un Dockerfile ou un fichier Docker Compose
- Propose un modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
area:build security type:chore
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
area:sdk security type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
-
area:content security type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 82/100
Les mainteneurs répondent en général sous 1 jour
-
area:build type:bug
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
Les mainteneurs répondent en général sous 1 jour
Toutes les issues de fluentcms/FluentCMS
Issues similaires
-
Difficulté 2/5 1-3 heures Accessibilité débutants 75/100
Les mainteneurs répondent en général sous 1 jour
-
bug needs-triage
Difficulté 2/5 1-3 heures Accessibilité débutants 67/100
microsoft/microsoft-ui-reactor#1567 ·
Les mainteneurs répondent en général sous 1 jour
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulté 2/5 1-3 heures Accessibilité débutants 76/100
openclaw/openclaw-windows-node#2287 · 2 commentaires · 1 réaction ·
Les mainteneurs répondent en général sous 1 jour
-
kind:ux needs-triage
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
elsa-workflows/elsa-foundation#4742 ·
Les mainteneurs répondent en général sous 1 jour
-
priority:P2
Difficulté 2/5 1-3 heures Accessibilité débutants 88/100