AI assist admin half: field actions with streaming, and usage (A-38)
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
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- csharp
- Ambito
- ai, api, full-stack, testing
Direzione di ricerca
Start with docs/planning/admin-technical-spec.md, sections 5.1, 5.5 and 10.7, then read the A-51 admin stub and the AI plugin endpoints /ai/actions/{action}, /ai/fields and /ai/usage. The issue describes work across the admin form, streaming action panel, usage page, settings and tests, with dependencies on A-51 and A-34. Done means the acceptance criteria pass, including the sample field action, OpenAPI checks and an end-to-end accepted suggestion.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Problem
Rows 9.14 and 9.15 ask that an editor runs AI actions on the fields a site opted in, and sees the usage. The AI assist plugin has /ai/actions/{action}, /ai/fields and /ai/usage, and its admin half is the stub of A-51. The form has no place for a field action either: FieldActionBase and [FieldAction] are in the contract and the manifest since A-18, and nothing draws, gates or loads one.
Proposal
The form's side, in FluentCMS.Admin (5.1). A field whose type a field action of an enabled half names gets a menu of those actions, for a caller who holds the action's permission. The half loads when the menu is first opened. An action answers a FieldActionResult that leaves the draft or replaces the field's value as an unsaved change; it never saves or publishes.
The half FluentCMS.Plugins.AiAssist.Admin (5.5):
- The actions (rewrite, shorten, expand, fix grammar, title, summary, SEO, translate) on the fields that
GET /ai/fieldsnames for the site, for a caller who holdsai.use. The suggestion streams into a panel (text/event-stream) and goes into the draft only when the user accepts it. - A refusal before the provider is a problem as any other; one after the stream began is its
errorevent. Both are shown in the panel, and the draft is left as it was. - The daily budget of the site (
FCMS1693, a 429) is shown with the problem's own text, and is not sent again as the client sends another 429 again. - Alt text: the server takes
altTextfor an opted-in text field withoptions.mediaId, so the action is offered on such a field with the images of the entry's media fields to choose from. Alt text of the asset itself waits for #3418. /ai/usage, forai.usage.read: the usage read in pages, with filters by principal, action and time, and the totals of the filter. A principal shows by its id until #3418.- The settings of
aiare the generated page of A-34, with the key as a secret. - The half's records are checked against the OpenAPI document.
Acceptance
- On an opted-in field an editor runs an action, sees the suggestion arrive in parts, accepts it and finds it in the draft as an unsaved change; declined, the draft is unchanged
- A field that is not opted in, a site with AI assist off and a caller without
ai.useshow no action, and the half is not fetched - A refusal before the stream, an error within it and the daily budget each show their reason and leave the draft as it was
- Alt text is suggested for an image of the entry on an opted-in text field
- The usage page lists and filters the usage of the site
- The sample half's field action shows in the form through the same seam
- Component tests cover the menu, the panel and the stream against a fake; the API tests check the records against the OpenAPI document and run an action against a stand-in of the provider; an end-to-end case accepts a suggestion
Design: docs/planning/admin-technical-spec.md, sections 5.1, 5.5 and 10.7 (A-38). Rows 9.14, 9.15. Needs A-51, and A-34 for the settings page; #3101, #3103 and #3104 are merged; #3418 for alt text of an asset and for names in the usage. Size: M.
- Lingua principale
- C#
- Stelle
- 567
- Fork
- 107
- Merge medio
- 1h 19m
- PR unite (30g)
- 353
Preparare l'ambiente
- Include un Dockerfile o un file Docker Compose
- Ha un modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di fluentcms/FluentCMS
-
area:localization plugin type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
area:storage type:bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 48/100
I maintainer di solito rispondono entro 1 giorno
-
area:testing type:bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 72/100
I maintainer di solito rispondono entro 1 giorno
-
area:api area:publishing type:feature
Difficoltà 4/5 3-5 giorni Idoneità per principianti 55/100
fluentcms/FluentCMS#3473 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
area:storage plugin type:bug
Difficoltà 5/5 Più di una settimana Idoneità per principianti 35/100
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di fluentcms/FluentCMS
Issue simili
-
fix(ocr): compile the Tesseract-free pipeline with Tokio runtimeForse già presa @Goldziher l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
priority:P2
Difficoltà 2/5 1-3 ore Idoneità per principianti 82/100
-
lompotc silently drops Java/C# class members past 128 instead of erroring, as its header claimsApertabug sev-5 vm
Difficoltà 2/5 1-3 ore Idoneità per principianti 76/100
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
-
area:jobads-cv bug FE mvp P3
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
klasolsson81/jobbliggaren#2271 ·
I maintainer di solito rispondono entro 1 giorno