semmelei: Procurement shows the Bakery Article Numbers
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 56/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- typescript
- Domain
- full-stack
Research direction
Start from the Procurement API and page, then trace how positions link to live Items and how lines are grouped and sorted. Add the distinct current article numbers to each line while preserving the existing grouping and order; show them in a new column, with comma separation or "–" when empty. Add the specified HTTP tests, update translations, regenerate the API client, and run just ci and the frontend checks.
Written by the indexing model from the issue text.
Description
Parent
#84
What to build
Every line of the Procurement ("Beschaffung") shows the Bakery Article Numbers of its Items, so Verkauf can place the order at the Bakery straight from the list.
The numbers are read live from the Items through each position's Item link, never snapshotted: a number changed after the order was placed shows the current one. Each Procurement line gets the distinct numbers of its linked live Items, sorted; positions of deleted Items or Items without a number contribute nothing. Several numbers render comma separated, none renders as "–". Grouping by the name snapshot and the sort order (most units first, ties by name) stay as they are; the list is also the packing list.
Frontend: a number column on the Procurement page, i18n per the conventions, API client regenerated.
Acceptance criteria
- HTTP test: the Procurement shows the Item's current number after it was changed after the order
- HTTP test: a line whose Item has no number has an empty list
- HTTP test: a line whose Item was deleted has an empty list
- HTTP test: two Items with the same name and different numbers give one line listing both numbers
- HTTP test: grouping and sort order unchanged
- The Procurement page shows the column, "–" for empty
-
just ciand the frontend checks are green
- Dominant language
- TypeScript
- Stars
- 0
- Forks
- 1
- Avg merge
- 10h 56m
- Merged PRs (30d)
- 34
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
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from myOmikron/code
-
wayfinder:task
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
wayfinder:task
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
myOmikron/code#102 · 2 comments ·
Maintainers usually reply within 1 day
-
ready-for-agent
Difficulty 5/5 Over a week Newbie friendliness 18/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
needs-triage
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
cursor/community-plugins#465 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
vetro-protocol/vetro-monorepo#978 ·
Maintainers usually reply within 1 day
-
ai-generated bug category:security effort:s priority:p3
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
LanternOps/breeze#9697 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
maniator/verticopolis#1303 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 73/100
components-web-app/docs#297 ·