react-router-sitemap VS connected-react-router

react-router-sitemap hasn't been updated in years, to the point where there are dependency tree issues with react versions newer than 16.

You can also take a look at react-router-sitemap

A sitemap is a file where all details about your site’s videos, pages, and other forks are provided, along with the relationship between them. Being an intelligent search engine, Google reads this file to crawl into your site easily. React does not possess any inbuilt method to create sitemaps. If you use React Router to manage to route, you need to find tools to create a sitemap. Although, this might require some of your efforts.

connected-react-router : Helps to connect your route with the redux state.

So, I think many people are not familiar with the concept of integrating a router into the Store, but in fact they most likely met the Connected React Router library, it allows, for example, with successful authentication directly in the action, to redirect the user to the /profile or /dashboard page, this allows the authentication logic do not spread beyond the action. To begin with, we will write timings for the state of this store.

Even if I look at the basic example on their GitHub, there is a similar coding pattern.

For this use case, I would use https://github.com/supasate/connected-react-router to make it so changing the state is changing the URL and then just having a link action fire a navigation action.

Info on setting up linking and routing to pages: https://github.com/supasate/connected-react-router/blob/master/FAQ.md#how-to-navigate-with-redux-action

Connect react-router with redux: https://github.com/supasate/connected-react-router This will allow you to navigate via dispatching actions from the saga.