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

semmelei: Dispatch the Procurement to the Bakery as CSV

クローズ
#91 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

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

関連するプルリクエストがすでにマージされています。

  • #297 @omikron-agent による — マージ済み

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
35/100
issue の種類
機能追加
明瞭さ
明確に書かれている
活発さ
活発
技術スタック
typescript
領域
api, backend, databases

調査の方向性

Start with parent issue #87 and the decision in #84, then trace the Dispatch and Review Window flow, admin settings API and form, Procurement response, and existing mail and recording sink tests. Check how Item links and position snapshots are represented before planning the grouped CSV and acknowledged delivery. Done means meeting the listed acceptance criteria, including retry behavior and exact attachment bytes.

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

説明

ready-for-agent

Parent

#87

What to build

At the Dispatch, semmelei sends the Procurement as a CSV to the Bakery, with a copy to the Nachbarschaftshilfe.

  • Settings: Admins enter the Bakery mail address and the copy address (both optional, validated as mail addresses) in the admin settings API and form.
  • No Bakery address: the day is skipped and not marked, so it dispatches on the first tick after an address is set. The Procurement response carries a not-dispatched reason (none / no Bakery address) and the page shows "Nicht versendet: keine Bäckerei-Adresse". Note: while no address is set, that day's customers get no confirmations either.
  • Bakery order: built from all non-cancelled orders' positions, grouped by the Item's live Bakery Article Number (read through the position's Item link, as decided in #84). Positions of deleted Items or Items without a number are left out entirely. Quantity summed; "Artikel" = distinct name snapshots joined with " / "; "Einzelpreis" = customer price snapshot of the first position; differing prices under one number log a warning.
  • CSV: header Artikel;Artikelnummer;Menge;Einzelpreis, ; separator, RFC 4180 quoting where needed, German decimal comma without currency sign (2,50), UTF-8 with BOM, CRLF, sorted by article number, filename bestellung-<YYYY-MM-DD>.csv, content type text/csv; charset=utf-8.
  • Mail: German regardless of order languages, subject Bestellung Nachbarschaftshilfe für <Wochentag, Datum>, a one-sentence body with the pickup date, the copy address as CC, the CSV attached.
  • Delivery: with lines, publish and wait for the ack; only then mark the day dispatched. A failed publish leaves it unmarked and the next tick retries (a duplicate order is the lesser failure than a lost one; this is the opposite of the customer mails, which mark before sending, and the reason belongs in a code comment). Without lines, mark dispatched and send no Bakery mail. Confirmations follow as in the Review Window ticket.
  • New i18n keys, API client regenerated, rorm migration committed.

Acceptance criteria

  • Bakery and copy address settable via API and form; invalid addresses rejected
  • No Bakery address: nothing sent, day not marked, Procurement reports the reason and the page shows it; setting the address dispatches on the next tick
  • At the Dispatch one mail goes to the Bakery address with the copy address in CC, the German subject and the CSV attached
  • CSV: header, one line per article number, joined names, summed quantity, 2,50, BOM, CRLF, sort order; Items without number and deleted Items left out; cancelled orders left out
  • No Bakery positions: no Bakery mail, day dispatched, confirmations sent
  • Failed ack: day not marked, retried next tick; after success no second Bakery mail
  • Differing prices under one article number log a warning
  • Tests assert the mails leaving the service (recipients, CC, subject, attachment bytes) through the HTTP harness with the recording sink
主要言語
TypeScript
スター
0
フォーク
1
平均マージ
9時間 39分
マージ済み PR(30日)
144

環境構築

このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。

はじめの一歩

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

myOmikron/code のほかの issue

myOmikron/code の issue をすべて見る

似ている issue

TypeScript の issue をもっと見る

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

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