dcramer / dcramer/peated

Barcode Registry

Open
#3 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
103
Forks
18
Avg merge
1h 19m
Merged PRs (30d)
555

Description

Barcodes are basically SKUs, so once we have them captured we could easily enable faster lookup. This will be useful for the most common bottles.

In an ideal world the UX flow to check-in would be:

  • Capture barcode
  • If no entity, create it
  • Store barcode w/ created entity reference

The barcode flow would be optional, but maybe we could make it mandatory for adding new bottles?

Some relevant resources:

Contributor guide

No contributing guide indexed for this repository

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.

Research direction

No project files, tests, or entry points are named. Start by reviewing the proposed flow and the Barcode Lookup API resource, then clarify whether barcode capture is optional or required and define the expected behavior for lookup, entity creation, and storing the reference.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
backend-api-design, full-stack
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.