WEBVTT

00:00.000 --> 00:03.270
So we made it to the end of section four, a pretty straightforward section.

00:03.270 --> 00:08.040
And in this section we took a look at why we needed routing in a single page application.

00:08.040 --> 00:10.800
Of course we're not routing between different pages.

00:10.800 --> 00:13.320
We need to route between different components.

00:13.320 --> 00:15.960
And we took a look at setting up React Router.

00:15.960 --> 00:22.440
And as I mentioned that's the de facto way of dealing with routing in a react application.

00:22.440 --> 00:24.060
So frequently asked questions.

00:24.060 --> 00:24.990
Just one for this one.

00:24.990 --> 00:27.240
Why not use React Router data fetching?

00:27.240 --> 00:33.270
That tool, React Router does now come with data fetching functionality, and it is for sure an option

00:33.270 --> 00:36.780
that we could use to do such a thing as fetching data.

00:36.810 --> 00:38.010
And it is good functionality.

00:38.040 --> 00:43.290
It does give us tight integration with our router, and that means we can fetch data tied directly to

00:43.320 --> 00:50.430
specific routes, for example, and we could delay our route transitions until our data is effectively

00:50.430 --> 00:54.420
loaded, ensuring that the data is available when our component mounts.

00:54.420 --> 00:55.950
But I'm not going to take that approach.

00:55.950 --> 01:01.320
There is another tool that we're going to use for data fetching, which offers more than React Router

01:01.320 --> 01:02.430
data fetching does.

01:02.460 --> 01:08.310
And this one that we're going to use provides global caching because it's integrated with what we're

01:08.310 --> 01:15.060
going to take a look at next, which is Redux global state management for our application.

01:15.060 --> 01:16.350
And that is coming up.