Find what can leave the first download of the admin

Abierto
#3,354 0 comentarios 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp

Línea de trabajo

Start by locating the spec mentioned in the acceptance criteria and the code or build configuration that defines the admin's first download. Measure its runtime and framework assemblies, Fluent UI, admin assemblies, resources, scripts, and styles; then identify what can be deferred or removed. Update the spec with a per-part table and set the budget based on the measured changes.

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

Descripción

area:admin

Problem

The first download of the admin reached its budget of 3,500,000 B (Brotli) with the component and block editors of A-26 (#3346), which belong to the form and cannot load lazily, so the budget was raised to 3,600,000 B in that pull request. A5 (publishing, versions, bulk) and A6 (administration) add more to the first download.

Proposal

Measure what the first download is made of (the runtime and framework assemblies, Fluent UI, the admin assemblies, resources, scripts and styles) and find what can leave it: pages of administration that can load lazily as the plugin halves do, trimming and feature switches of the runtime, unused components and icons of the component library, resources per culture.

Acceptance

  • A table of the first download by part is in the spec
  • The budget is set from that table, with what was moved out of the first download
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.