You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the new or updated feature that you are suggesting?
Hi!
I am using react-router-dom in v6. I need to navigate somewhere without having to use useNavigate.
Why should this feature be included?
As far as I understand, if I want to programatically change a route, I should use the useNavigate hook inside my component to get access to the navigate method. does not work in my use case.
I do render hundreds of components into my App and each of these components might trigger a route change and therefore all of them need to call useNavigate to get access to the navigate function. Now this is of course problematic as each route change triggers a rerender of those many components that use useNavigate.
Is there any way to work around the use of useNavigate but still trigger route changes?
Thanks a lot!
The text was updated successfully, but these errors were encountered:
What is the new or updated feature that you are suggesting?
Hi!
I am using react-router-dom in v6. I need to navigate somewhere without having to use useNavigate.
Why should this feature be included?
As far as I understand, if I want to programatically change a route, I should use the useNavigate hook inside my component to get access to the navigate method. does not work in my use case.
I do render hundreds of components into my App and each of these components might trigger a route change and therefore all of them need to call useNavigate to get access to the navigate function. Now this is of course problematic as each route change triggers a rerender of those many components that use useNavigate.
Is there any way to work around the use of useNavigate but still trigger route changes?
Thanks a lot!
The text was updated successfully, but these errors were encountered: