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

semmelei: Dispatch the Procurement to the Bakery as CSV

Open
  • Is something wrong?
#91 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
typescript
Domain
api, backend, databases

Research direction

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.

Written by the indexing model from the issue text.

Description

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
Dominant language
TypeScript
Stars
0
Forks
1
Avg merge
10h 20m
Merged PRs (30d)
36

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

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 myOmikron/code

All issues in myOmikron/code

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.