-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add Navbar and skeleton pages #41
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.
The styling looks good Joel.
Just a couple of suggestions according to me:
- Currently, when I hover the
Notifications
tab or if I clicked theProfile
avatar there ispadding-right
coming up to the header of navbar. Unfortunately, this is currently bug in material-ui. I believe this can solved usingPopper
instead ofPopover
. useStyles
hook should be in separate file to make it consistent with rest of the project structure.Notifications
tab shouldn't be wrapped inside Link tag as user is not going to send over to different page.- The navbar isn't responsive. I recommend to check out this article. But, instead of using custom useState for mobile screen detection you can use useMediaquery provided by material-ui out of the box.
Let me know if you need any help :)
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.
nice clean code!
@g4rry420 Thanks for the thorough review, Gurkiran. |
As I was refactoring anyway, I updated the profile menu to work as a toggle. @bonnieli, does the approval still stand? It's a small change, but I just want to be sure :) |
yep approval still stands! |
Thank you!
… On Jun 5, 2021, at 5:57 PM, Bonnie Li ***@***.***> wrote:
As I was refactoring anyway, I updated the profile menu to work as a toggle. @bonnieli, does the approval still stand? It's a small change, but I just want to be sure :)
yep approval still stands!
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
This reverts commit 4f161ce. Accidentally pushed wrong branch
What this PR does (required):
Screenshots / Videos (required):
Any information needed to test this feature (required):
Any issues with the current functionality (optional):
-I provided a null key to all items being mapped on line 131 of Navbar.tsx. I tried to make the key equal the name of the mapped item ("alert", in this case), but this causes TypeScript to throw "No overload matches this call." I'm not sure how to give the items unique keys in this circumstance.