Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

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)

Open
  • Is something wrong?
#7,910 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
java, javascript
Domain
frontend, testing-qa

Research direction

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.

Written by the indexing model from the issue text.

Description

@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.

Dominant language
Java
Stars
278
Forks
97
Avg merge
18h 53m
Merged PRs (30d)
228

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-dirigible/dirigible

All issues in eclipse-dirigible/dirigible

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.