So we made it to the end of section four, a pretty straightforward section.
And in this section we took a look at why we needed routing in a single page application.
Of course we're not routing between different pages.
We need to route between different components.
And we took a look at setting up React Router.
And as I mentioned that's the de facto way of dealing with routing in a react application.
So frequently asked questions.
Just one for this one.
Why not use React Router data fetching?
That tool, React Router does now come with data fetching functionality, and it is for sure an option
that we could use to do such a thing as fetching data.
And it is good functionality.
It does give us tight integration with our router, and that means we can fetch data tied directly to
specific routes, for example, and we could delay our route transitions until our data is effectively
loaded, ensuring that the data is available when our component mounts.
But I'm not going to take that approach.
There is another tool that we're going to use for data fetching, which offers more than React Router
data fetching does.
And this one that we're going to use provides global caching because it's integrated with what we're
going to take a look at next, which is Redux global state management for our application.
And that is coming up.