After a lot of work we've now finally got this information about whether or not we are signed in.
Inside of our landing page.
The last thing we need to do is take a look at that current user prop if it is equal to nil.
We need to print out.
You are not signed in.
And if it is equal to well anything some kind of object as an I.D. or email inside of it then we will
print out you are signed in.
So let's flip back over and give this a shot.
Here's my landing page stuff.
I'm going to delete everything that's inside there right now.
I'll put in just a very simple ternary expression so I can return aren't user.
If that thing is defined I will show how about an H1 that says you are assigned in otherwise an H1 that
says you are not signed in and naturally we could probably just return a simple H1 and then use the
Turner expression side but I'll leave that up to you.
I'm gonna save that look back over and I will see that I am in fact signed it.
Now if you want to test this out with us being signed out.
Well we only have the ability to sign out of our application yet but we can manually tell her our application
to sign ourselves out.
Let me show you what I mean inside of my Chrome developer console.
I'm going to open up the very last little tab over here and find the one marked application inside of
here.
I'm going to find on the left hand nav cookies and I should be able to expand cookies like so select
this domain and it will show the cookie that is set for this domain so I can select that and then clear
all.
And now we should not have any cookie tied to ticketing but dev so if I now attempt to refresh I will
see you are not signed in.
Well I'd say this is looking like it's working out pretty well.
OK.
Well that's pretty much it for handling this kind of log in page or a domain landing page.
We still have to take care of the header and the sign and page as well.
So still a little bit of work left.
Quick pause right here and we'll continue in just a moment.