Media field editor, list cell and media picker of the admin

Abierto
#3,289 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
48/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
csharp, openapi, tailwindcss

Línea de trabajo

Read docs/planning/admin-technical-spec.md sections 5.2 and 10.4, then inspect the media admin components and FieldEditorBase; the issue names no implementation files or test paths. Check the merged prerequisites A-19, A-21, #3100, #3103 and #3104 before starting. Done means the picker, media field editor and list cell meet the acceptance checks, including keyboard access, route contract tests and the Article.Hero end-to-end case.

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

Descripción

area:admin type:feature

Problem

Row 3.10 asks for a media picker and row 1.4 for media fields. A media field of a form shows its JSON read-only, a list shows the same in its cell, and an editor cannot set the image of Article.Hero.

Proposal

In FluentCMS.Plugins.Media.Admin:

  • IMediaPicker: a dialog over the library with the folder tree, search, upload inline and single or multiple selection, limited to the types the field allows. It reuses the browse component of A-21. Declared with [AdminService], so asking for it loads the half.
  • The field editor of media: a thumbnail with pick, upload, remove, and reorder for a field with several assets; alt text and focal point editable in place with the components of A-50 (PATCH /media/{id}). Read-only, errors, locale and direction as FieldEditorBase gives them.
  • The list cell of media: a thumbnail, with a count for several.
  • Thumbnails from the urls of the Management reads (#3100); labels of the assets of a list are read with one call, not one per row (2.7).
  • The field and the cell fall back to the read-only JSON when the plugin is disabled in the site.

Acceptance

  • On the Blog sample an editor picks an image for Article.Hero from the library, uploads another from the picker, removes it, saves, and the list shows the thumbnail
  • A field that allows images only refuses a PDF in the picker and in the upload
  • Alt text and focal point changed from the field are saved on the asset
  • The picker and the field are usable by keyboard alone, and pass the axe-core check in both themes
  • The built-in Editor and Author pick and upload (#3103)
  • Component tests cover the editor, the cell and the picker; contract tests check the media routes it calls against the OpenAPI document (#3104); an end-to-end case sets the image of Article.Hero

Design: docs/planning/admin-technical-spec.md, sections 5.2 and 10.4 (A-20). Rows 3.10, 1.4, 5.7. Needs A-19 and A-21; #3100, #3103 and #3104 are merged. Size: M.

Lenguaje dominante
C#
Estrellas
569
Forks
107
Merge medio
2 h 49 min
PR fusionados (30 d)
397

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.