-
Notifications
You must be signed in to change notification settings - Fork 10.3k
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
[gatsby-link] Export NavLink explicitly from the package #2008
Comments
kripod
changed the title
[gatsby-link] Export NavLink
[gatsby-link] Export NavLink explicitly from the package
Sep 3, 2017
Let's consider this for v2 |
Not really sure if it's better or worse for gatsby to have them split out, but FWIW you can set const CustomLink = glamorous(Link)({
// CSS
'.active': {
// Active styles
}
})
CustomLink.defaultProps = {
exact: true
} |
Not relevant now that we've moved to @reach/router. |
@KyleAMathews There's a lack of support for Reach Router's |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Instead of automatically choosing an appropriate React Router link component based on the given props, I think that letting developers explicitly choose
NavLink
overLink
should be a possibility.That approach would make styling Glamorous components much easier compared to the current approach:
The text was updated successfully, but these errors were encountered: