-
Notifications
You must be signed in to change notification settings - Fork 9
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
feat: Direct About Skate
clicks to the /user-guide endpoint
#2593
Conversation
Coverage of commit
|
ae2c5dd
to
cd30730
Compare
Coverage of commit
|
<NavLink | ||
className={({ isActive }) => | ||
"c-left-nav__link" + | ||
(isActive ? " c-left-nav__link--active" : "") | ||
} |
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.
question: This doesn't go anywhere within the app, so I'm wondering, what benefits do we get from using <NavLink>
here over an <a>
?
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.
Hmmm - probably not much benefit, huh.
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.
Sooo I think we gain some benefit in consistency. Even if we don't need all of the features of NavLink
, we still get the benefit of it effortlessly looking like the other links in this section!
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.
Coverage of commit
|
Asana Ticket: https://app.asana.com/0/1148853526253420/1206673444071869/f