Skip to content

Task: AddProfile Has Been Voted Off the Island #93

@sgilfeather

Description

@sgilfeather

🎯 due Monday, April 8th

My generically-typed modular AddProfile component is too complex and over-engineered than what we need for the Legacy Project's webpage (it was fun while it lasted, y'all). That being said, I'm nuking the old AddProfile component and transitioning to a much simpler AddSenior page that's less parameterized. This ticket is for me! (Skylar)

  • Kill your baby AddProfile and transition to using just the singular add-senior.tsx page for your profile. When mapping over the input boxes, create a separate component for the dropdown s

Right now, setProfileData only sets the value of the selectName field (event.target.name) to the new value provided (event.target.value). We want to accumulate values chosen in the dropdown, so that setProfileData adds a new value to the input box, and doesn't replace it.

  • Modify components/addProfile/form.tsx at line 31 so that it accumulates a list of values, rather than replacing them on every call of handleSelected.

Furthermore, there's a bug in the profile form where clicking on any input box causes the dropdown to pop up.

  • Fix this bug, so that the dropdown only pops up on selection of its input box. This requires refactoring the component such that this specific input box accumulates a list of Student models: displaying their names, while keeping track of their IDs so that these can be compiled into a list on submission to create the Senior model.

Screenshot 2023-04-24 at 11 18 57

Metadata

Metadata

Assignees

Labels

help wantedExtra help would be great!

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions