-
Notifications
You must be signed in to change notification settings - Fork 7
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
Active Navbar Link should be visible #4
Comments
@aryad14 Can you please assign it to me? It's pretty straight forward. I can easily knock this out. |
Hey can you assign this issue to me ? |
@aryad14 Can you please assign it to me ? I'd like to work on it. |
It's not working. Do you guys use a clerk publishable key or any specific node version? Looks like .env.local in git ignore |
@aryad14 any update? |
@PALLAVIKHEDLE I have added .env.sample file to the repo, make sure to check it and setup clerk authentication on your side |
Yes, I set up the Clerk authentication. But what about stripe and MongoDB URI? |
For setting up the project you have to add the mongodb url and stripe API keys. Otherwise it won't work |
Can you provide me those, or do you want me to add those from my end? |
You can add them on your side. |
Issue
The links do not have a active state, hence it is difficult to know on which route a user is.
Expected Solution
Add some styling to the navigation link which states on which route the user is. For example, if the user is on About page, the About link on the navbar should have some styling denoting that the user is currently on the About Page.
Thank you!
The text was updated successfully, but these errors were encountered: