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

reports: a report parameter bound to an entity key renders a picker, not a number input (kind: ledger account)

Open
#7,897 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
Mostly clear
Activity status
Active
Tech stack
java
Domain
full-stack

Research direction

Start by tracing how generated .report parameters are created for kind: ledger and how the Harmonia report page renders parameters, then compare that with the form handling for to-one relations and hierarchy-aware pickers. Keep the generated controller’s key binding and authored parameters: inputs compatible. Done means a ledger report offers a selectable account picker, supports selecting group accounts for tree entities, and reloads the card with the chosen key.

Written by the indexing model from the issue text.

Description

What is missing

kind: ledger (#7887) declares an account report parameter on its own behalf - the key of the account whose lines it lists. The generated .report parameter carries only {name, type, initial}, so the Harmonia report page renders it as a plain number input: the user has to know the account's id. Every other place the platform asks for a row of a nomenclature offers a picker (with the hierarchy-aware tree picker for an entity declaring hierarchy:).

Proposed shape
  • the generator marks such a parameter with the entity it selects (e.g. lookup: { entity, controller, label, hierarchyProperty } on the .report parameter), for kind: ledger's account first;
  • the report page renders that parameter with the same dropdown / tree picker a form uses for a to-one relation, label shown, key bound;
  • the generated controller keeps binding the key unchanged, so links and mailed reports (attach: bind) keep working.
Acceptance

Opening a generated ledger report offers the chart of accounts as a picker (group accounts selectable when the account entity is a tree); choosing one reloads the card. Authored parameters: keep their current inputs.

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.