-
-
Notifications
You must be signed in to change notification settings - Fork 1.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
@Reach/Router support for NavLink #1308
Comments
What is |
Hey @TheSharpieOne thanks for the quick response! My loose understanding is that Link would be a function, but perhaps that's wrong? It's rendering properly, so that's where I'm getting weirded out. :) |
Seems like it returns an object, we may need to also allow objects which a certain shape (has |
Understood, so right now you're doing a Thanks for the heads up. I'd do a PR for this, but I think it may be a tad out of my league in terms of understanding the src structure! :( |
It's the prop-types lib which is doing the work, reactstrap just defines what is allowed and right now for that prop it's only allowed to be a function or a string. |
Understood, so it's just allowing additional types. Cool! Maybe I'll take a crack at understanding it - happy to contribute back if I can muster it! |
I'm also getting the same issue, looking for patch release :-) |
so am i, please help |
+1 |
I have updated the dependencies as per the change log - https://github.com/coreui/coreui-free-react-admin-template/blob/master/CHANGELOG.md. But still I am facing some issues with AppSidebarNav. Is this because I have created a Protected route ?
|
NavLink
6.5.0
npm/es
16.5.0
4.1.3
What is happening?
Trying to implement Reach-Router
Link
component within the NavLinktag
attribute.What should be happening?
It appears to work, but there is a Console Error.
Steps to reproduce issue
Error message in console
Code
The text was updated successfully, but these errors were encountered: