support `Link` from react-router-dom (button-close not rendered anymore when using custom children)
See original GitHub issuecurrently using custom children so that I can bind Link
from react-router-dom
to the links, would there be a better way to make it work?
Issue Analytics
- State:
- Created 6 years ago
- Comments:7 (3 by maintainers)
Top Results From Across the Web
Forcing a React-Router <Link> to load a page, even if we're ...
I solved this by pushing a new route into history, then replacing that route with the current route (or the ...
Read more >Migrating to React Router v6: A complete guide
Migrate your React Router applications from v5 to v6 with this in-depth guide, including a review of additions and improvements from v5.
Read more >Upgrading from v5 v6.6.1 - React Router
For example, a <Link to="me"> that is rendered inside a <Route path="users"> will always render a link to /users/me , regardless of whether...
Read more >Suspense for Data Fetching (Experimental) - React
Approach 1: Fetch-on-Render (not using Suspense). A common way to fetch data in React apps today is to use an effect: // In...
Read more >How to handle navigation in your app with React Router Link
In this article, we'll explore the navigation possibilities in a React app and we'll take a look at the React Router Link component....
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
In my case i want to have a custom link to /privacy page in the banner and a separate close button
The issue is that close button
<div className="button-close">Got it</div>
is not working anymore if using custom html.I opened a PR to fix this issue: #52