Media library of the admin: grid and list, folders, search, upload by drop and paste

Offen
#3,290 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Maintainer antworten meist innerhalb von 1 Tag

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
5/5
Geschätzter Aufwand
Über eine Woche
Anfängerfreundlichkeit
35/100
Issue-Typ
Feature
Klarheit
Größtenteils klar
Aktivitätsstatus
Aktiv
Tech-Stack
csharp

Rechercherichtung

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.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

area:admin type:feature

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 (FCMS1581 to FCMS1584) 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.

Vorherrschende Sprache
C#
Sterne
569
Forks
107
Ø Merge
2 Std. 49 Min.
Gemergte PRs (30 T.)
397

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus fluentcms/FluentCMS

Alle Issues in fluentcms/FluentCMS

Ähnliche Issues

Weitere Issues zu C#

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.