dotnet new fluentcms-admin, and the admin in dotnet new fluentcms (A-44)

Aperta
#3,461 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
csharp

Direzione di ricerca

Start with docs/planning/admin-technical-spec.md sections 6.2, 6.4 and 10.8, then read the existing templates under templates/fluentcms and the checks in templates/test-templates.sh and eng/fresh-machine.ps1. Implement both admin template paths and update the plugin and template READMEs as described. Done means all listed acceptance checks pass, including trimmed publishing, admin routes and the CI time limit.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

area:admin area:build type:feature

Problem

Row 11.1 asks for three templates: fluentcms, an API host with the admin; fluentcms-admin, a standalone admin; and fluentcms-plugin. FluentCMS.Templates has two of them, and the host has no admin:

  • fluentcms writes a host of FluentCMS.Core, a data provider and the media, search and webhooks plugins (templates/fluentcms/FluentCms-App.csproj), whose Program.cs maps the APIs and the OpenAPI document and nothing under /admin. Its options are --provider and --sample (templates/fluentcms/.template.config/template.json).
  • fluentcms-admin does not exist. A team with admin halves of its own, the output of dotnet new fluentcms-plugin among them, has no app to put them in: the only app is FluentCMS.Admin.App of this repository, which is not a package.
  • The checks read nothing of the admin. templates/test-templates.sh creates the six hosts and the plugin with and without its half, starts the SQLite hosts and reads the Delivery API; eng/fresh-machine.ps1 does the same from packages on a clean machine. Section 6.2 asks that the Templates job reads /admin/config.json and /admin/.

Proposal

  • dotnet new fluentcms-admin -n <name> writes a WebAssembly app like FluentCMS.Admin.App: Program.cs with AddFluentCmsAdmin; package references to FluentCMS.Admin, the rich text editor, the administration assembly and the six first-party halves, each with its BlazorWebAssemblyLazyLoad line; the trimmed publish with trim warnings as errors; wwwroot/config.json for a local API host and index.html; a launch profile for dotnet watch; and a README on adding a half of the team's own, on the two settings the API host needs for the app's origin (6.4), and on hosting the result as static files (docs/admin-hosting.md) or from the team's API host with FluentCMS.Admin.Hosting serving this project. It has no option: a team removes the lines of a half it does not want.
  • dotnet new fluentcms gains --admin, on by default: the package FluentCMS.Admin.Hosting, cms.AddAdmin(), app.MapFluentCmsAdmin(), the keys of FluentCms:Admin in the settings, and a section of the README on opening /admin and on the first administrator. It serves the prebuilt build of the package (A-55). --admin false leaves each of these out.
  • The plugin template's README says how to put its half into an app made with fluentcms-admin.
  • The checks. test-templates.sh creates the hosts with the admin and two of them without, builds each with warnings as errors, starts the SQLite hosts and reads /admin/config.json and /admin/; it creates the app, publishes it trimmed, adds the plugin template's half to it and checks that the build stops without the lazy line and passes with it; and it starts one host that serves the template's app in place of the prebuilt one. eng/fresh-machine.ps1 reads /admin/ of its Blog host. The job's time before and after is in the pull request.

Acceptance

  • dotnet new fluentcms builds with warnings as errors for each provider and sample, and its SQLite host answers /admin/ with the base set and /admin/config.json with the host's origin and the client fluentcms-admin
  • dotnet new fluentcms --admin false writes no reference to the admin, in the project, the code, the settings or the README, and /admin answers 404
  • dotnet new fluentcms-admin builds with warnings as errors and publishes trimmed without a trim warning, and the published app holds the manifests of the six halves
  • The half of dotnet new fluentcms-plugin added to that app is listed in its gathered manifests, and the build stops when its lazy line is missing
  • A host of the template serves the template's app through FluentCMS.Admin.Hosting
  • The Templates job and the Fresh machine jobs run these checks, and the Templates job stays within its 30 minutes
  • The READMEs of the three templates and templates/README.md describe the admin parts

Design: docs/planning/admin-technical-spec.md, sections 6.2, 6.4 and 10.8 (A-44). Rows 11.1, 11.4, 8.17; decision 5. Needs A-55 for --admin, and A6 merged for the packages it references. Size: M.

Lingua principale
C#
Stelle
567
Fork
107
Merge medio
1h 19m
PR unite (30g)
353

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di fluentcms/FluentCMS

Tutte le issue di fluentcms/FluentCMS

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.