-
Notifications
You must be signed in to change notification settings - Fork 93
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
UI: Created Navbar Component #230
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.
@stableapple According to the mocks there should be Blogs after FAQs, also Contact should be Contact Us.
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.
It will be better if you will add a new gif in your PR with all the changes you have made.
src/Navigation.js
Outdated
<li className="li_signIn">Sign In</li> | ||
</Link> | ||
<Link to="/" className="li"> | ||
<li className="active" >Sign Up</li> |
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.
hello, I guess you have applied to the Active class only to Sign UP. I believe all the list elements in nav will have that active class on hover.
Apart from that things look good to me.
Am I right @Rahulm2310 @mtreacy002 ?
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.
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.
@shades-7 According to the Figma file, a blue line appears upon hover. Active class is for the blue background of the signup button.
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.
Here you can link to the existing Register
page until we have the new Sign Up
page created so not to block the contributor to access the Register
feature.
@stableapple your design has a light blue bar on the top of navbar. |
As we don't have the designs for smaller screens, can't say about the hamburger button and the nav. @stableapple Can you please show the behaviour(toggling) of nav on smaller screens(mobile) in a GIF. |
@mtreacy002 which section should I review exactly? |
1 similar comment
@mtreacy002 which section should I review exactly? |
@Vuyanzi, just want to confirm the design done here is as expected. The Figma did show the different colour styles. But I'm curious to few things:
|
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.
@stableapple , sorry for taking a while to give my feedback. This is because I'm waiting for the sidebar to be created first or at least in progress, since otherwise contributors access to the existing features (upon login) will be blocked. Now that we have #254 in progress, hopefully we can avoid the blockage if we can finish this pr and #254 around the same time. Hope this make sense. I really appreciate your patience ❤️ .
On this point, please check my comments below 😉.
<Nav className="ml-auto"> | ||
|
||
<Link to="/" className="li"> | ||
<li >About Us</li> |
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.
This later can be linked to the video section (UI not completed yet, so no changes needed here 😉)
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.
<Link to="/" className="li"> | ||
<li >About Us</li> | ||
</Link> | ||
<Link to="/" className="li"> |
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.
Based on Figma, this later can be linked to the Why BridgeInTech section (pr #247 is still in progress). No changes needed atm.
src/Navigation.js
Outdated
<li className="li_signIn">Sign In</li> | ||
</Link> | ||
<Link to="/" className="li"> | ||
<li className="active" >Sign Up</li> |
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.
Here you can link to the existing Register
page until we have the new Sign Up
page created so not to block the contributor to access the Register
feature.
<Nav.Item> | ||
<Card> | ||
<Card.Header> | ||
<Accordion.Toggle as={Link} to="/" eventKey="0" onClick={logout}>Logout</Accordion.Toggle> |
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.
Make sure this Logout
option is shown for users who have successfully logged-in (instead of Sign In and Sign Up buttons).
Also, @stableapple . I've just asked @Vuyanzi on Zulip about the sequence of the main nav menus. Please don't hesitate to share with us your thoughts by replying to that post on the zulip channel 😉 |
Should I implement the functionality around login and register in the current design or is there a separate design for it? |
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.
@stableapple , thank you for adding the routes to the sections that have already completed. About the Sign In and Sign Up designs, for now you can just link these menu items to the existing login and register pages. This is so at least the contributors can access the existing features of Login/Register and continue with the development. Later when the Sign In and Sign Up prs #248 #249 are completed, we can refactor the pages to the new designs.
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.
Thank you for accommodating to the changes requested, @stableapple. This looks good to me. The Login/Register and Logout features are now functioning as normal. I've also tested this on my local device and here's the outcome:
- Code review: done
- Tested on all possible behaviours
Expected behaviours:
- Most of the menu items (not including Sign In/Sign Up) are linked to the relevant sections of the homepage (these menus are: FAQs, Blogs, Contact Us).
Sign In
tab is linked to the Login pageSign Up
tab is linked to the Register page- user can sign in to existing account/register a new account
- when user sign in the
Sign In/Sign Up
tabs are replaced byLogout
tab
Actual behaviours: as expected (see gif below)
- Environment:
OS: MacOS BigSur
Browser: Microsoft Edge
Thank you again for your patience and contribution 🎉🎉🎉. Now we just need one more reviewer to approve this then we'll merge it 😉. Perhaps @Rahulm2310 or @vj-codes can help?
test failing with unused var as the cause
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.
Sorry, I overlooked the testing that failed. Please remove user
from the AuthContext call then it should fix the test. Thanks
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.
LGTM @stableapple 🎉🎉🎉.
Sorry, I was unable to review it. Anyway, great work @stableapple @mtreacy002 🎉 🎉 |
Description
Added Navbar Component
Fixes #208
Type of Change:
Code/Quality Assurance Only
How Has This Been Tested?
Checklist:
Code/Quality Assurance Only