Media library of the admin: grid and list, folders, search, upload by drop and paste
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
Línea de trabajo
Start with docs/planning/admin-technical-spec.md, sections 4.14, 5.2 and 10.4, and the existing media routes and admin menu. Implementing this page spans browsing, uploads, folders, accessibility, and several kinds of tests; first check the dependency on A-19 and the related issues. Done means meeting the listed acceptance checks, including route contract tests against the OpenAPI document.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
Problem
Row 3.15 asks for a media library, row 5.2 for upload by drag-and-drop and paste, and row 5.4 for folders. The media routes exist and the admin has no page over them: an asset is uploaded with the CLI or a direct call.
Proposal
The page /media of FluentCMS.Plugins.Media.Admin, with its menu item in the media section:
- A browse component, which the picker of A-20 reuses: grid and list views of a folder, the folder tree, search, filters by type and tag, and paging (
GET /media,GET /media/folders). The view, the folder and the filters are in the query string. - Upload by button, by dropping files on the page and by pasting. Each file shows its state (waiting, uploading, done, refused) and its refusal (
FCMS1581toFCMS1584) by name; a refused file does not stop the others. The state is per file and not per byte: the browser's fetch reports no upload progress, and the access token stays in C#. Drop and paste take a small script module of the half, which joins the allow-list of 3.1. - Folders: create, rename, move, and delete an empty one.
- Selecting an asset opens the detail panel of A-50; until it lands the panel shows the title, the type and the size.
Acceptance
- An editor browses folders, switches between grid and list, searches, filters by type and tag, and pages
- Ten files dropped at once upload with a state per file, and one of a refused type is named with its reason while the nine others finish
- An image pasted from the clipboard uploads into the open folder
- A folder is created, renamed, moved and deleted; deleting one with assets says why it is refused
- The page is usable by keyboard alone and passes the axe-core check in both themes and in the right-to-left pseudo-culture
- Component tests cover the browse component and the upload states; contract tests check the routes against the OpenAPI document (#3104); an end-to-end case uploads by drop and moves an asset's folder
Design: docs/planning/admin-technical-spec.md, sections 4.14, 5.2 and 10.4 (A-21). Rows 3.15, 5.2, 5.4. Needs A-19; #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
- 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
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 75/100
Los mantenedores suelen responder en 1 día
-
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