You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of searching through options to find the corresponding label, we should consider
typing value as DropdownOption<T> so we automatically have access to the label/value pair
making value optional, i.e. value: DropdownOption<T> | undefined so that we can have different styling for the Placeholder vs. the Selected Value (i.e. placeholder should be grey while value should be black).
Alternatively, we can just directly use/style Select from React-Select
This change would affect (i.e. CustomSelect is used in):
Onboarding (for the Review and Submit Screen)
no issues arise here b/c the value will always be non-null when a user reaches the review screen
PlantDetails, for the PlantingType input in Add Details Page
we're currently handling this by just passing in '' if there's no selected value yet
Currently, CustomSelect expects
value: T
as a prop, and styles the placeholder/value like so:Instead of searching through options to find the corresponding label, we should consider
value
asDropdownOption<T>
so we automatically have access to the label/value pairvalue
optional, i.e.value: DropdownOption<T> | undefined
so that we can have different styling for the Placeholder vs. the Selected Value (i.e. placeholder should be grey while value should be black).Alternatively, we can just directly use/style
Select
from React-SelectThis change would affect (i.e. CustomSelect is used in):
The text was updated successfully, but these errors were encountered: