Implement hearting, queueing and Play Now for levels #146
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…2 buttons max, ability to add username query parameter to level categories
…or level button area
…ents, titleSubtext is next to title again
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request implements hearting, queueing and Play Now for levels on the rewrite website. The buttons to do so appear under certain conditions on the FancyHeaderComponent, to the right of the title on desktop layout and a little below on mobile layout. If there are more than two buttons to appear on the level page's FancyHeaderComponent, all buttons starting from the second one will be put as navitems into a dropdown menu, which you can open and close with a dedicated button. This pr was mostly about hearting and queueing levels, I have decided to do Play Now too to show off the dropdown menu functionality. There are also some other minor changes, like the description of a FancyHeaderComponent always being below the rest and having the title wrap. Imagine the level description in the example screenshots was long.