This repository has been archived by the owner on Sep 29, 2024. It is now read-only.
feat: Responsive Navbar Layout #257
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
Signed-off-by: Jy <[email protected]>
Signed-off-by: AlexNg <[email protected]>
Signed-off-by: AlexNg <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
caffeine-addictt
suggested changes
Aug 8, 2024
caffeine-addictt
suggested changes
Aug 8, 2024
caffeine-addictt
suggested changes
Aug 8, 2024
caffeine-addictt
approved these changes
Aug 8, 2024
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What type of PR is this? (check all applicable)
Description
Responsive Navbar layout, it contains CTA button, and dropdown menu for the notification bell and links to different pages, notification does not work yet.
Related Tickets & Documents
QA Instructions, Screenshots, Recordings
Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.
Added/updated tests?
We encourage you to keep the code coverage percentage at 80% and above.
have not been included
[optional] Are there any post deployment tasks we need to perform?
Checklist