00:00:06.743 --> 00:00:08.053 Oh well that, I mean, yeah, fine.
00:00:08.063 --> 00:00:10.765 We'll just stop it and start it again when I'm doing really, you
00:00:10.765 --> 00:00:10.973 know.
00:00:16.213 --> 00:00:18.253 OK, so for whatever reason.
00:00:21.023 --> 00:00:25.143 The config is not showing in here.
00:00:25.213 --> 00:00:25.453 Why not?
00:00:27.563 --> 00:00:28.313 They're not loading.
00:00:28.383 --> 00:00:28.993 There it is.
00:00:29.103 --> 00:00:30.023 Didn't work the first time.
00:00:30.033 --> 00:00:30.513 That's weird.
00:00:36.663 --> 00:00:38.033 Do your job.
00:00:38.203 --> 00:00:38.613 Thank you.
00:00:38.963 --> 00:00:43.363 Alright, so as you guys know.
00:00:47.163 --> 00:00:48.363 Let's do it like.
00:00:51.633 --> 00:00:52.343 You know like this.
00:00:54.673 --> 00:00:56.953 Through and I'll just grab API OK.
00:00:59.623 --> 00:01:00.893 And then I'm going to create another file.
00:01:03.383 --> 00:01:04.273 App config.
00:01:06.903 --> 00:01:08.343 Example dot JSON.
00:01:11.763 --> 00:01:18.313 So let's pretend for a second that there are you guys ready.
00:01:18.383 --> 00:01:19.373 I wanna make sure you're ready.
00:01:19.383 --> 00:01:21.943 I I am actually legitimately going through Clint.
00:01:22.163 --> 00:01:24.623 So, OK, OK.
00:01:25.373 --> 00:01:25.833 All right.
00:01:25.993 --> 00:01:29.286 So in the config of course you guys know by now because you've
00:01:29.286 --> 00:01:32.735 worked here a long time, there's a ton of crap instead of config,
00:01:32.735 --> 00:01:34.983 and most of it actually does belong there.
00:01:35.553 --> 00:01:38.532 There's like subcontract debug and HTML5 mode and all the
00:01:38.532 --> 00:01:41.563 dashboards, settings and all that crap is in there, right?
00:01:42.183 --> 00:01:46.076 Umm, one of the things that's in there is all this stuff inside
00:01:46.076 --> 00:01:49.847 of routes, so there's and and and for everything under routes
00:01:49.847 --> 00:01:51.733 in different areas of the cart.
00:01:51.783 --> 00:01:55.428 Or I mean different areas of the site, so I'm going to copy like,
00:01:55.428 --> 00:01:58.853 I don't know, four more just that we have a better, you know,
00:01:58.853 --> 00:02:00.013 a better sample here.
00:02:00.973 --> 00:02:01.393 Umm.
00:02:02.323 --> 00:02:05.460 And then I'm going to actually format this so that it doesn't
00:02:05.460 --> 00:02:08.243 complain at me the whole time of doing this recording.
00:02:12.853 --> 00:02:13.073 It.
00:02:17.913 --> 00:02:18.173 Uh.
00:02:20.763 --> 00:02:24.333 And fruits divided by workup.
00:02:26.713 --> 00:02:32.423 OK, so this is what Seb config roots generally look like.
00:02:32.473 --> 00:02:35.103 There's more than these, right?
00:02:35.113 --> 00:02:37.293 But these are just like the first five.
00:02:38.213 --> 00:02:38.673 Umm.
00:02:40.393 --> 00:02:44.493 And the question you might ask is well, why have?
00:02:44.843 --> 00:02:46.113 Why have this filed all?
00:02:46.283 --> 00:02:47.873 Why have these sections at all?
00:02:48.263 --> 00:02:52.233 If the whole site is always the same route right?
00:02:52.323 --> 00:02:56.773 And the answer is well, in a site that only one stamp like
00:02:56.773 --> 00:03:01.149 normal standalone site like where we do everything we do,
00:03:01.149 --> 00:03:05.750 all the hosting we have, the databases, we host images, it's
00:03:05.750 --> 00:03:10.578 our API they hit and those sites there's no reason to have this
00:03:10.578 --> 00:03:11.483 file at all.
00:03:12.323 --> 00:03:15.353 Courts dot TS does absolutely nothing to help you.
00:03:15.823 --> 00:03:19.823 In fact, if it does anything, it probably hinders you a little.
00:03:19.823 --> 00:03:20.073 Umm.
00:03:22.063 --> 00:03:23.433 Why shouldn't say that it's not?
00:03:23.513 --> 00:03:25.722 Does absolutely nothing, but it doesn't do any early as much as
00:03:25.722 --> 00:03:26.033 it could.
00:03:26.243 --> 00:03:31.035 OK, when it when it starts to shine is when you have a
00:03:31.035 --> 00:03:33.823 situation like we have with PBC.
00:03:34.583 --> 00:03:41.753 So PAVC is hosted somewhere else by the client, right?
00:03:41.823 --> 00:03:42.673 It's not.
00:03:42.903 --> 00:03:44.883 The whole site is not stuffed.
00:03:46.073 --> 00:03:47.743 They're hosting their own site.
00:03:47.853 --> 00:03:50.783 This is not an out of box like SEF setup.
00:03:50.853 --> 00:03:52.603 There's no DNN on this site.
00:03:52.793 --> 00:03:54.283 For instance, they have their own CMS.
00:03:54.293 --> 00:04:00.021 We're putting stuff into and so the problem comes when, let's
00:04:00.021 --> 00:04:02.423 say you wanna show images.
00:04:03.793 --> 00:04:07.578 So like we're we're building our catalog for them, right,
00:04:07.578 --> 00:04:11.494 building everything but the catalog will and let's say that
00:04:11.494 --> 00:04:15.475 you want to have the images for the product and the Kellogg,
00:04:15.475 --> 00:04:18.543 right, which is pretty reasonable thing to do.
00:04:20.863 --> 00:04:22.723 So here I have an image right?
00:04:23.513 --> 00:04:28.455 Well, but but we are hosting this image on
00:04:28.455 --> 00:04:32.363 pc-stage.clarityclient.com right?
00:04:32.773 --> 00:04:36.862 Like our own site, the image is not being hosted by our client
00:04:36.862 --> 00:04:40.173 because they don't know what the image looks like.
00:04:40.643 --> 00:04:42.713 They don't know and they don't want to deal with the images.
00:04:43.163 --> 00:04:46.673 Right and like now, could this change in theory later?
00:04:46.683 --> 00:04:51.814 It could in theory, but for now they're getting images from us,
00:04:51.814 --> 00:04:55.983 but they're not getting this header from us, right?
00:04:56.073 --> 00:05:01.157 This header is still there stuff and hence the term court cross
00:05:01.157 --> 00:05:01.713 origin.
00:05:02.143 --> 00:05:02.503 Right.
00:05:02.513 --> 00:05:04.813 There's two origins for the site.
00:05:04.983 --> 00:05:08.455 There's the one hosting the images and there's the one
00:05:08.455 --> 00:05:12.306 hosting that right and then everything in the site is coming
00:05:12.306 --> 00:05:15.463 from one of the origins for the most part, right?
00:05:15.513 --> 00:05:18.531 All the catalogs coming from us, the header and the footer coming
00:05:18.531 --> 00:05:19.583 from them for instance.
00:05:20.903 --> 00:05:22.973 So what's that?
00:05:22.983 --> 00:05:30.489 You put a image in here and the normal way right is to leave out
00:05:30.489 --> 00:05:33.953 the URL like as in the domain.
00:05:34.103 --> 00:05:35.853 Sorry, not the whole URL, the domain.
00:05:36.483 --> 00:05:37.713 So let's say we just have this.
00:05:38.003 --> 00:05:38.993 Sorry, let me make it a little bigger.
00:05:40.503 --> 00:05:43.773 Let's say we just have images, ecommerce category images.
00:05:44.933 --> 00:05:47.175 Well, you both know because you're both good front end
00:05:47.175 --> 00:05:47.623 developers.
00:05:47.633 --> 00:05:52.240 You both know that the browser will just zoom whatever it's
00:05:52.240 --> 00:05:53.853 before the 1st slash.
00:05:54.163 --> 00:05:59.623 First slash should just match the domain of the site we're on,
00:05:59.623 --> 00:06:00.143 right?
00:06:00.153 --> 00:06:04.814 It should just match PVC liner to hbstest.net, but it would be
00:06:04.814 --> 00:06:09.476 wrong because people similary the HTTPS test.net does not have
00:06:09.476 --> 00:06:14.285 an images folder with ecommerce inside of it with content inside
00:06:14.285 --> 00:06:17.023 of it with place where inside of it.
00:06:18.863 --> 00:06:25.975 So the set of config tells us, hey, when you're loading images,
00:06:25.975 --> 00:06:32.976 pull them from PVC stage, not people two linear to hftest.net,
00:06:32.976 --> 00:06:33.643 right?
00:06:33.653 --> 00:06:35.383 Pull them from a different domain.
00:06:35.763 --> 00:06:40.001 That's the whole point of this route, or most of the point of
00:06:40.001 --> 00:06:41.163 this route thing.
00:06:41.333 --> 00:06:43.913 Evenings listing so here.
00:06:43.923 --> 00:06:48.393 What you can see we have API BCC stage ducklercline.com.
00:06:48.863 --> 00:06:50.303 Why did I have to set that setting?
00:06:52.763 --> 00:06:53.513 Not rhetorical.
00:06:53.603 --> 00:06:54.443 Well, I wanted to answer.
00:07:03.693 --> 00:07:07.421 To let the site know what it should be pinging and what it
00:07:07.421 --> 00:07:08.053 should be.
00:07:09.343 --> 00:07:09.583 Right.
00:07:10.783 --> 00:07:15.748 Because the everywhere we're hitting API like like I I don't
00:07:15.748 --> 00:07:20.958 know if you guys have seen this yet but and you I guess it's in
00:07:20.958 --> 00:07:22.993 the contact place, right.
00:07:24.163 --> 00:07:28.836 If it hasn't moved but here it does Axios dot default dot base
00:07:28.836 --> 00:07:33.360 URL and then does course link and then the area which is the
00:07:33.360 --> 00:07:34.473 third argument.
00:07:34.483 --> 00:07:38.863 Notice API here corresponds with API instead of roots, right?
00:07:40.813 --> 00:07:45.738 If this post is null, but to say that app setting isn't set,
00:07:45.738 --> 00:07:50.825 which it normally isn't, right, well then the root course link
00:07:50.825 --> 00:07:53.813 will resolve to is going to be what?
00:07:59.043 --> 00:08:00.793 What's the default route if you?
00:08:00.803 --> 00:08:02.913 If you're not explicit, like default domain.
00:08:02.923 --> 00:08:03.703 If you're not explicit.
00:08:04.073 --> 00:08:06.633 Just a slash, just the site itself.
00:08:07.463 --> 00:08:07.773 Right.
00:08:07.783 --> 00:08:12.406 It's this is itself which would be HFP which would be in our
00:08:12.406 --> 00:08:14.453 case right here that right.
00:08:14.943 --> 00:08:21.319 So it will assume a default of that while you and I, all three
00:08:21.319 --> 00:08:27.897 of us know with our human brains that in 200 HPS test.net is not
00:08:27.897 --> 00:08:33.868 hosting Sev Info, there's no penicillin to SS test on that
00:08:33.868 --> 00:08:35.993 slash desktop module.
00:08:36.003 --> 00:08:39.223 Plus clarity commerce Slash API storefront.
00:08:39.673 --> 00:08:42.723 Because it's not a step site, right?
00:08:42.793 --> 00:08:47.060 It's whatever the whatever the whatever the client is using a
00:08:47.060 --> 00:08:50.708 WS or their own stuff, or their own CMS or their own
00:08:50.708 --> 00:08:55.113 conglomerate of whatever like, but they found me useful, right?
00:08:55.163 --> 00:08:55.703 We don't.
00:08:55.713 --> 00:08:57.243 We're we're not hosting this like.
00:08:59.323 --> 00:09:00.323 So that's like ours.
00:09:02.563 --> 00:09:06.581 That a large part of my cores dot TS exists at all and why we
00:09:06.581 --> 00:09:07.553 need to use it.
00:09:08.243 --> 00:09:12.911 And of course you wanna use it in core because even though core
00:09:12.911 --> 00:09:17.068 isn't a core site, when you start using a core site, you
00:09:17.068 --> 00:09:21.225 don't want to have to get replaced every hard coded link
00:09:21.225 --> 00:09:24.143 everywhere with the course link, right?
00:09:25.593 --> 00:09:26.803 You want to just already be there.
00:09:28.383 --> 00:09:29.613 Yeah, that'd be a big lift.
00:09:30.553 --> 00:09:31.643 Yeah, and it is.
00:09:31.653 --> 00:09:33.893 And I've had to do some of that poor PC to work.
00:09:34.823 --> 00:09:39.383 Umm like one example I know of was and this is my fault right?
00:09:39.393 --> 00:09:39.973 Like so.
00:09:40.023 --> 00:09:45.163 No, no shade to anybody else, like in here.
00:09:46.733 --> 00:09:49.723 This path right here for the route for the catalog.
00:09:50.233 --> 00:09:55.103 It used to be slash catalog, right?
00:09:55.293 --> 00:10:00.754 But then, umm, people to Linears catalog is hosted at slash
00:10:00.754 --> 00:10:03.303 products, not slash catalog.
00:10:04.243 --> 00:10:08.657 So I submitted a PR expecting everything to work and didn't
00:10:08.657 --> 00:10:13.513 realize this path was hard coded so it didn't respect the catalog
00:10:13.513 --> 00:10:18.074 section of the the config and that section would have told it
00:10:18.074 --> 00:10:20.723 hey the root is flash products not.
00:10:22.973 --> 00:10:25.733 Black catalog like normal, right?
00:10:25.943 --> 00:10:29.733 So to enable this to be dynamic to where we don't have to.
00:10:29.793 --> 00:10:33.604 For instance, we don't have to do like a 301 redirect from
00:10:33.604 --> 00:10:37.802 slash cap from product to slash catalog because we just let them
00:10:37.802 --> 00:10:41.354 keep their URL because all we had to do is put the app
00:10:41.354 --> 00:10:45.488 setting, you know, put the upset again and this is just dynamic
00:10:45.488 --> 00:10:48.653 now and it works great and it's whatever, right.
00:10:50.543 --> 00:10:53.933 So does that make sense? Alex?
00:10:54.063 --> 00:10:56.053 I'm gonna ask you because you've been quieter.
00:10:56.143 --> 00:10:56.893 Does that make sense?
00:10:57.333 --> 00:11:00.793 We need to use this file like what?
00:11:00.443 --> 00:11:00.683 Yeah.
00:11:00.803 --> 00:11:01.543 What is purposes?
00:11:02.223 --> 00:11:05.138 Yeah, I didn't realize that you could actually like customize
00:11:05.138 --> 00:11:07.113 the route to catalog and stuff like that.
00:11:07.263 --> 00:11:07.883 That's pretty cool.
00:11:09.903 --> 00:11:10.763 Yeah you can.
00:11:11.483 --> 00:11:11.983 Umm.
00:11:13.563 --> 00:11:16.413 And I'll show you just in here a little more in example.
00:11:16.423 --> 00:11:19.500 So and like if we go keep looking at PC because again it's
00:11:19.500 --> 00:11:21.273 a, it is actually course website.
00:11:22.183 --> 00:11:26.770 Umm of course that up if you look in here, several of the
00:11:26.770 --> 00:11:29.933 hosts host is more or less just domain.
00:11:30.073 --> 00:11:37.782 OK, so don't let 3 go umm for the API and for the for the
00:11:37.782 --> 00:11:38.713 images.
00:11:39.713 --> 00:11:44.481 I had to explicitly set it to PVC stage because it was trying
00:11:44.481 --> 00:11:48.865 to get images from here and it was trying to hit our API
00:11:48.865 --> 00:11:52.633 endpoints from piece to linear to HTTPS on that.
00:11:52.783 --> 00:11:55.003 Suppose wouldn't work umm.
00:11:57.163 --> 00:12:03.063 So that is what it's primarily for is.
00:12:03.353 --> 00:12:05.647 And then here you can see another example going the other
00:12:05.647 --> 00:12:06.043 direction.
00:12:06.443 --> 00:12:13.032 So product detail, I had to tell Seth, hey, the product detail
00:12:13.032 --> 00:12:16.693 page is hosted on a different URL.
00:12:17.833 --> 00:12:23.013 It's not PC stage, it's PBC linear to https.net, right?
00:12:23.263 --> 00:12:27.508 I have to tell Seth so that it doesn't try to redirect to PVC
00:12:27.508 --> 00:12:31.684 sage when you click on a product detail link, right when you
00:12:31.684 --> 00:12:32.643 click on like.
00:12:35.023 --> 00:12:36.983 The product card name widget right here.
00:12:37.903 --> 00:12:42.946 This was redirecting to PVC stage declaredcline.com/product
00:12:42.946 --> 00:12:48.157 and making you leave the site and that's because the host for
00:12:48.157 --> 00:12:50.343 product detail wasn't set.
00:12:50.693 --> 00:12:51.773 Now Stephen knows.
00:12:51.823 --> 00:12:57.332 Oh, I'm being loaded into another website and that side is
00:12:57.332 --> 00:13:03.308 hosting the product detail page and I need to redirect to there
00:13:03.308 --> 00:13:09.471 so that was a mouthful, but that is that is largely what cores is
00:13:09.471 --> 00:13:13.113 for to make that whole process easier.
00:13:13.123 --> 00:13:17.462 So when we have cords, websites, we don't have to go build all
00:13:17.462 --> 00:13:21.663 this again or manually put in URLs in various places, right?
00:13:21.673 --> 00:13:24.395 Or build a component that memorizes what the what the path
00:13:24.395 --> 00:13:24.533 is.
00:13:25.403 --> 00:13:25.863 Umm.
00:13:26.243 --> 00:13:29.064 Because if you do that, then any other component that would also
00:13:29.064 --> 00:13:31.667 need to pass, how to use that component or duplicate it and
00:13:31.667 --> 00:13:33.273 you have to change paths everywhere.
00:13:33.283 --> 00:13:34.363 It's just being right.
00:13:35.793 --> 00:13:37.673 So that's what for.
00:13:39.003 --> 00:13:41.003 Hopefully I'll explain that faster in the video.
00:13:42.353 --> 00:13:43.823 Umm, OK.
00:13:44.873 --> 00:13:50.400 So walking through a coarse link actually does here this
00:13:50.400 --> 00:13:51.273 function.
00:13:53.163 --> 00:13:54.953 So what this what this function does?
00:13:54.963 --> 00:13:59.413 All the ones below it depend on it right towards image link,
00:13:59.413 --> 00:14:02.113 cores, props, link, core store link.
00:14:02.163 --> 00:14:06.228 All of these use correct link, so if you understand what cord
00:14:06.228 --> 00:14:10.294 link does then you'll understand what chords image link does,
00:14:10.294 --> 00:14:14.162 because this is basically the the meat potatoes of of this
00:14:14.162 --> 00:14:15.933 file is largely right here.
00:14:16.923 --> 00:14:21.013 Umm, so the first thing it does is says hey, there's no step
00:14:21.013 --> 00:14:24.968 config, there's no settings to read, just return null, you
00:14:24.968 --> 00:14:29.259 know, come back later when Steph Config is is not null and call
00:14:29.259 --> 00:14:33.483 me again because I can't give you any specialized data without
00:14:33.483 --> 00:14:37.506 having a path without having that company our two, which is
00:14:37.506 --> 00:14:40.523 the stupid name because there's no path one.
00:14:40.613 --> 00:14:45.673 But from what I've been told, we haven't brought uh.
00:14:45.683 --> 00:14:49.223 See Michael or what I've been told.
00:14:49.293 --> 00:14:54.293 We haven't brought all of the core stuff over from Angular
00:14:54.293 --> 00:14:59.632 still to this day, but all of this does it says hey is there a
00:14:59.632 --> 00:15:01.073 return URL token?
00:15:02.153 --> 00:15:06.383 In the past, we were given, right.
00:15:06.433 --> 00:15:12.535 So it's one of these, for instance, flash checkup plus
00:15:12.535 --> 00:15:16.973 check out had and return the URL equal.
00:15:18.063 --> 00:15:23.000 Itsyeah.google.com or flashbacks, calling whatever it
00:15:23.000 --> 00:15:27.663 is and having problem right now tip colon platter.
00:15:28.673 --> 00:15:33.753 OK, so all this function does swap returnurl token.
00:15:34.763 --> 00:15:40.905 Is it just remove this and that and put them in the uh URL
00:15:40.905 --> 00:15:46.943 encode character for that like in percent 7 or something.
00:15:47.813 --> 00:15:49.983 Whatever it is, it just puts them around return URL.
00:15:50.043 --> 00:15:50.563 That's all it is.
00:15:51.733 --> 00:15:53.583 Doesn't, umm.
00:15:56.163 --> 00:16:02.113 This one says if it's an absolute URL, as in the whole
00:16:02.113 --> 00:16:08.819 thing is there, it starts with HTTP or HTTPS then just return
00:16:08.819 --> 00:16:12.173 what they gave us with the umm.
00:16:13.313 --> 00:16:15.956 With this no cash thing with this just for cash busting,
00:16:15.956 --> 00:16:16.883 that's all it's for.
00:16:17.803 --> 00:16:18.203 Umm.
00:16:18.983 --> 00:16:22.406 But basically, it's like, hey, if you want to use force link
00:16:22.406 --> 00:16:25.830 for some weird reason and you want to put in the entire path
00:16:25.830 --> 00:16:27.233 actually hardcoded right?
00:16:27.273 --> 00:16:31.473 So you have a link somewhere and it's gonna go to.
00:16:33.383 --> 00:16:33.953 Gosh, I don't know.
00:16:35.153 --> 00:16:36.953 Go to somewhere very very unique.
00:16:39.243 --> 00:16:40.813 You've got, you know, you're doing this.
00:16:43.243 --> 00:16:45.193 You got the config and then you decide.
00:16:45.203 --> 00:16:50.396 Https school com because this is like only gonna be one place and
00:16:50.396 --> 00:16:54.723 it wouldn't be of any benefit to put it in Suh config.
00:16:55.163 --> 00:16:58.699 Then the cores link will just early out and just return you
00:16:58.699 --> 00:17:01.233 what what it what you gave it essentially.
00:17:02.373 --> 00:17:06.551 Umm, it's kind of stupid again in my opinion, because why even
00:17:06.551 --> 00:17:10.795 used chords link if you already have an absolute path but other
00:17:10.795 --> 00:17:14.575 than it does return your relative anything that's that's
00:17:14.575 --> 00:17:16.233 the only benefit of that.
00:17:16.293 --> 00:17:18.363 So, OK, so here's the part.
00:17:18.373 --> 00:17:20.634 I don't know if you're really paying attention, Alex, but this
00:17:20.634 --> 00:17:22.752 is the part that will actually help you in your day to day
00:17:22.752 --> 00:17:23.183 development.
00:17:23.433 --> 00:17:26.563 If you're like, what the hell is actually happening in this file
00:17:26.563 --> 00:17:27.093 right here?
00:17:27.153 --> 00:17:31.877 Line 171 this is where the magic actually everything you ever
00:17:31.877 --> 00:17:36.753 need to understand and adjust is all in these lines right here.
00:17:38.383 --> 00:17:42.013 Umm so area to use.
00:17:45.863 --> 00:17:46.803 Is just.
00:17:48.293 --> 00:17:51.543 Yeah, like this object.
00:17:52.913 --> 00:17:53.893 It's some objects.
00:17:56.353 --> 00:17:57.373 With a host in a root.
00:18:04.903 --> 00:18:09.033 It's a sub config dot roots at some area, so if you wondered
00:18:09.033 --> 00:18:12.824 when you pass in the third argument of area, how do you
00:18:12.824 --> 00:18:13.163 know?
00:18:13.303 --> 00:18:13.943 Like what?
00:18:13.953 --> 00:18:19.043 This is supposed to be like like site, cart, catalog etcetera.
00:18:19.353 --> 00:18:22.413 Well, they're all just keys of Seb config dot roots.
00:18:23.633 --> 00:18:24.053 That's all that.
00:18:24.143 --> 00:18:29.263 Is, umm and then it says hey, if we can't find an area then you
00:18:29.263 --> 00:18:32.543 just passed in garbage arguments, right.
00:18:33.503 --> 00:18:35.593 Uh, and we're not gonna handle it for you.
00:18:35.683 --> 00:18:36.493 Go screw yourself.
00:18:36.503 --> 00:18:39.643 We're turning early, then the root.
00:18:39.763 --> 00:18:45.390 All that this does is it adds the host and the root together
00:18:45.390 --> 00:18:51.202 or either one depending on what exists, which is a whole which
00:18:51.202 --> 00:18:53.693 makes it a bad name, right?
00:18:53.863 --> 00:18:58.233 So all it does is just add the domain and the root.
00:18:59.103 --> 00:19:06.044 So like if host is null but root isn't, then this will just be
00:19:06.044 --> 00:19:12.875 whatever root is and if host is truthy and root is null, then
00:19:12.875 --> 00:19:19.816 root will just be whatever host is, and if they're both truthy
00:19:19.816 --> 00:19:24.333 then root will be host plus root, right?
00:19:24.343 --> 00:19:25.533 So an API's case.
00:19:27.903 --> 00:19:29.243 It's gonna give you.
00:19:33.363 --> 00:19:37.976 In this example, I'm not really sure about that argument, but
00:19:37.976 --> 00:19:39.613 and this example easy.
00:19:44.803 --> 00:19:50.008 All that going to give you the whole path without the query
00:19:50.008 --> 00:19:54.173 parameters, that's what chords link group does.
00:19:56.333 --> 00:19:57.673 Have to use three.
00:19:59.933 --> 00:20:02.633 You just removed flashes, I think.
00:20:05.253 --> 00:20:07.573 I honestly don't fully understand what it does.
00:20:10.613 --> 00:20:12.163 Have to and and.
00:20:14.663 --> 00:20:18.759 During the beginning, look for forward Slash in the whole
00:20:18.759 --> 00:20:19.253 string.
00:20:21.623 --> 00:20:23.573 I tested against PATH 2.
00:20:27.963 --> 00:20:29.103 I don't really know what this says.
00:20:30.233 --> 00:20:33.413 Some sort of garbage with with the, I won't say that in the
00:20:33.413 --> 00:20:36.223 real recording, but some sort of garbage with regex.
00:20:36.493 --> 00:20:38.563 I'm not really sure what the point of this line is at all.
00:20:39.483 --> 00:20:39.823 Umm.
00:20:41.263 --> 00:20:43.503 And then this says, hey, if there's a root.
00:20:44.313 --> 00:20:50.015 So if this is truthy and path to use three, which again I don't
00:20:50.015 --> 00:20:55.717 know what this is, but I think it's normally truthy, it ends up
00:20:55.717 --> 00:20:58.033 normally being truthy and.
00:21:00.543 --> 00:21:01.543 See, this is one of those times.
00:21:01.553 --> 00:21:03.991 Somebody should save this like in a variable because I I
00:21:03.991 --> 00:21:05.573 literally don't know what this does.
00:21:06.833 --> 00:21:07.773 If there's a root.
00:21:11.433 --> 00:21:14.290 And path to use three ends up actually being something other
00:21:14.290 --> 00:21:15.133 than an MG string.
00:21:21.843 --> 00:21:22.743 We're gonna talk about.
00:21:22.943 --> 00:21:24.813 I mean, I'm not doing a real recording yet, so.
00:21:27.813 --> 00:21:31.351 No, I was just gonna say I I think that regex might just be
00:21:31.351 --> 00:21:35.183 checking to see if that forward slash is already there and if it
00:21:35.183 --> 00:21:37.483 if it's not there the IT would add it.
00:21:36.813 --> 00:21:37.083 Umm.
00:21:37.673 --> 00:21:39.093 That's my guess, but I don't know.
00:21:40.953 --> 00:21:41.403 Yeah.
00:21:41.413 --> 00:21:45.138 So you're thinking that like what this does is add flash if
00:21:45.138 --> 00:21:45.573 needed.
00:21:46.463 --> 00:21:47.193 That's what I think.
00:21:48.643 --> 00:21:53.433 Or add I guess add beginning slash if needed.
00:21:53.193 --> 00:21:55.443 I'm not sure where it where it's adding it.
00:21:53.483 --> 00:21:54.003 Yeah, that's.
00:21:57.763 --> 00:22:00.243 OK, here and neither has like a test.
00:22:00.253 --> 00:22:05.297 Both of these right and then if they're both truthy, it doesn't
00:22:05.297 --> 00:22:06.243 do anything.
00:22:06.613 --> 00:22:10.996 Otherwise it adds a forward flash and then it adds path to
00:22:10.996 --> 00:22:11.813 or nothing.
00:22:13.873 --> 00:22:14.663 I think you're right.
00:22:14.703 --> 00:22:18.923 Actually, I thought, yeah, I'm beginning flash if needed, OK.
00:22:21.853 --> 00:22:24.543 So the myth tech is there a route in the area?
00:22:25.843 --> 00:22:29.263 Do we have at least the flash or stuff after that?
00:22:30.413 --> 00:22:34.213 And that's the root.
00:22:40.993 --> 00:22:42.833 Half the test of this.
00:22:50.103 --> 00:22:52.253 Even weird stuff.
00:22:52.293 --> 00:22:53.153 I don't know what it does.
00:22:57.113 --> 00:23:03.063 OK, OK, not entirely sure what that does for some.
00:23:03.103 --> 00:23:09.198 Some reason it shortens the path to use three to to something
00:23:09.198 --> 00:23:11.853 else, but I'm not sure why.
00:23:12.143 --> 00:23:16.477 No over here, but not which is horrible, but enough swap
00:23:16.477 --> 00:23:21.419 returned URL token again, which I'm not entirely sure why that's
00:23:21.419 --> 00:23:24.993 there because you already handle that up here.
00:23:25.113 --> 00:23:29.545 I'm guessing it's because the query params like the params
00:23:29.545 --> 00:23:34.202 body could have the return URL and this would remove it again
00:23:34.202 --> 00:23:34.503 umm?
00:23:36.593 --> 00:23:41.763 And then all this does very super duper simple is.
00:23:44.723 --> 00:23:47.983 Return post plus fruit plus.
00:23:51.243 --> 00:23:51.603 Different.
00:23:53.703 --> 00:23:53.963 Right.
00:23:56.333 --> 00:24:00.394 So in this example, notice we probably wouldn't have
00:24:00.394 --> 00:24:01.773 perimeters, right?
00:24:01.943 --> 00:24:05.173 But if you passed in like and you know.
00:24:08.483 --> 00:24:08.853 I don't know.
00:24:12.693 --> 00:24:17.581 It would be helpful and I've tried to do it, but it's it's a
00:24:17.581 --> 00:24:18.783 little bizarre.
00:24:18.853 --> 00:24:19.593 We could do it though.
00:24:19.623 --> 00:24:20.283 Let's try doing it.
00:24:21.013 --> 00:24:24.053 Umm, you know?
00:24:24.063 --> 00:24:31.135 So if you had something else here like and uh calf counter
00:24:31.135 --> 00:24:33.173 people one right.
00:24:33.723 --> 00:24:36.603 Well, up here the params body.
00:24:39.463 --> 00:24:41.003 Brandon Body would look like.
00:24:46.933 --> 00:24:47.413 Umm.
00:24:51.273 --> 00:24:57.763 Will look like this cache counter one right and then this.
00:24:58.333 --> 00:25:02.388 This function append query string append query string
00:25:02.388 --> 00:25:07.043 params just turns this object of cache counter one into cache
00:25:07.043 --> 00:25:11.323 counter equal one with an ampersand like so that the URL
00:25:11.323 --> 00:25:15.153 the URL can have it in a like parsed friendly way.
00:25:16.533 --> 00:25:17.953 Uh, so that's all that does.
00:25:24.583 --> 00:25:24.803 So.
00:25:27.563 --> 00:25:30.344 Flowers and I'm not sure if you feel like an expert now, but
00:25:30.344 --> 00:25:33.125 hopefully you at least have some idea of what's happening in
00:25:33.125 --> 00:25:33.353 here.
00:25:34.373 --> 00:25:36.723 Uh now.
00:25:36.573 --> 00:25:37.523 It's really helpful.
00:25:37.573 --> 00:25:41.083 Honestly, like some of those comments, that would be great.
00:25:41.093 --> 00:25:44.673 Like to commit those so that we could always refer back to them.
00:25:45.523 --> 00:25:46.373 It would have been helped.
00:25:46.383 --> 00:25:46.643 Would have.
00:25:48.133 --> 00:25:48.483 OK.
00:25:48.543 --> 00:25:52.705 Well, hey, if meant if in James will let me do it, I will be
00:25:52.705 --> 00:25:56.936 glad to put it in here or what I can do is, uh, we could just
00:25:56.936 --> 00:26:01.371 make a good new cleaner article or find an existing one and then
00:26:01.371 --> 00:26:05.533 we can bookmark it and just start sharing it with everybody.
00:26:06.003 --> 00:26:06.263 Yeah.
00:26:08.393 --> 00:26:12.071 And like we can even put it in the onboarding certification
00:26:12.071 --> 00:26:14.523 like you have to go read this you know.
00:26:15.683 --> 00:26:19.445 I had no idea what area was before this training, so that
00:26:19.445 --> 00:26:20.613 was that was huge.
00:26:21.003 --> 00:26:24.705 Just knowing like where that's coming from and Seth config and
00:26:21.503 --> 00:26:21.673 Yeah.
00:26:24.705 --> 00:26:26.703 what just what area actually was.
00:26:27.473 --> 00:26:31.004 Yeah, that that is like where the coin starts to drop and that
00:26:27.783 --> 00:26:28.983 Yeah, I thought this is great.
00:26:31.004 --> 00:26:34.311 that that is the only reason when I figured that out, that
00:26:34.311 --> 00:26:37.731 was the only way I understood what was going on in this file
00:26:37.731 --> 00:26:38.123 at all.
00:26:38.493 --> 00:26:40.633 Like that was the thing that was huge.
00:26:39.123 --> 00:26:44.097 Also, that step would like where host and root are connected that
00:26:44.097 --> 00:26:47.413 I had no idea like what was going on there.
00:26:47.713 --> 00:26:49.183 So that was very helpful as well.
00:26:50.913 --> 00:26:51.603 Yeah.
00:26:51.773 --> 00:26:53.593 And they're really poorly named.
00:26:54.713 --> 00:27:01.303 Like really host could be called domain in my opinion.
00:27:02.133 --> 00:27:02.843 I agree.
00:27:02.893 --> 00:27:04.533 Ohh man that that just like.
00:27:05.403 --> 00:27:06.873 Yeah, you connected the dots.
00:27:07.433 --> 00:27:08.953 Root is like that.
00:27:08.503 --> 00:27:08.683 Yeah.
00:27:09.023 --> 00:27:11.703 That threw me off in until this meeting.
00:27:13.173 --> 00:27:18.531 OK, well, I'm glad I'm glad that I have opened the the the gates
00:27:18.531 --> 00:27:19.273 a little.
00:27:19.283 --> 00:27:20.633 Then that makes me happy.
00:27:21.433 --> 00:27:27.667 Umm yeah, the root is just whatever comesafter.com without
00:27:27.667 --> 00:27:29.463 query parameters.
00:27:30.453 --> 00:27:31.613 I got you, OK.
00:27:31.873 --> 00:27:36.523 So the root of the catalog, normally it's slash catalog,
00:27:36.523 --> 00:27:37.013 right?
00:27:37.163 --> 00:27:38.973 The root of checkout is slash.
00:27:38.983 --> 00:27:44.433 Checkout the root of home is nothing right?
00:27:44.443 --> 00:27:45.133 It's just a flash.
00:27:45.583 --> 00:27:49.854 The root of the dashboard is watch dashboard and then of
00:27:49.854 --> 00:27:51.653 course it can be nested.
00:27:51.663 --> 00:27:56.800 So like the root of signing in without a modal is flash
00:27:56.800 --> 00:28:00.103 authentication slash sign in right?
00:28:00.173 --> 00:28:04.293 It's the whole that whole thing that's considered the root.
00:28:05.853 --> 00:28:09.353 So, OK, OK, cool.
00:28:09.013 --> 00:28:09.833 Yeah, that was lovely.
00:28:09.363 --> 00:28:12.975 Well then, when I do the recording, I'm definitely going
00:28:12.975 --> 00:28:16.143 to keep both of these screens up right here. Umm.
00:28:15.353 --> 00:28:15.963 Yes.
00:28:16.013 --> 00:28:21.339 And honestly, like if you could even like put a comment in get
00:28:21.339 --> 00:28:26.327 James to approve it where host like equals domain that was
00:28:26.327 --> 00:28:28.103 hugely helpful to me.
00:28:28.753 --> 00:28:30.383 Dude, I'll just change it, man.
00:28:30.393 --> 00:28:30.873 I'm not scared.
00:28:32.383 --> 00:28:32.513 But.
00:28:34.173 --> 00:28:38.336 The only problem is we would have to go change it in the back
00:28:38.336 --> 00:28:41.693 end too so that it's actually says domain, right?
00:28:42.123 --> 00:28:45.706 That would be the only which would take longer than we have
00:28:42.163 --> 00:28:42.383 Yeah.
00:28:45.706 --> 00:28:46.363 today. Umm.
00:28:49.363 --> 00:28:51.093 Yeah, that that helped a lot.
00:28:49.433 --> 00:28:50.253 Yeah, host.
00:28:51.343 --> 00:28:52.953 Even just knowing now.
00:28:52.963 --> 00:28:53.543 Like what?
00:28:53.943 --> 00:28:55.303 What those are referring to?
00:28:55.363 --> 00:28:58.994 Like I I'm in a much better spot than I was before, but yeah,
00:28:58.994 --> 00:29:01.513 those comments that that's hugely helpful.
00:29:01.523 --> 00:29:04.847 Just to be able to refer back to it, I know it's not best
00:29:04.847 --> 00:29:06.223 practice, but it's nice.
00:29:06.343 --> 00:29:06.463 Yeah.
00:29:08.983 --> 00:29:09.683 Yeah. OK.
00:29:14.393 --> 00:29:14.643 Yeah.
00:29:14.653 --> 00:29:15.463 Nice job, man.
00:29:16.743 --> 00:29:17.093 Thank you.
00:29:17.693 --> 00:29:21.316 Coors is so hard for me to wrap my head around and it's gonna
00:29:18.203 --> 00:29:18.543 I've been.
00:29:21.316 --> 00:29:24.823 continue to be hard for me to wrap my head around, but it's
00:29:24.823 --> 00:29:25.583 good to have.
00:29:25.593 --> 00:29:28.803 Like it'll it will be good to have something to refer back to.
00:29:28.813 --> 00:29:32.642 So this is definitely one topic that I'm gonna have to utilize
00:29:31.233 --> 00:29:31.373 Yeah.
00:29:32.642 --> 00:29:33.493 in the future.
00:29:35.433 --> 00:29:37.073 Yeah, well, good.
00:29:38.113 --> 00:29:42.163 Umm, I want to figure out what this says before I record it.
00:29:42.173 --> 00:29:43.123 So if there's a root.
00:29:45.763 --> 00:29:46.173 And.
00:29:50.443 --> 00:29:51.223 How are you?
00:29:54.413 --> 00:29:56.643 Ohh this is yeah, OK, this is not bad.
00:29:56.653 --> 00:29:57.893 Look, so start at the beginning.
00:29:59.153 --> 00:30:00.473 It's scape a character.
00:30:01.743 --> 00:30:05.013 Look for a backflash right?
00:30:05.333 --> 00:30:12.309 So it's looking for a backslash at the beginning of Path 2, so
00:30:12.309 --> 00:30:12.863 does.
00:30:12.923 --> 00:30:15.520 Is there a backflash or I'm sorry forward flash is there
00:30:15.520 --> 00:30:17.433 forward slash at the beginning of PATH 2?
00:30:20.063 --> 00:30:26.917 Which it's kind of weird that it uses that instead of route to
00:30:26.917 --> 00:30:27.243 me.
00:30:28.653 --> 00:30:29.343 Umm.
00:30:33.483 --> 00:30:37.559 That would be nice if instead of like path to if it was root 2 or
00:30:37.559 --> 00:30:40.523 host two or whichever one it's like a amending.
00:30:39.673 --> 00:30:39.793 Yeah.
00:30:42.163 --> 00:30:45.603 Yeah, the naming doesn't make any sense. Umm.
00:30:48.793 --> 00:30:56.415 Anyway, OK, so if there's a route and after use so and
00:30:56.415 --> 00:31:02.513 there's any path at all, right after you 3.
00:31:09.603 --> 00:31:10.043 I mean, yeah.
00:31:12.493 --> 00:31:14.583 Is it almost always true path to you?
00:31:14.593 --> 00:31:15.593 Three is almost always true.
00:31:15.603 --> 00:31:18.172 The only time it's not true is when you just pass in no path,
00:31:18.172 --> 00:31:20.493 which is kind of stupid because it's required argument.
00:31:21.613 --> 00:31:26.213 So as far as I can tell, like this is the useless check.
00:31:26.223 --> 00:31:28.653 I don't know why it's there at all. Umm.
00:31:27.983 --> 00:31:31.746 Yeah, but you're completely right, since that is required
00:31:31.746 --> 00:31:33.823 argument that that is pointless.
00:31:33.363 --> 00:31:33.543 Yeah.
00:31:34.753 --> 00:31:36.543 Yeah, like no one time.
00:31:36.553 --> 00:31:41.185 It matters if you possibly could import this function into it in
00:31:41.185 --> 00:31:45.746 plain JavaScript file and then you wouldn't have any TypeScript
00:31:45.746 --> 00:31:50.235 support, but all of our code is in except except for index dot
00:31:49.953 --> 00:31:50.213 Right.
00:31:50.235 --> 00:31:52.943 JS and I want a N dot J those two so.
00:31:56.993 --> 00:31:57.283 And then.
00:32:04.053 --> 00:32:06.333 And have to use 3.
00:32:09.033 --> 00:32:10.813 Start with the root.
00:32:11.443 --> 00:32:12.193 That's what that says.
00:32:18.693 --> 00:32:19.263 OK.
00:32:19.333 --> 00:32:20.413 Yeah, that makes sense.
00:32:22.163 --> 00:32:22.733 I don't know.
00:32:22.793 --> 00:32:26.088 I still haven't figure out what the purpose of this whole check
00:32:26.088 --> 00:32:29.229 is, but I think that's what the last part after the last you
00:32:29.229 --> 00:32:30.053 know after here.
00:32:30.093 --> 00:32:31.063 I think that's what that does.
00:32:36.543 --> 00:32:36.823 So.
00:32:43.113 --> 00:32:48.883 Then what does it do then?
00:32:48.933 --> 00:32:52.043 Reassign how to use 3.
00:32:57.413 --> 00:32:57.843 To be.
00:33:13.913 --> 00:33:14.683 I'm string.
00:33:16.253 --> 00:33:18.713 What does substring do in JavaScript?
00:33:20.283 --> 00:33:20.883 I can't remember.
00:33:20.893 --> 00:33:21.633 I'll stop by head.
00:33:21.413 --> 00:33:22.783 You have to Google that one.
00:33:22.833 --> 00:33:28.019 I'm I'm thinking that that line may chop off everything like all
00:33:28.019 --> 00:33:32.726 any query params or anything that comes after the like the
00:33:32.726 --> 00:33:34.003 meat of the URL.
00:33:35.013 --> 00:33:37.313 I think that might be what's happening there.
00:33:43.443 --> 00:33:44.663 So to use to.
00:33:49.523 --> 00:33:54.274 Ohh no, it's taking OK so it takes everything after the index
00:33:54.274 --> 00:33:55.423 it's passed in.
00:33:56.303 --> 00:34:01.110 Yeah, so this is removing the beginning, then a path to use,
00:34:00.043 --> 00:34:00.283 Yep.
00:34:01.110 --> 00:34:01.583 right?
00:34:09.473 --> 00:34:09.773 So then.
00:34:12.973 --> 00:34:19.343 Remove we've beginning of how to you 3.
00:34:27.073 --> 00:34:28.623 Like what is the point of this code?
00:34:30.743 --> 00:34:35.203 I have no idea that that chunk there I I don't.
00:34:35.253 --> 00:34:39.231 I don't understand that all, but I if we could step through like
00:34:39.231 --> 00:34:43.026 debug and just step through, I think it would make a lot more
00:34:43.026 --> 00:34:46.883 sense just to like hover over and see what each variable is at
00:34:44.013 --> 00:34:44.153 Yeah.
00:34:46.883 --> 00:34:48.413 each step of the process.
00:34:49.983 --> 00:34:50.893 What's in here then?
00:34:50.943 --> 00:34:51.343 Let's do.
00:34:54.063 --> 00:34:56.533 Actually I already have the file open because apparently I was.
00:34:56.543 --> 00:34:56.953 I was.
00:34:57.013 --> 00:35:01.733 I was playing around here so OK, so we put a break point here and
00:35:01.733 --> 00:35:05.880 we'll make it conditional and we'll own, say only if area
00:35:05.880 --> 00:35:06.953 equals the API.
00:35:07.933 --> 00:35:08.243 Umm.
00:35:08.273 --> 00:35:12.941 And the only reason I'm gonna do that is because we know the API
00:35:12.941 --> 00:35:15.813 actually has a host and a route, right?
00:35:15.053 --> 00:35:16.253 Yes, that's good talk.
00:35:15.933 --> 00:35:18.473 So what happens if they're both truthy?
00:35:18.623 --> 00:35:19.303 So OK.
00:35:28.173 --> 00:35:31.173 And I guess we never hit it.
00:35:33.433 --> 00:35:36.143 OK, I won't use API.
00:35:40.213 --> 00:35:42.033 What if we use images that might be better?
00:35:55.143 --> 00:35:56.413 OK, never mind.
00:35:56.423 --> 00:35:58.123 We'll just what is headed no matter what.
00:36:06.873 --> 00:36:08.723 My phone crazy here.
00:36:08.773 --> 00:36:09.603 Why am I not hitting?
00:36:12.543 --> 00:36:13.343 It might not hitting this.
00:36:18.013 --> 00:36:18.893 They have no idea.
00:36:21.533 --> 00:36:22.273 That's a conflict.
00:36:23.773 --> 00:36:24.293 Is the thing.
00:36:27.733 --> 00:36:30.187 Like it's always truthy, and yet I'm never hitting the next
00:36:30.187 --> 00:36:30.433 slide.
00:36:34.453 --> 00:36:37.842 Which could only mean that the cores link function is not being
00:36:37.842 --> 00:36:38.213 called.
00:36:41.803 --> 00:36:42.553 Well, here we go.
00:36:42.643 --> 00:36:45.253 I mean, when I step over.
00:36:46.613 --> 00:36:50.264 OK, well, when I step over it works, but when I I don't know
00:36:50.264 --> 00:36:50.503 man.
00:36:50.593 --> 00:36:51.113 That's weird.
00:36:51.853 --> 00:36:54.613 OK so here you can see the area is API.
00:36:53.913 --> 00:36:55.063 OK, you yeah.
00:36:55.073 --> 00:36:56.513 You. Umm.
00:36:56.573 --> 00:37:00.163 I'm not sure why it wasn't hitting here when I hit
00:37:00.163 --> 00:37:03.823 continue, but uh, here's these two areas API right?
00:37:04.893 --> 00:37:08.903 And then path to because there is no return URL token.
00:37:05.183 --> 00:37:05.403 Yep.
00:37:11.203 --> 00:37:11.893 Well, I'm sorry.
00:37:11.903 --> 00:37:13.793 Do you want me to go back and, like, go into this?
00:37:17.233 --> 00:37:17.903 Hold on a second.
00:37:17.913 --> 00:37:20.463 Hover over path two or help hover over.
00:37:20.613 --> 00:37:22.563 Ohh I could see path OK so.
00:37:22.673 --> 00:37:24.643 Yeah, after this, that.
00:37:25.863 --> 00:37:30.913 And because there is no return URL token in here, all it is.
00:37:30.293 --> 00:37:31.423 Tattoos this same.
00:37:31.943 --> 00:37:32.893 How to just the same?
00:37:33.423 --> 00:37:33.853 OK.
00:37:33.903 --> 00:37:34.933 Yep, I'm good with that.
00:37:34.943 --> 00:37:37.493 And you did a good job explaining what that is.
00:37:37.963 --> 00:37:39.283 So you don't need to do that again.
00:37:39.763 --> 00:37:43.500 And and by the way, this is always the case with every link
00:37:43.500 --> 00:37:45.743 and stuff right now like this line.
00:37:44.703 --> 00:37:48.093 Yeah, I've I've never seen the URL token in my life.
00:37:48.103 --> 00:37:51.343 Actually, that was the first time I've ever, like, actually
00:37:51.343 --> 00:37:51.613 seen.
00:37:51.623 --> 00:37:53.928 What it looks like whenever you typed it out, but I've never
00:37:53.928 --> 00:37:54.533 seen one before.
00:37:54.813 --> 00:37:58.320 OK, it's to my knowledge we don't use it in anything modern
00:37:58.320 --> 00:38:02.003 except like I didn't know if we were using it when I got here,
00:38:02.003 --> 00:38:03.523 but it's been a long time.
00:38:03.533 --> 00:38:05.183 If we did so, OK.
00:38:05.223 --> 00:38:06.243 So then this check.
00:38:06.293 --> 00:38:09.623 Hey, does the root or or?
00:38:09.633 --> 00:38:16.817 Sorry, does the path that we got right start with HTTP and we
00:38:16.817 --> 00:38:18.903 know that doesn't?
00:38:21.223 --> 00:38:21.533 Right.
00:38:21.863 --> 00:38:23.273 So this is just if you're gonna.
00:38:22.143 --> 00:38:22.363 Yep.
00:38:23.283 --> 00:38:27.197 If you're gonna pass in google.com and for some reason
00:38:27.197 --> 00:38:31.823 you're gonna use towards link to do it, this will core link will
00:38:31.823 --> 00:38:36.307 just get out of your way and say hey, clearly you want to make
00:38:36.307 --> 00:38:37.303 your own link.
00:38:37.353 --> 00:38:38.183 You know what you're doing?
00:38:38.193 --> 00:38:39.403 We'll leave you alone, right?
00:38:39.753 --> 00:38:40.633 So it's not going to go there.
00:38:41.833 --> 00:38:42.183 OK.
00:38:42.193 --> 00:38:43.293 And then area to youth?
00:38:43.303 --> 00:38:44.673 Here's exactly what I copied.
00:38:44.683 --> 00:38:46.493 You'll see area to you.
00:38:46.503 --> 00:38:51.183 It's just post, which is essentially domain and route
00:38:51.183 --> 00:38:51.703 right?
00:38:52.713 --> 00:38:56.083 So the step config is telling course linked right now.
00:38:56.373 --> 00:39:02.207 Hey the API is hosted at pbcstage.client.com and the part
00:39:02.207 --> 00:39:08.141 after com the root is desktop modules clarity commerce API
00:39:08.141 --> 00:39:14.478 storefront which you might think this is kind of redundant but
00:39:14.478 --> 00:39:21.016 actually for sites that are not DNN this could just be slash API
00:39:21.016 --> 00:39:22.123 storefront.
00:39:23.653 --> 00:39:23.893 OK.
00:39:25.063 --> 00:39:26.813 Right, because that's that module clarity.
00:39:26.823 --> 00:39:30.911 Commerce is only used because DNN has a desktop modules and
00:39:30.911 --> 00:39:35.272 clarity commerce folder which we committed the clarity commerce
00:39:35.272 --> 00:39:35.953 one right.
00:39:36.293 --> 00:39:39.763 But that's the only reason that you're you're so used to that.
00:39:39.773 --> 00:39:43.150 But if you go to a FP FP does it use DNN and the root is just
00:39:43.150 --> 00:39:45.765 slash API storefront, so it doesn't get changed
00:39:45.765 --> 00:39:46.473 occasionally.
00:39:46.483 --> 00:39:49.353 But anyway, OK, so we have an area to use.
00:39:49.573 --> 00:39:51.253 The API was valid, right?
00:39:51.263 --> 00:39:56.678 It's a valid key and sub config dot roots and then we're going
00:39:56.678 --> 00:40:01.577 to get the full route which we'll just end up being post
00:40:01.577 --> 00:40:02.523 plus route.
00:40:03.523 --> 00:40:04.773 So, but I'll step into it.
00:40:04.783 --> 00:40:09.501 So we can actually see what it does, so here it gets the area
00:40:09.501 --> 00:40:14.295 again and then throws again if we if it doesn't find it, which
00:40:14.295 --> 00:40:18.936 is kind of dumb, right because cores link already checked us
00:40:18.936 --> 00:40:21.143 already checked that for umm.
00:40:21.973 --> 00:40:26.368 Then it says if a host is not provided by lookup, which in our
00:40:26.368 --> 00:40:28.043 case is not, it's false.
00:40:28.083 --> 00:40:31.703 It's undefined in our case, but it's always false.
00:40:31.833 --> 00:40:33.623 I haven't figured out why it's even there.
00:40:34.053 --> 00:40:36.630 Like Jesse said, it's probably 5 years old and no one uses it
00:40:36.630 --> 00:40:36.963 anymore.
00:40:38.263 --> 00:40:40.723 Then just go into chords link root inner.
00:40:42.753 --> 00:40:43.413 Let's go in there.
00:40:47.123 --> 00:40:48.913 It didn't step in what in the world?
00:40:53.273 --> 00:40:54.563 I don't know why I stop.
00:40:54.573 --> 00:40:55.023 I pressed.
00:40:57.163 --> 00:40:59.103 I pressed to go in, but it didn't do it.
00:41:00.083 --> 00:41:00.483 How weird.
00:41:02.903 --> 00:41:06.475 Well, anyway, you can see as I was going to tell you, all it
00:41:06.475 --> 00:41:09.403 does is just add the host and the route together.
00:41:10.013 --> 00:41:13.963 It basically gives you a full URL right?
00:41:13.863 --> 00:41:14.093 Get.
00:41:14.203 --> 00:41:16.701 And if if you go up here and look at the code, it's not that
00:41:16.701 --> 00:41:17.193 complicated.
00:41:17.383 --> 00:41:19.993 Hey, there's no host and no root return, nothing.
00:41:20.203 --> 00:41:23.093 If there's not a host but there is a root, return the root.
00:41:23.403 --> 00:41:26.253 If there is a host and not a root, return the host.
00:41:26.463 --> 00:41:27.993 If there's both return to boost.
00:41:29.353 --> 00:41:29.933 Makes sense?
00:41:30.743 --> 00:41:35.013 Forgot that that very it's very simple function umm.
00:41:37.223 --> 00:41:41.042 But then phase three is copied for no good reason at all, as
00:41:41.042 --> 00:41:44.862 far as I can tell, because all it is is just a copy of route
00:41:44.862 --> 00:41:45.613 stupid line.
00:41:47.223 --> 00:41:52.125 This is just gonna add the forward slash here if it's
00:41:52.125 --> 00:41:57.481 missing and you can see for instance with the cart path it
00:41:57.481 --> 00:42:03.199 is missing because I forgot to put it like and and override so
00:42:03.199 --> 00:42:08.555 it's going to happily put the slash there for me because I
00:42:08.555 --> 00:42:09.463 forgot it.
00:42:10.583 --> 00:42:11.063 Makes sense?
00:42:10.853 --> 00:42:14.423 I thought that so, which is actually kind of cool.
00:42:14.433 --> 00:42:17.841 That's kind of this should really be its own function and
00:42:17.841 --> 00:42:21.720 just say, you know, it should be called like add forward slash if
00:42:21.720 --> 00:42:25.363 missing, but they just put it online so that's all that does.
00:42:26.693 --> 00:42:28.353 And then here the thing we can't figure out.
00:42:30.053 --> 00:42:30.893 So if there's a root.
00:42:33.113 --> 00:42:41.442 And there's a path to use which is the root in our case and the
00:42:41.442 --> 00:42:42.223 roots.
00:42:44.733 --> 00:42:45.463 Asked it again.
00:42:45.953 --> 00:42:47.703 After years, which they're identical.
00:42:50.233 --> 00:42:55.703 So if that test passes, which it always does, I suppose then.
00:42:58.893 --> 00:43:00.333 After you 3 equals.
00:43:02.373 --> 00:43:08.023 Have to use three dot substring starting at 47.
00:43:08.083 --> 00:43:09.213 So what has passed this view?
00:43:09.223 --> 00:43:12.513 Three, turn into an empty string.
00:43:16.253 --> 00:43:16.873 What in the world?
00:43:17.923 --> 00:43:18.913 Yeah, it's so weird.
00:43:18.923 --> 00:43:21.303 I I have no idea what the intention is behind that.
00:43:22.663 --> 00:43:25.313 Me neither, but here you can see.
00:43:25.323 --> 00:43:30.689 Fortunately, base three is the full URL, so then it adds
00:43:30.689 --> 00:43:36.244 nothing to it, adds an empty string, and then append query
00:43:36.244 --> 00:43:42.458 string params would append query parameters if we had any, but we
00:43:42.458 --> 00:43:43.023 don't.
00:43:44.253 --> 00:43:51.133 Umm take a look in here and we step in.
00:43:53.473 --> 00:43:55.203 So is there no params body?
00:43:55.213 --> 00:43:56.223 Oh, there's not.
00:43:56.273 --> 00:43:56.543 OK.
00:43:57.903 --> 00:44:00.213 Do we want to add no cash?
00:44:00.343 --> 00:44:01.193 Ohh, we don't.
00:44:01.233 --> 00:44:01.573 OK.
00:44:01.583 --> 00:44:04.590 We'll just return what we got, which is all it does for most of
00:44:04.590 --> 00:44:05.013 the time.
00:44:07.813 --> 00:44:12.212 So, but this would work so like for instance if you wanna go to
00:44:12.212 --> 00:44:15.443 the the catalog right and you want to pass in.
00:44:16.963 --> 00:44:19.469 I'm actually doing that in 10 real quick so I can show it to
00:44:19.469 --> 00:44:19.633 you.
00:44:21.073 --> 00:44:21.393 Excuse me.
00:44:23.433 --> 00:44:29.715 So over here they want to see more link to filter the
00:44:29.715 --> 00:44:34.833 attributes all by showcase auction is true.
00:44:36.903 --> 00:44:43.310 So that course link it actually made this and what it did is it
00:44:43.310 --> 00:44:46.213 turned make a show it to you.
00:44:47.243 --> 00:44:52.438 OK, the option it turned this object with attributes all
00:44:52.438 --> 00:44:54.443 showcase auction true.
00:44:56.233 --> 00:44:58.113 It turns that into this.
00:45:03.653 --> 00:45:05.463 They just URL encoded it, right?
00:45:05.473 --> 00:45:06.223 That's all it did.
00:45:06.653 --> 00:45:10.951 So just replaced like the opening Curly brace with percent
00:45:10.951 --> 00:45:15.396 7B air play another character like the opening array bracket
00:45:15.396 --> 00:45:17.363 or whatever with decent 22.
00:45:17.413 --> 00:45:18.453 I mean like, that's all it does.
00:45:19.203 --> 00:45:23.040 It just, it just makes it URL friendly because otherwise if
00:45:22.893 --> 00:45:23.113 Nice.
00:45:23.040 --> 00:45:27.133 you don't do that you get that weird object object thing right?
00:45:27.203 --> 00:45:32.630 So you get like and attribute all equals like array, bracket,
00:45:32.630 --> 00:45:33.943 object, object.
00:45:33.953 --> 00:45:36.983 Using that before. Yeah.
00:45:35.003 --> 00:45:35.823 Yes. Yep.
00:45:37.073 --> 00:45:37.423 Yeah.
00:45:37.473 --> 00:45:42.119 So if you don't, if you didn't call append query params and
00:45:42.119 --> 00:45:46.998 actually like you know, let it do its job and do it right then
00:45:46.998 --> 00:45:50.483 it would it would you know it would work so.
00:45:50.493 --> 00:45:53.353 Can I see your code back in the showcase auctions again?
00:45:54.203 --> 00:45:54.343 Yeah.
00:45:59.713 --> 00:46:04.313 Umm back in VS code where you actually use the.
00:46:03.023 --> 00:46:05.673 Oh, yeah, right here.
00:46:05.953 --> 00:46:06.773 Yeah, right there.
00:46:12.323 --> 00:46:13.333 A/C passed.
00:46:18.563 --> 00:46:19.093 So what?
00:46:19.143 --> 00:46:20.363 What was the 2nd argument?
00:46:20.373 --> 00:46:21.133 Is that area?
00:46:23.013 --> 00:46:29.681 So the earth arguments the first argument is the subcontext, the
00:46:25.013 --> 00:46:25.753 Records like.
00:46:28.953 --> 00:46:29.173 Yep.
00:46:29.681 --> 00:46:32.553 second argument is the path.
00:46:34.123 --> 00:46:34.923 That. That's it.
00:46:34.153 --> 00:46:36.343 So Yep.
00:46:34.933 --> 00:46:38.173 OK, that's what it's called in the course dot TS file path.
00:46:38.383 --> 00:46:39.323 Alright, I'm.
00:46:38.663 --> 00:46:42.233 Yep, and and it's pretty much always some sort of root.
00:46:39.403 --> 00:46:39.893 I'm with you.
00:46:42.723 --> 00:46:45.211 It's like it's always starts with the config dot roots dot
00:46:45.211 --> 00:46:45.633 something.
00:46:45.643 --> 00:46:48.964 It's always some stuff config dot roots dot something dot root
00:46:48.964 --> 00:46:51.073 like every time I've ever seen it used.
00:46:49.223 --> 00:46:52.803 And then catalog is your area OK.
00:46:52.093 --> 00:46:52.463 Yeah.
00:46:52.513 --> 00:46:54.063 And then catalog is the area.
00:46:54.433 --> 00:46:58.293 Yep, which would correspond to this in theory. Right?
00:46:58.933 --> 00:46:59.173 Mm-hmm.
00:47:00.233 --> 00:47:05.235 And then primary, but this is used for but we don't use it
00:47:05.235 --> 00:47:10.491 because it's not built up for react is you instead of setting
00:47:10.491 --> 00:47:11.593 all of these.
00:47:12.543 --> 00:47:16.339 So let's say that like ten of these are PVC stage and the rest
00:47:16.339 --> 00:47:17.243 are PVC linear.
00:47:18.963 --> 00:47:23.143 So primary can be changed.
00:47:23.153 --> 00:47:25.183 If you look at this commented out code up here.
00:47:25.533 --> 00:47:32.010 I have a class right now it can be changed to alternate one
00:47:32.010 --> 00:47:38.810 alternate 2 or alternate 3 and this will use the alternate URL
00:47:38.810 --> 00:47:41.293 for the domain in Seth.
00:47:42.593 --> 00:47:44.943 OK, so that's not really used anymore.
00:47:46.523 --> 00:47:50.412 It's really not used anymore and in my opinion it's really
00:47:50.412 --> 00:47:51.203 unnecessary.
00:47:52.383 --> 00:47:57.861 Umm, because you can always just set ten of your app settings to
00:47:57.861 --> 00:48:01.233 whatever host you need it to be, right?
00:48:01.273 --> 00:48:04.252 Instead of passing alternate one or alternate to alternate 3,
00:48:04.252 --> 00:48:07.135 just change the host and the app settings and it's the same
00:48:07.135 --> 00:48:07.423 thing.
00:48:09.383 --> 00:48:09.813 OK.
00:48:09.853 --> 00:48:10.473 That makes sense.
00:48:10.103 --> 00:48:14.414 So yeah, so as you're learning a lot of this is confusing because
00:48:14.414 --> 00:48:18.528 it's written poorly, and also because we don't use it anymore.
00:48:18.528 --> 00:48:19.443 Unfortunately.
00:48:20.233 --> 00:48:24.483 So yeah, you're like, that's why it's hard for me.
00:48:20.653 --> 00:48:21.943 That makes a lot of sense.
00:48:24.493 --> 00:48:28.419 Yeah, it's because it's because no one, I mean, you saw Jesse in
00:48:28.419 --> 00:48:29.023 here even.
00:48:29.033 --> 00:48:32.053 He was like, I'm not really sure what that does like.
00:48:32.143 --> 00:48:32.263 Yeah.
00:48:32.343 --> 00:48:36.243 And he's been here longer than any of us, so yeah.
00:48:37.343 --> 00:48:40.923 Can you go back to your showcase auctions dot TSX one more time.
00:48:41.733 --> 00:48:43.023 Yeah, you're intended to.
00:48:43.033 --> 00:48:43.863 You I'll just send it to.
00:48:44.573 --> 00:48:44.813 Yeah.
00:48:47.503 --> 00:48:47.973 Umm.
00:48:47.623 --> 00:48:49.083 Yeah, it's helpful to actually see.
00:48:49.093 --> 00:48:49.653 Like what?
00:48:49.723 --> 00:48:52.443 What you're passing into it that that really helps.
00:48:53.583 --> 00:48:53.703 Yeah.
00:48:55.623 --> 00:48:56.093 Umm.
00:48:56.143 --> 00:49:00.774 And then the last one here, no cash that's that's the 5th
00:49:00.774 --> 00:49:01.493 argument.
00:49:05.103 --> 00:49:10.229 As far as I know, we never used anywhere, but in theory it's
00:49:10.229 --> 00:49:15.019 intended to be able to break caching of an endpoint like
00:49:15.019 --> 00:49:18.213 bypassing and something into the URL.
00:49:18.563 --> 00:49:24.136 We do use that concept, which you've seen it before, probably
00:49:24.136 --> 00:49:29.170 right here, door front, react JS configs passes in this
00:49:29.170 --> 00:49:34.654 underscore 1263 and the only reason that's there is to break
00:49:31.723 --> 00:49:31.923 Yeah.
00:49:34.654 --> 00:49:35.373 caching.
00:49:35.433 --> 00:49:39.309 So if you change this to 1264, it will ignore the Redis cache
00:49:39.309 --> 00:49:42.123 and actually go make the call again for you.
00:49:42.833 --> 00:49:43.513 Oh wow.
00:49:43.733 --> 00:49:46.573 OK, I had no idea what that was.
00:49:45.183 --> 00:49:45.323 Yeah.
00:49:47.633 --> 00:49:48.833 Yep, that's what it was.
00:49:48.843 --> 00:49:52.713 It's just a it's just a cache counter and if you look in here,
00:49:52.713 --> 00:49:56.093 there's also the call to get cash counter Now this one
00:49:56.093 --> 00:49:58.243 doesn't correspond to that number.
00:49:58.333 --> 00:50:00.924 I I don't know exactly why there's two different numbers,
00:50:00.924 --> 00:50:01.683 but they're both.
00:50:01.693 --> 00:50:05.611 Essentially, do the same thing, which is they slightly alter the
00:50:05.611 --> 00:50:08.023 URL so that you can get around caching.
00:50:09.183 --> 00:50:11.113 Then that's this is a perfect example.
00:50:12.853 --> 00:50:15.743 So Yep, so that's, that's all.
00:50:14.283 --> 00:50:14.543 OK.
00:50:15.753 --> 00:50:20.145 No caches for, except that I think no caches is old outdated
00:50:20.145 --> 00:50:24.105 way of doing it by the date instead of by an arbitrary
00:50:24.105 --> 00:50:25.113 number, right?
00:50:25.173 --> 00:50:29.017 If you look at here, yeah, to be here, it has no cache and then
00:50:25.183 --> 00:50:25.293 And.
00:50:29.017 --> 00:50:32.862 it's like, hey, leave the path alone, but add a parameter of no
00:50:32.862 --> 00:50:33.643 cache equals.
00:50:33.713 --> 00:50:34.863 And then here's the date.
00:50:34.953 --> 00:50:37.733 Or here's a oh, it actually is the number.
00:50:37.903 --> 00:50:41.093 It's just a it's just a random number.
00:50:41.143 --> 00:50:42.973 I see it's a number.
00:50:43.043 --> 00:50:46.967 See, it has new date dot get time which is the time since
00:50:46.967 --> 00:50:48.523 epoch and milliseconds.
00:50:48.993 --> 00:50:51.323 So it's always going to be something new.
00:50:49.113 --> 00:50:49.353 Yep.
00:50:53.553 --> 00:50:53.963 Right.
00:50:54.153 --> 00:50:56.789 That number will never happen twice, because this code can
00:50:56.789 --> 00:50:58.353 never run in the same millisecond.
00:51:00.813 --> 00:51:03.163 So it bust the cache by passing a number.
00:51:03.173 --> 00:51:05.853 The back ends never gotten before, and then the back end.
00:51:05.863 --> 00:51:09.846 Like Ohh, we haven't cashed that number and read it, so we'll
00:51:09.846 --> 00:51:11.773 just return the real response.
00:51:12.913 --> 00:51:15.093 So there you go.
00:51:15.133 --> 00:51:16.193 That's what no caches for.
00:51:16.283 --> 00:51:17.913 That's that's all the arguments.
00:51:17.923 --> 00:51:18.833 You're now an expert.
00:51:18.843 --> 00:51:21.023 Congratulations, that's.
00:51:20.423 --> 00:51:23.373 I think that's all my brain can absorb from this session.
00:51:23.103 --> 00:51:23.233 Yeah.
00:51:23.423 --> 00:51:26.898 That's caching is another thing that I think would be a good
00:51:26.898 --> 00:51:30.487 future training topic, because that that kind of confuses me a
00:51:30.487 --> 00:51:30.943 lot too.
00:51:31.903 --> 00:51:33.253 Yeah, I agree.
00:51:33.543 --> 00:51:34.333 I agree it would.
00:51:35.323 --> 00:51:38.597 I would not be the right guy for it, but I agree that it would
00:51:38.597 --> 00:51:38.753 be.
00:51:39.963 --> 00:51:40.733 It'd be helpful.
00:51:40.823 --> 00:51:44.833 It'd be helpful to know how the Redis cache is actually built.
00:51:45.723 --> 00:51:46.803 That's what I'd like to see.
00:51:47.103 --> 00:51:47.993 Like, what's the?
00:51:48.043 --> 00:51:50.834 What are what determines the strings that are actually in
00:51:50.834 --> 00:51:51.123 there?
00:51:53.383 --> 00:51:58.613 That's what I would like to see, but yeah, so there you go.
00:51:59.163 --> 00:52:00.533 And I did have to actually.
00:52:00.623 --> 00:52:05.732 So you'll you'll know the for your thick some places out of
00:52:05.732 --> 00:52:11.351 box use site when they shouldn't for the area and I had to go fix
00:52:11.351 --> 00:52:12.203 it for PC.
00:52:13.493 --> 00:52:15.933 Umm, so here's the perfect example right here.
00:52:17.033 --> 00:52:23.656 This is an anchor that goes to product details but passing
00:52:23.656 --> 00:52:30.280 sight as the area and so you can probably imagine what the
00:52:30.280 --> 00:52:33.423 problem would be right here.
00:52:33.433 --> 00:52:38.543 You have site and it has its own host right?
00:52:33.563 --> 00:52:35.563 Do we? Yeah.
00:52:38.593 --> 00:52:43.569 With like whatever and it has its own root with whatever
00:52:43.569 --> 00:52:46.363 right, whatever, whatever it is.
00:52:47.843 --> 00:52:49.123 But then we have product detail.
00:52:54.143 --> 00:52:58.727 And product detail actually has a host as you can see like
00:52:58.727 --> 00:52:59.193 right?
00:52:59.243 --> 00:53:07.118 Like in my example, if you see it actually has a host right of
00:53:07.118 --> 00:53:12.243 listen sucking but tbclinear.hstest.net.
00:53:13.553 --> 00:53:15.473 So what happened is this link?
00:53:16.663 --> 00:53:22.493 Yes, it's hosed from site, which doesn't have the app setting.
00:53:23.443 --> 00:53:27.603 It's host is still just pvcstage.clarityclient.com,
00:53:27.603 --> 00:53:28.083 right?
00:53:30.393 --> 00:53:32.550 But you're trying to get a product detail and the product
00:53:30.473 --> 00:53:30.683 Yeah.
00:53:32.550 --> 00:53:33.963 detail actually has a different host.
00:53:34.493 --> 00:53:35.713 So this link breaks.
00:53:38.093 --> 00:53:40.203 Because the path and the area don't match.
00:53:40.293 --> 00:53:43.645 So this so the app settings for product detail for the host
00:53:43.645 --> 00:53:46.383 isn't respected because this is pointing a site.
00:53:46.433 --> 00:53:49.533 So this should actually be spark detail.
00:53:50.373 --> 00:53:52.963 Do you have any idea like when that was fixed?
00:53:54.493 --> 00:53:55.203 Just curious.
00:53:55.093 --> 00:53:55.603 I don't.
00:53:56.113 --> 00:53:59.224 I don't think I fixed it in core, I just fixed it in PVC
00:53:59.224 --> 00:54:01.353 because I needed it to to work in PVC.
00:54:02.033 --> 00:54:02.623 Got you.
00:54:03.483 --> 00:54:06.153 So but it's it's here.
00:54:03.813 --> 00:54:07.900 I swear I've I've seen that and I can't remember what project I
00:54:07.900 --> 00:54:08.603 had to use.
00:54:08.613 --> 00:54:12.843 The image was fall back on and I I ran into that.
00:54:11.153 --> 00:54:11.443 Umm.
00:54:12.853 --> 00:54:16.963 So is that still a core bug this?
00:54:16.323 --> 00:54:17.373 It probably is.
00:54:17.443 --> 00:54:19.497 I mean, well, I mean, you could go look at the image with fall
00:54:19.497 --> 00:54:19.693 backs.
00:54:19.993 --> 00:54:20.253 Yeah.
00:54:21.263 --> 00:54:26.003 This is this project is almost brand new off the floor and.
00:54:29.073 --> 00:54:29.723 Crying.
00:54:33.903 --> 00:54:35.583 Here's the config and images.
00:54:40.673 --> 00:54:42.693 But probably broken in here.
00:54:44.733 --> 00:54:45.963 It works right here.
00:54:45.973 --> 00:54:50.143 It actually passes images and as the area. Umm.
00:54:52.733 --> 00:54:54.363 It's probably broken in a couple areas.
00:54:54.613 --> 00:54:57.393 Still, it may not be broken in as many as it was, but it
00:54:57.393 --> 00:54:58.613 probably looked in a few.
00:54:59.703 --> 00:55:06.460 So anyway ohh they all the ones that have brought teacher route
00:55:06.460 --> 00:55:11.423 should be part detail but anyway there you go.
00:55:12.893 --> 00:55:13.173 Nice.
00:55:15.053 --> 00:55:17.503 So I will leave my comments here.
00:55:18.823 --> 00:55:26.460 Umm, I don't think I can go over this in 4 minutes now because
00:55:24.773 --> 00:55:29.972 Doubtful, but will you share the link in in here or in like the
00:55:26.460 --> 00:55:27.793 yeah, cool.
00:55:29.972 --> 00:55:32.003 in some other channel or?
00:55:33.593 --> 00:55:34.233 For the recording.
00:55:34.713 --> 00:55:35.013 Yeah.
00:55:36.463 --> 00:55:40.181 Uh, I can put it in the I'll put it in Afghan anything channel
00:55:40.181 --> 00:55:41.833 since we're all in there so.
00:55:41.283 --> 00:55:41.833 Sweet.
00:55:41.903 --> 00:55:42.733 Alright, sounds good.
00:55:44.933 --> 00:55:47.223 I meant I am gonna let go.
00:55:47.233 --> 00:55:47.853 Have a great weekend.
00:55:48.473 --> 00:55:49.483 Yeah, you too, man.
00:55:49.493 --> 00:55:50.193 Happy Friday.
00:55:50.203 --> 00:55:50.553 Take care.
00:55:51.683 --> 00:55:52.243 Thank you, Sir.
00:55:52.283 --> 00:55:52.633 You as well.
00:55:53.163 --> 00:55:53.583 Alright, bye.
00:55:54.833 --> 00:55:55.013 Right.