In last video we successfully redeployed our application and get our client side app to show up on the
screen.
And I want to look at some aspects of our application and get a little bit of a better sense about what's
going on here especially in relation to this diagram right here where we had spoken about some of the
different responsibilities of the Express server.
So the first thing I want to mention to you is if I go up to my address bar while I'm at my application
and I put in like Slash surveys like so you'll notice that the entire page reloads and I get sent over
to the dashboard component.
So when I change the address up here and press enter that makes an entirely new TTP request to our express
server.
Now of course as we mentioned the Express server has no idea what SLAs surveys is pointing at.
So the Express server says OK well do I have a file inside of my bill directory called surveys.
No I don't.
OK I guess I'll just go ahead and load up the html document that I have.
So the HMO document loads up inside of that HMO document.
If we look in to the body tag right here you'll notice that we've got right here right here right here.
One of the tags inside of here is a tag that points directly to our main dot G-S file.
So the XML document is responsible for then going back to the server trying to grab this very specific
file which Express does have so nodes to kind of lump it into its asset directory or the directory to
pull this file out.
The server responds with the DOT G-S file and the entire re-act application boots up when the re-act
application boots up re-act router then takes over and it decides on what components to show on the
screen depending upon the current route.
One thing I want to make sure is really clear at this point we've kind of very briefly touched on this
volonte.
Want to make sure it's really clear when we are using re-act router that is a client side navigation
routing library only so only once a user is inside of an HMO document with our javascript file loaded
up.
Does any of the re-act router rules take any effect whatsoever.
None of the reactor outer stuff is at all loaded up into Express.
None of the routing there is shared at all to prove that to you.
If I click on the logo over here and remember that the logo is a link tag that is rendered by re-act
router.
You'll notice that the entire page does not refresh.
Instead it's a very quick transition.
Well OK I can't go if the logo kicks me back to the same survey or the same dashboard Once that's a
bad example.
But essentially if this had been a link to go back to just the route route like that we would have seen
an instantaneous page change here because re-act rider was not refashioning the entire S.M. document.
It was just changing the set of components that were visible on the screen.
OK.
So now the very last thing I want to do here just to make sure that everything is working the way we
expect I should be able to click the log out button to log out.
Yup I'm able to Asheville to click log in with Google to get back in.
Yes I can I should still be able to add credits
put in my credit card number.
Ten twenty one two three.
And oops I put in a e-mail.
There we go.
And now I'm able to add some number of credits I should see my credits increase right there.
Yes I have five credits now.
OK.
So this is looking pretty darn awesome I think that we've definitely moved forward an additional step
here.
So I'm really happy with the deployment that we have so far.
And I think they are now ready to continue on in the next section and start working on our next feature.
So I'll see you in just a minute.