-
Notifications
You must be signed in to change notification settings - Fork 0
42 published schedule match high fidelity #52
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Overall, looks really good, so good work! After discussing with design, we agreed having a "current season" option as well as the actual season (winter 2024) was redundant. So could you change it so the default is the actual season name (ie [season] [year])?
if (a.split(' ')[1] !== b.split(' ')[1]) { | ||
return b.split(' ')[1] - a.split(' ')[1]; | ||
} else { | ||
// If years are equal, compare alphabetically |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the drop down should be sorted in reverse chronological order but sorting it alphabetically results in fall coming before summer.
))) | ||
} | ||
{/* season dropdown menu */} | ||
<Select |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The text of the dropdown is a bit large. Michael and I think that you can create 2 separate elements: 1 large text to hold the season name and 1 "hidden" select where the options would display but the selected option would not. Let us know your thoughts on this workaround
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good!
buttons are not functional
closes #42