Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

semmelei: Dispatch the Procurement to the Bakery as CSV

Aperta
  • Qualcosa non va?
#91 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
5/5
Tempo stimato
Più di una settimana
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Specificata chiaramente
Stato di attività
Attiva
Stack tecnologico
typescript
Ambito
api, backend, databases

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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
Lingua principale
TypeScript
Stelle
0
Fork
1
Merge medio
10h 20m
PR unite (30g)
36

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di myOmikron/code

Tutte le issue di myOmikron/code

Issue simili

Altre issue su TypeScript

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.