Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine

BOM - Unit Should be More Dynamic

Open
#2,120 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

difficult front-end
Dominant language
TypeScript
Stars
36
Forks
9
Avg merge
4d 21h
Merged PRs (30d)
11

Description

Description

Right now units are just an optional field next to quantity in the material form. Ideally this field would be more dynamic/ intuitive for users to use. My main idea for this is for a user to select a unit and then they would get another input pop up based on that unit. For example, a user should be able to select a pack and then another input should pop up allowing them to specify how many items are in that pack. This will be a bit tricky since this is a model in our database, so I'm marking this ticket as difficult, since it'll take some thinking to figure out a clean way to do this.

Acceptance Criteria
  • Unit select looks better and is more intuitive to use
  • More specifically, you can specify how many items to go in a pack, if you select pack from the list of items (doing this in a clean way will take some thinking)
Proposed Solution

You could try adding a custom 'Pack' option to the list of options in the unit dropdown then have it create a new unit whenever someone enters a new pack size. You could hide all these extra pack sizes from the list displayed in the units options as well. That's just me spitballing, so if it doesn't make sense shoot me a message in slack

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

Start by locating the material form and the unit model referenced in the issue, then trace how units are selected and stored. Define the interaction for selecting Pack and entering its item count, including how generated pack sizes are represented and omitted from the regular unit list; done means both acceptance criteria work cleanly.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.