WEBVTT

1
00:00:01.579 --> 00:00:08.400
So, let's start by planning the REST API, the application we're going to build.

2
00:00:08.620 --> 00:00:15.680
Let's start by planning what exactly the API should look like, and I plan to build

3
00:00:15.680 --> 00:00:23.940
a REST API that allows users to create and share events with other users, events like

4
00:00:23.920 --> 00:00:31.200
meetups or going to a restaurant, and then users should also be able to register for

5
00:00:31.200 --> 00:00:34.500
events shared by others, that's the idea.

6
00:00:36.140 --> 00:00:41.480
And therefore this application should have a couple of core features, like for example

7
00:00:41.480 --> 00:00:43.340
user authentication.

8
00:00:44.560 --> 00:00:51.360
In order to create or edit or delete events, but also in order to register for events,

9
00:00:52.200 --> 00:00:58.140
users need to be authenticated, they need to be signed up with our application, because

10
00:00:58.140 --> 00:01:04.540
only registered users can create, edit or delete events or register for events or unregister

11
00:01:04.540 --> 00:01:06.680
for events they did register for.

12
00:01:08.180 --> 00:01:13.240
So these are some of the core features, user authentication and the entire event management

13
00:01:13.240 --> 00:01:13.680
part.

14
00:01:14.770 --> 00:01:20.800
In addition, I want to make sure that users can only edit or delete the events they created,

15
00:01:22.000 --> 00:01:27.880
so that I can't delete an event I did not create, that would not be great I'd argue.

16
00:01:29.440 --> 00:01:36.160
And the application will also have image upload, people when creating events should be able

17
00:01:36.160 --> 00:01:43.460
to upload a nice image, so that if we were to add a frontend to this application, which

18
00:01:43.460 --> 00:01:48.300
we won't do here, but if we were to do that, we could display that image.

19
00:01:49.600 --> 00:01:54.080
And we'll build the image upload functionality into this API, therefore.

20
00:01:55.220 --> 00:02:02.900
So a couple of features, it's not a super complex, but also not a super trivial REST

21
00:02:02.900 --> 00:02:09.460
API, and therefore I'd say it's the perfect example for using all these AI tools and building

22
00:02:09.460 --> 00:02:10.699
this as a demo project.