Implement navigation rail 🚃 ❄️ #18
Merged
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
|
They seem cool! Nice work 👏 |
fgiris
approved these changes
Feb 20, 2023
haitech
reviewed
Feb 21, 2023
Implement navigation rail and seperate the components into its own sections
oas004
force-pushed
the
feature/navigation-rail
branch
from
eb68749 to
536cfe7
Compare
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.
Implement navigation rail and seperate the components into its own sections with the nav rail. Thinking we could expose more components like this and their separate state in the end. Now the designers can at least see how the nav rail is looking.
Was a bit unsure about the icons. Wdyt? 😅
resolves #7