Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

postings: one item per source LINE (forEach over the source's composition child), carrying the line's own dimensions

Abierto
  • ¿Algo no está bien?
#7,915 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java, yaml
Área
backend, databases

Línea de trabajo

Start by locating the postings: configuration parser and the code that builds PostingIntent items, then trace how source composition children are read and how itemsSumEqual and reverses: are handled. The issue gives an ExpenseClaimItem example; use it to map the expected repeated lines, line fields, and per-row when: behavior. Done means the example supports per-line dimensions and accounts while preserving balance checks and reversal behavior.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

A postings: block builds the target document's items from a fixed list over the SOURCE HEADER: items: [{ Account: rule(X), debit: "Net" }, ...]. That is enough for a document whose ledger impact is header totals (an invoice's receivable / revenue / VAT). It is not enough when the line carries something the ledger must keep per line. On 14.88.0 and 14.90.0 (PostingIntent has no per-line key) there is no way to:

  • Book an analytic dimension. An expense claim's lines each name a Project (one trip mixes the client's hotel with an office supply). The posting can only book the claim's total expense, so the project is lost at the ledger and a "by project" balance report has nothing to read.
  • Book per-line accounts. A cash payment order paying three different things, a purchase invoice whose lines go to different expense accounts (602 services and 601 materials), or a depreciation run that books one line per asset at the asset's own category account.
Ask

An item template that is repeated per row of a source composition child, with the line's own fields available to the cells:

postings:
  - name: expensePosting
    event: { onTransition: ExpenseClaim, model: expenses, when: "Status == 3" }
    creates: JournalEntry
    backReference: Expense
    rule: { entity: PostingRule, match: { documentType: "Expense" } }
    items:
      - forEach: ExpenseClaimItem                   # the source's composition child
        lines:
          - { Account: rule(ExpenseAccount), debit: "line.Amount", Project: "line.Project" }
      - { Account: rule(VatPurchasesAccount), debit: "Vat", when: "Vat != 0" }
      - { Account: rule(PayableAccount),      credit: "Total" }

line.<field> reads the child row. A to-one FK copies like any other cell (#6533). A per-line when: guards each row. The balance check stays the document's itemsSumEqual. A reversal (reverses:) mirrors the repeated rows negated, the same as the fixed ones.

Where it is needed
  • BusinessIntents/base-journal#83 (analytic dimension: project / cost centre propagated from source documents).
  • The per-account depreciation run of BusinessIntents/base-fixed-assets.
  • Purchase invoices with per-line expense accounts.
Lenguaje dominante
Java
Estrellas
278
Forks
97
Merge medio
18 h 53 min
PR fusionados (30 d)
228

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eclipse-dirigible/dirigible

Todos los issues de eclipse-dirigible/dirigible

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.