Skip to content

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

Merged
merged 8 commits into from
Mar 5, 2024

Conversation

kristenyee
Copy link
Contributor

@kristenyee kristenyee commented Feb 29, 2024

buttons are not functional
closes #42

@kristenyee kristenyee changed the base branch from main to dev February 29, 2024 19:31
Copy link
Member

@michellelin1 michellelin1 left a 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
Copy link
Member

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
Copy link
Member

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

Copy link
Collaborator

@ThatMegamind ThatMegamind left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

@ThatMegamind ThatMegamind merged commit b26ce4d into dev Mar 5, 2024
@ThatMegamind ThatMegamind deleted the 42-published-schedule-match-high-fidelity branch March 5, 2024 04:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Published Schedule Match High Fidelity
4 participants