openboxes / openboxes/openboxes-mobile

Create component that accepts barcode scan

Open
#9 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
10
Forks
13
Avg merge
5d 22h
Merged PRs (30d)
7

Description

After scanning data into the field the field

  • should either store data in field as-is or should pull extra data using API.
  • should be read only
  • should transition focus to the next input field when available.
  • should display an error if API request does not return data

For example a SKU field should attempt to lookup the product associated with the SKU. The SKU and product name should be visible / read only. Clicking on the field should make it editable / scannable again.

In the case that the field is the only field on the page then subsequent scans could potentially update the field value even when the field is read only but we'd need to check if usability is ok there. I think a better approach for single field pages would be to move to the next page (in case of a wizard).

Note: We'll need a separate component for searching by SKU and bin location. This component should not exhibit behavior above.

Contributor guide

Open the contributing guide

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 files, tests, or entry points are identified in the issue, so first locate the existing field and API components in the mobile application. Clarify the component boundary and single-field behavior before implementation. Done means scanned values follow the specified read-only, lookup, error, editability, and focus-transition behavior, while SKU/bin-location search remains separate.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
mobile
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.