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
{{ message }}
This repository has been archived by the owner on Aug 1, 2024. It is now read-only.
Hi, @oyeanuj - I do plan to eventually support React Route 4. I need to dive deeper into their API and implementation to come up with the right approach. Unfortunately, it's not something I'm actively working on since we have a lot of other priorities. If you have some ideas, please do not hesitate to share them with me.
@ctumolosus From my research so far, it seems the most flexible implementation would be to associate data fetching at a component level (regardless of whether it is a route component or not), and then use the strategy deployed here to make the fetch: ctrlplusb/react-universally#479 (comment) (someone using it for async components with RR4, but could totally be useful for redux-fetch)
Hope that can help!
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi @ctumolosus, thank you for open sourcing this library. Wondering if you are considering adding support for React Router v4 - especially with SSR?
The text was updated successfully, but these errors were encountered: