Hacktoberfest 2026：メンテナが10月に向けて印を付けた、オープンで初心者向けの issue。 Hacktoberfest の issue を見る

intent: sourceStatusOnRetire is refused for a cross-model target - a milestone/timesheet billed into another module's invoice can never be re-billed after a void

オープン
  • 何か問題がありますか？
#7,954 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
48/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
java, yaml
領域
api, backend

調査の方向性

Start with IntentParser.validateGeneratesReopen, which the issue names as refusing cross-model targets, and inspect how published .model data exposes owner status nomenclature and how CrossModelSupport reads it. Trace the generated reopen listener for local targets and its subscription to the target's -transitioned topic. Done means the example parses and voiding its generated invoice returns the milestone to REACHED, allowing a second Generate.

索引モデルが issue の本文から書いたものです。

説明

Problem

sourceStatusOnRetire (#6868, extended to button create-froms by #7647) is refused for a cross-model target at 14.93.0 (IntentParser.validateGeneratesReopen):

generates [invoice-from-milestone] cannot reopen for a cross-model target (uses [sales-invoices]) - what RETIRES a [SalesInvoice] is the stage: classification of its status nomenclature, seeded in the owner model and not resolvable here

The commonest create-from in an ERP is exactly this shape: a document of one module is billed into another module's invoice. In BusinessIntents:

  • base-projects invoice-from-milestone (Milestone -> SalesInvoice, sourceStatus: 3 INVOICED, fromStatus: [2]): when the invoice is voided, the milestone stays INVOICED, the from-status guard 409s the next Generate, and immutableWhen locks it. The milestone's amount can never be billed again (BusinessIntents/base-projects#30).
  • base-timesheets invoice-from-timesheet (ProjectTimesheet -> SalesInvoice, sourceStatus INVOICED): same dead end for a voided month invoice.

The target module cannot author the reopen instead (it would need uses: back to the source module - the cycle).

Ask

Let sourceStatusOnRetire resolve the retiring statuses of a cross-model target from the owner's published .model: the owner already knows which seed rows of its EntityStatus nomenclature are stage: cancelled / stage: void. Emitting those ids into the owner .model (like the widget types CrossModelSupport already reads) would let the reopen listener be generated in the SOURCE module, subscribed to the target's -transitioned topic, exactly as for a local target.

Expected

generates:
  - name: invoice-from-milestone
    from: Milestone
    to: SalesInvoice
    uses: sales-invoices
    fromStatus: [2]
    sourceStatus: 3
    sourceStatusOnRetire: 2   # voiding/cancelling the invoice returns the milestone to REACHED

generates without a parser issue; voiding the generated invoice returns the milestone to REACHED and a second Generate succeeds.

主要言語
Java
スター
278
フォーク
97
平均マージ
16時間 46分
マージ済み PR（30日）
265

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

eclipse-dirigible/dirigible のほかの issue

eclipse-dirigible/dirigible の issue をすべて見る

似ている issue

Java の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。