Northeastern-Electric-Racing / Northeastern-Electric-Racing/FinishLine
Components - Create Multiple Autocomplete component
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 36
- Forks
- 9
- Avg merge
- 4d 21h
- Merged PRs (30d)
- 11
Description
Description
We use multiple autocompletes in lots of situations but we currenlty use the default google mui autocomplete, which is fine, but it would be nice if we ever decided we wanted to change how they all looked wed only have to change one file instead of 10.
Acceptance Criteria
component for autocomplete and works with all current use cases of a mutiple autocomplete in the code base
Proposed Solution
copy and paste one of the autocompletes to another file, add all the props necessary to make the file compile and then try to abstract it so that it works for all of them in the codebase
Mocks
epic #1255
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the existing multiple-autocomplete usages across the codebase and compare the props each one requires to compile. Create a shared component that supports all current use cases, then verify each existing usage works with it and that the acceptance criterion is met.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- frontend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100