Lazy loading of the admin per plugin assembly, gated by enablement and access
Los mantenedores suelen responder en 1 día
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 5/5
- Tiempo estimado
- Más de una semana
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bien especificado
- Estado de actividad
- Activo
- Stack tecnológico
- csharp
- Área
- backend, developer-experience, frontend
Línea de trabajo
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.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
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.
- Lenguaje dominante
- C#
- Estrellas
- 569
- Forks
- 107
- Merge medio
- 2 h 49 min
- PR fusionados (30 d)
- 397
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:host area:operations type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area:build security type:chore
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area:sdk security type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
-
area:content security type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100
Los mantenedores suelen responder en 1 día
-
area:build type:bug
Dificultad 2/5 1-3 horas Aptitud para principiantes 78/100
Los mantenedores suelen responder en 1 día
Todos los issues de fluentcms/FluentCMS
Issues similares
-
bug needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 67/100
microsoft/microsoft-ui-reactor#1567 ·
Los mantenedores suelen responder en 1 día
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 76/100
openclaw/openclaw-windows-node#2287 · 2 comentarios · 1 reacción ·
Los mantenedores suelen responder en 1 día
-
kind:ux needs-triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 66/100
elsa-workflows/elsa-foundation#4742 ·
Los mantenedores suelen responder en 1 día
-
priority:P2
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
[LANG] Add support for C# (.cs)Abiertoenhancement good first issue help wanted new-language
Dificultad 2/5 1-3 horas Aptitud para principiantes 82/100