Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

apptest: the generic UI crud flow is silently not registered for an entity without an editable text field (relation-keyed documents get no UI coverage)

Aperta
  • Qualcosa non va?
#7,910 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à
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
48/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
java, javascript
Ambito
frontend, testing-qa

Direzione di ricerca

Start with test/flows/crud.js in @aerokit/[email protected] and inspect the handleField(entity) registration check. Trace how the flow creates a row, reads the save response, locates it for editing and deletion, and uses freshUniqueKeys for relation picks. Done when relation keyed entities receive UI CRUD coverage via their label or record key, and entities with no editable field are reported as skipped with a reason.

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

Descrizione

@aerokit/[email protected] test/flows/crud.js: if (!handleField(entity)) return;. The generic UI create/edit/delete flow is registered only when the entity has an editable text field that the flow can type a unique marker into and then find the row by. An entity whose user-entered data is ALL relations, dates and numbers therefore gets no UI crud coverage at all. The run reports nothing: the flow is simply absent from the list, neither skipped nor failed.

Case: BusinessIntents/base-timesheets.

  • EmployeeTimesheet has ProjectTimesheet + Employee (relations, the business key), number (system), employeeName (readOnly snapshot) and totals (aggregates).
  • ProjectTimesheet has Project, period (month), and totals.

Both carry a stored, read-only label Name (label: "{period|yyyy MMMM} - {Project.name}", "{ProjectTimesheet.Name} - {Employee.name}") that is unique per row and shown in the list. On 14.88.0 both entities' REST, list, multilingual and My flows run and pass, but neither gets the UI crud flow. That has been the open row of base-timesheets#28 since 2026-10-02.

Ask: when no editable text handle exists, fall back to the entity's generated label Name, or to the row's key in the record route.

  1. Create through the form, filling the required relations with fresh picks (freshUniqueKeys already does this for the business key).
  2. Read back the created row's Name (or id) from the REST response of the save.
  3. Locate, edit (any editable non-key field, or a relation re-pick) and delete by it.

If an entity truly has nothing editable after create, say so in the run as a skipped flow with the reason, rather than leaving it out silently.

Lingua principale
Java
Stelle
278
Fork
97
Merge medio
17h 19m
PR unite (30g)
261

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 eclipse-dirigible/dirigible

Tutte le issue di eclipse-dirigible/dirigible

Issue simili

Altre issue su Java

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.