And once we're done, setting up our configuration essentially wants our front end application is running
the back, an application is running, we have the proxy and we use concurrently.
Now we can start finally setting up the logic.
So yes, I know we spent quite a long time on setting up the proxy and kind of progression, but it
was very important for me to showcase all the steps in detail because I know that I'm going to be getting
those questions at the end of the day and of course, Q&A anyway.
So I might as well cover that during the video because in the video, I can give you a visual representation.
So there was a small detour, but now we're back on track and the way it's going to work, we will set
up some logic on the back backend, which we already have for it is there.
So that's going to be the first thing we're set up.
And then we implement the logic on the frontend.
So set up the controller, then handle that on the front, then set up the controller, handle that
on the front and then hopefully you know where I'm going with this.
Now, when it comes to register, it's actually very similar to a logging.
And therefore, in order to show all the steps, I'll use log-in functionality from the complete project.
So that way you can clearly see because there's no point for me to register a new user again, they're
going to be very, very similar and the steps are falling where we want to provide the values, then
we'll invoke the request in this case to any longer than once the data comes back.
We'll set up the user token, the location in the components, and we'll also do that in a local storage.
So these are two steps.
And just to showcase how everything is going to look in the complete project, we're going to go here
with my dummy one and then I will provide the evaluation.
And once we click on Submit, we'll make a log and request.
And then if we're successful, we will direct the user towards the dashboard so programmatically navigate
them to the dashboard page.
And then when it comes to components, you'll notice that I will have my user token and location.
So let me make this one bigger.
And then once I scroll down notice, I'm going to have the info about the user that we're sending back,
whether that is an email, the last name and, you know, the rest.
And also, we have user location.
And then we have the token.
So all of these three factors and also we set them up in our local storage because when I refreshed
the page, I actually wanted to purchase them since when it comes to state, they're not going to be
persistent.
Now we do have the logic there in the app context, where every time we refresh the page, we will reset
them will basically grab them from the local storage.
But if, for example, I go here and I clean it out now, at the moment I will refresh.
They won't be there by default again.
That's one of the things with state and react.
It's not persistent between the page refreshes and once we know what we're going to be working on.
Essentially, the enregistre controller.
Now let's start following the steps.