00:00:08.623 --> 00:00:09.613 Yeah, I had no idea.
00:00:12.323 --> 00:00:12.713 Yeah.
00:00:13.323 --> 00:00:14.103 Super useful.
00:00:13.503 --> 00:00:16.673 Honestly, like some of the most crazy information I've gotten is
00:00:16.673 --> 00:00:19.306 just like from groups on LinkedIn, and I think that's
00:00:19.306 --> 00:00:22.085 where I learned it from. Was like a group on LinkedIn or
00:00:22.085 --> 00:00:22.573 something.
00:00:23.623 --> 00:00:25.013 Actually I think mine was a tick tock.
00:00:26.303 --> 00:00:29.473 Hey man, Tik toks not as bad as they tell you. Like you can get
00:00:26.333 --> 00:00:27.103 That's where I learned it.
00:00:29.283 --> 00:00:29.583 Yep.
00:00:29.473 --> 00:00:32.445 some good stuff if you if you get that algorithm right, you
00:00:32.445 --> 00:00:32.693 know.
00:00:33.093 --> 00:00:35.423 Yeah, mine was like the VS code, Tik T.O.K or something, yeah.
00:00:40.313 --> 00:00:42.523 Very cool. Alright, go ahead.
00:00:40.593 --> 00:00:44.208 So how how would we actually submit a change like? Is there
00:00:44.208 --> 00:00:47.763 anything we could we could do real quick to see the whole?
00:00:49.433 --> 00:00:50.363 Or did I miss it?
00:00:50.783 --> 00:00:52.683 Well, they did have the source code.
00:00:50.993 --> 00:00:54.212 I think it's because it has the git right there. You use the git
00:00:54.212 --> 00:00:57.283 that's inside VS code to submit your thing and it will do it.
00:00:57.933 --> 00:00:58.323 There.
00:00:58.573 --> 00:01:02.072 Yeah, it's the same. It's the same git. It's the same like Git
00:00:59.003 --> 00:00:59.513 Yeah.
00:00:59.423 --> 00:00:59.953 Ohh.
00:01:02.072 --> 00:01:04.683 extension that regular Visual Studio code has.
00:01:05.253 --> 00:01:09.036 So you're just add it and then I guess you don't have to push
00:01:05.333 --> 00:01:05.613 It.
00:01:09.036 --> 00:01:11.293 like once you commit that counts as.
00:01:10.143 --> 00:01:13.771 Well, you still commit and push, right? Yeah. You commit and
00:01:11.083 --> 00:01:12.253 You're already in a repo, right?
00:01:13.771 --> 00:01:14.663 push, but yeah.
00:01:14.663 --> 00:01:15.013 OK.
00:01:16.803 --> 00:01:17.343 Interesting.
00:01:17.163 --> 00:01:19.093 Yeah, this is just normal VS code.
00:01:17.163 --> 00:01:20.188 Because I'm I. It's that it looks like it's it looks like
00:01:20.188 --> 00:01:22.953 it's what probably checking out to like a temporary.
00:01:24.793 --> 00:01:28.878 Temporary folder somewhere and treats it as just reading from
00:01:28.878 --> 00:01:29.273 there.
00:01:32.123 --> 00:01:34.233 Uh. Let's see. Can I? Oops, can't do that.
00:01:36.743 --> 00:01:37.483 What have I done?
00:01:38.953 --> 00:01:41.003 No, I worked so hard on that.
00:01:43.003 --> 00:01:44.213 I don't even know where I am anymore.
00:01:43.453 --> 00:01:44.353 Or spinning.
00:01:44.943 --> 00:01:46.643 Let's go back to here.
00:01:45.903 --> 00:01:49.512 Obviously, obviously the normal git rules still apply, you can't
00:01:49.512 --> 00:01:52.900 just go in and modify the QA branch and push it, but you can
00:01:52.900 --> 00:01:56.509 modify. You could probably check out a different branch in here,
00:01:56.509 --> 00:02:00.063 push it, and then make the PR in Azure like you normally would.
00:02:00.763 --> 00:02:01.493 If it's a quick one.
00:02:05.773 --> 00:02:09.693 I guess I I guess it well, I guess you would just use the
00:02:09.693 --> 00:02:13.883 normal get controls right? Like you could check out in there?
00:02:14.523 --> 00:02:18.558 Well, the checkout, the checkout happens by clicking by hitting
00:02:18.558 --> 00:02:21.333 period on the the code. Whatever. Whatever.
00:02:22.723 --> 00:02:25.866 Uh, and correct me if I'm wrong on this. Anybody who knows this
00:02:25.866 --> 00:02:29.058 well enough, but whatever branch you're on, when you when you do
00:02:29.058 --> 00:02:30.973 that is the branch. It will check out.
00:02:31.363 --> 00:02:32.143 Right, Yep.
00:02:32.423 --> 00:02:35.093 Yeah, it's the same way. If you were in like the.
00:02:32.743 --> 00:02:35.243 That's correct. So you see where I just made that commit.
00:02:33.813 --> 00:02:34.153 OK.
00:02:34.773 --> 00:02:37.303 No. You can switch to branch looks like.
00:02:36.863 --> 00:02:40.077 Yep, Yep. So see what I just made that commit to change this
00:02:40.077 --> 00:02:43.397 to example to default settings. That was just now on this call
00:02:43.397 --> 00:02:46.505 using that save and then push and it opens whatever branch
00:02:46.505 --> 00:02:49.983 you're on right here that you're browsing is when you hit period.
00:02:51.063 --> 00:02:52.663 Ah, OK.
00:02:52.253 --> 00:02:54.923 You can also switch branches though if you do.
00:02:52.443 --> 00:02:53.033 Yeah, they had.
00:02:54.303 --> 00:02:55.003 Yeah, in here.
00:02:56.653 --> 00:02:56.873 Yep.
00:02:56.743 --> 00:02:59.972 They had the same, uh feature from like the command line,
00:02:56.963 --> 00:02:57.553 The.
00:02:58.163 --> 00:02:58.523 OK.
00:02:59.972 --> 00:03:03.369 right? Like if you're in the folder on the command line, you
00:03:03.369 --> 00:03:06.654 just hit code period and it opens up Visual Studio in that
00:03:06.654 --> 00:03:09.383 git repo. Everything right, like in that folder.
00:03:10.413 --> 00:03:12.133 You can do the same thing from the command line.
00:03:11.463 --> 00:03:11.723 Yep.
00:03:12.703 --> 00:03:12.953 Yep.
00:03:15.703 --> 00:03:19.077 The PR has clickable link to that branch as well, so you can
00:03:19.077 --> 00:03:22.452 click on that link and just hit period, it'll open it up for
00:03:22.452 --> 00:03:22.673 you.
00:03:26.993 --> 00:03:29.400 Yep. And Jeremy, the way he was switched branches, you do a
00:03:29.400 --> 00:03:31.927 control P and then greater than and then like Switch branch to
00:03:31.927 --> 00:03:34.374 or something like that was the commands that you can give it
00:03:34.374 --> 00:03:36.981 will give you a list of all the different branches. You can just
00:03:34.443 --> 00:03:34.793 OK.
00:03:36.981 --> 00:03:37.583 search through.
00:03:38.003 --> 00:03:39.283 Could you get the task, Ben? Yeah.
00:03:39.953 --> 00:03:40.983 For the command pilot or whatever.
00:03:42.373 --> 00:03:42.603 Yep.
00:03:42.533 --> 00:03:44.163 Unfortunately, I can shift does not work.
00:03:42.903 --> 00:03:43.213 On that.
00:03:46.143 --> 00:03:46.693 OK. Yeah.
00:03:46.693 --> 00:03:48.593 There it is. There's the command prompt, yeah.
00:03:50.603 --> 00:03:51.683 Tristan has their hands up.
00:03:50.993 --> 00:03:51.453 There you go.
00:03:53.813 --> 00:03:56.432 Yeah, other question, does this mean James is gonna be actually
00:03:56.432 --> 00:03:57.823 leaving comments in our code now?
00:03:58.813 --> 00:04:00.763 The style cop coming for you.
00:04:00.393 --> 00:04:03.023 Right. Like he's gonna just leave it in the actual code.
00:04:01.303 --> 00:04:02.013 Yeah.
00:04:03.193 --> 00:04:03.823 Yeah. Yep.
00:04:07.003 --> 00:04:09.753 No. If I'm actually editing the file, I'm fixing it directly.
00:04:10.153 --> 00:04:10.673 Yep.
00:04:11.293 --> 00:04:13.792 And that's because I largely assumed that you're either not
00:04:13.792 --> 00:04:16.167 gonna understand what I'm saying, or it's like the third
00:04:16.167 --> 00:04:18.083 try and you're still not getting what I said.
00:04:21.283 --> 00:04:23.841 So what you're saying is we're going to get less comments
00:04:23.841 --> 00:04:26.003 because you're just going to do the work for us?
00:04:27.263 --> 00:04:27.973 Great.
00:04:29.383 --> 00:04:31.273 Some one's getting whacked.
00:04:34.463 --> 00:04:36.453 We shared something happened to get PR.
00:04:34.893 --> 00:04:35.143 Yeah.
00:04:44.093 --> 00:04:45.383 There you have it. Very cool.
00:04:48.073 --> 00:04:49.373 Yay.
00:04:48.283 --> 00:04:50.553 Thanks. Thanks for that. Appreciate it.
00:04:50.153 --> 00:04:50.673 Yeah, you bet.
00:04:52.173 --> 00:04:55.621 All right, now the connectives can split out, and I think front
00:04:55.621 --> 00:04:58.638 end is going to split out as well and then back end can
00:04:58.638 --> 00:04:59.823 remain where they are.
00:04:59.453 --> 00:05:03.063 We what do we have for back end today? Like a monologue for a
00:05:02.433 --> 00:05:05.823 We got that index and index in search from Sir Gray.
00:05:03.063 --> 00:05:03.413 while?
00:05:05.973 --> 00:05:06.963 No, even better.
00:05:07.803 --> 00:05:08.463 Yeah.
00:05:09.173 --> 00:05:14.023 Can you tell me which person has the example you wanted me to do?
00:05:14.343 --> 00:05:18.726 Yeah, I have it well. So it'll be on, it's on develop code, but
00:05:18.726 --> 00:05:20.233 I'd like to index the.
00:05:22.443 --> 00:05:25.713 What is it? The starting or we said, yeah, I guess starting
00:05:25.713 --> 00:05:28.766 price is probably fine or Brendan if you can think of a
00:05:28.766 --> 00:05:31.273 better one that's on the lot, the lot object.
00:05:31.963 --> 00:05:32.523 Umm.
00:05:34.123 --> 00:05:37.493 No, that sounds fine. We would need to index UM.
00:05:38.763 --> 00:05:41.752 Uh, it's already on there. The product categories. UM, I'm
00:05:41.752 --> 00:05:44.893 trying something more complex because relatively simple stuff
00:05:44.893 --> 00:05:47.883 like getting it to index and querying against it isn't too
00:05:47.883 --> 00:05:51.125 bad, it's the more complex stuff where it's like you wanna pull
00:05:51.125 --> 00:05:54.114 back all of the values that matched your query. So like if
00:05:54.114 --> 00:05:56.293 it's like brand names and stuff like that.
00:05:54.473 --> 00:05:57.947 I think I think he wanted to do the simple one first to as a
00:05:57.947 --> 00:06:01.591 primer and then a slightly more advanced advanced example after
00:05:59.113 --> 00:06:00.113 OK. Gotcha. Yeah.
00:05:59.193 --> 00:05:59.653 Mm-hmm.
00:06:01.591 --> 00:06:03.243 that which was the other one.
00:06:02.043 --> 00:06:04.728 Yeah. Then yeah, the starting price is perfect because that'll
00:06:02.193 --> 00:06:02.673 Yes.
00:06:04.728 --> 00:06:07.414 be like, UM, that'll be pretty straightforward. Yeah. And then
00:06:07.414 --> 00:06:08.863 we can do something more complex.
00:06:10.603 --> 00:06:12.806 Awesome. Thank you. And I'm gonna hop over to the connect
00:06:12.806 --> 00:06:15.237 connect phone. Feel free to call me if you have questions on it
00:06:15.237 --> 00:06:15.503 though.
00:06:16.273 --> 00:06:16.493 Like.
00:06:16.683 --> 00:06:19.993 OK. Can you open that up and I will.
00:06:21.373 --> 00:06:21.943 Guide.
00:06:23.483 --> 00:06:24.153 And tell.
00:06:25.063 --> 00:06:30.573 You. Meaning who? Yes, I would love if Nick Bulisky.
00:06:25.163 --> 00:06:25.873 And stuff.
00:06:32.243 --> 00:06:36.352 I'm now I'm putting you on the spot, but can you share your
00:06:34.083 --> 00:06:34.853 Yeah, what's up?
00:06:36.352 --> 00:06:37.653 screen and open up?
00:06:39.753 --> 00:06:43.613 A. Open up your local with the latest code from develop.
00:06:44.673 --> 00:06:47.200 And that's OK. If it's gonna take you a second to to pull up,
00:06:47.200 --> 00:06:48.423 like, to get pull and develop.
00:06:49.233 --> 00:06:53.482 If you and Nick the the 2022.4 local that that you set up, you
00:06:53.482 --> 00:06:54.763 can just check out.
00:06:55.983 --> 00:06:58.753 Develop on that and everything is.
00:07:00.083 --> 00:07:03.267 Nearly identical, so you'll just have to build the front and back
00:07:03.267 --> 00:07:03.943 and that's it.
00:07:05.503 --> 00:07:05.893 OK.
00:07:06.933 --> 00:07:10.047 Awesome. Thanks for thanks for being the Guinea pig, Nick and
00:07:09.963 --> 00:07:10.833 No problem.
00:07:10.047 --> 00:07:11.203 Val and being volatile.
00:07:37.283 --> 00:07:39.743 And it's let me know when you got it open.
00:07:40.963 --> 00:07:42.513 Yep, just one second.
00:07:42.173 --> 00:07:43.443 It's like A and E.
00:07:47.693 --> 00:07:51.023 We working on another screen I'm guessing.
00:07:52.393 --> 00:07:53.273 I'm sorry. What was that?
00:07:54.773 --> 00:07:57.503 Ohh, were you like doing something on another screen?
00:07:58.143 --> 00:08:00.991 Yeah, I have the terminal up on my other window. I'm just
00:08:00.991 --> 00:08:02.563 switching directories right now.
00:08:01.743 --> 00:08:05.633 Gotcha. Gotcha. Yeah. Yeah. OK. Just making sure.
00:08:14.963 --> 00:08:17.433 And then what branch was I supposed to be on?
00:08:17.893 --> 00:08:18.863 Develop.
00:08:18.413 --> 00:08:18.873 Develop.
00:08:20.623 --> 00:08:24.063 So you can just get check out, develop and then get pull.
00:08:37.513 --> 00:08:40.193 And I also don't have the right window up.
00:08:50.883 --> 00:08:54.953 Saying this is the one I should have up and I just ran the.
00:08:56.573 --> 00:08:58.493 It pull and I had.
00:08:59.443 --> 00:09:02.803 Something weird pop up, but I couldn't drag the window over.
00:09:04.233 --> 00:09:05.423 OK. Yeah, up to date.
00:09:06.273 --> 00:09:06.963 OK, cool.
00:09:08.423 --> 00:09:09.883 So yeah, now you can.
00:09:11.783 --> 00:09:14.991 I mean, we could just start working on it from here. Since
00:09:14.973 --> 00:09:18.083 Yeah. So go ahead and close the three files you got open.
00:09:14.991 --> 00:09:16.133 you're on on develop.
00:09:18.923 --> 00:09:22.272 Umm, those aren't gonna be relevant to this. OK, so you
00:09:22.272 --> 00:09:25.860 have a property that you wanna get indexed into elastic and
00:09:25.860 --> 00:09:28.073 this property is the starting price.
00:09:30.013 --> 00:09:31.433 On the lot, correct.
00:09:32.153 --> 00:09:32.413 Yes.
00:09:33.363 --> 00:09:33.943 OK.
00:09:35.293 --> 00:09:37.953 If you focus on content.
00:09:39.093 --> 00:09:42.423 And that you're already full screen. OK, expand the data
00:09:42.423 --> 00:09:43.183 access layer.
00:09:43.993 --> 00:09:46.503 And then expand the data model shared.
00:09:48.143 --> 00:09:52.433 And let's go to the models, auctions.
00:09:54.293 --> 00:09:55.373 And the lot.
00:09:58.703 --> 00:10:01.603 OK. And we'll find that that starting that starting price
00:10:01.603 --> 00:10:02.453 property in here.
00:10:07.893 --> 00:10:10.862 So there's the interface for it, and if we Scroll down, we'll
00:10:10.862 --> 00:10:12.203 find the the concrete of it.
00:10:13.513 --> 00:10:16.203 And we'll just double check everything cool there. Yep.
00:10:16.203 --> 00:10:19.084 Starting price there. Has it? OK, so starting price has the
00:10:19.084 --> 00:10:21.822 property there. That's a decimal. It's nullable. We know
00:10:21.822 --> 00:10:24.944 everything we need to know about this property. Go ahead and pin
00:10:24.944 --> 00:10:26.673 this file to state to keep it open.
00:10:29.443 --> 00:10:33.116 OK, so the next thing we wanna touch is on the right side on
00:10:33.116 --> 00:10:35.163 the solution Explorer, scroll up.
00:10:35.903 --> 00:10:38.263 And collapse the data access layer.
00:10:39.073 --> 00:10:39.543 Uh.
00:10:40.923 --> 00:10:44.040 And we're going to expand providers and then go to the
00:10:44.040 --> 00:10:44.833 searching one.
00:10:45.993 --> 00:10:46.463 Uh.
00:10:48.223 --> 00:10:52.313 Yep. And in there we've got the elastic search.
00:10:54.413 --> 00:10:56.353 And then we have lots.
00:10:58.113 --> 00:10:59.563 And then we have the dump reader.
00:11:01.763 --> 00:11:04.278 Why is it called the dump reader? Because that's how the
00:11:04.278 --> 00:11:06.837 original example from elastic search calls it and I never
00:11:06.837 --> 00:11:08.073 bothered to change the name.
00:11:08.463 --> 00:11:12.962 Also pro tip something something James. I haven't talked to you
00:11:08.663 --> 00:11:09.583 It's a funny name too.
00:11:12.962 --> 00:11:17.461 about the the core auction stuff yet, but for core auctions, we
00:11:17.461 --> 00:11:20.273 don't have a separate catalog for lots.
00:11:21.763 --> 00:11:25.029 It's lot data is indexed onto the products as basically
00:11:25.029 --> 00:11:28.877 extended properties and it's all flattened to one thing basically
00:11:28.877 --> 00:11:32.201 so that all of the existing catalog search functionality
00:11:32.201 --> 00:11:35.467 works without having to duplicate it and the front end.
00:11:35.467 --> 00:11:39.024 And we can also have combined catalogs where users can add a
00:11:39.024 --> 00:11:42.815 normal product to their cart or bid on a lot directly inside the
00:11:42.815 --> 00:11:43.573 same results.
00:11:45.003 --> 00:11:47.113 So this actually indexed onto the product basically.
00:11:45.023 --> 00:11:47.783 OK, so for core, do we need to edit the lot 1 or do we need to
00:11:47.783 --> 00:11:48.703 edit the product one?
00:11:48.733 --> 00:11:49.463 The product one.
00:11:50.323 --> 00:11:52.811 OK. So then collapse the lots one, we'll ignore that and go to
00:11:52.811 --> 00:11:53.443 the product one.
00:12:01.863 --> 00:12:03.613 OK, go to the product dump reader.
00:12:05.423 --> 00:12:08.073 And we can close the other dump reader so we don't get confused.
00:12:08.733 --> 00:12:10.313 And go ahead and pin. This file is going to keep it open.
00:12:12.383 --> 00:12:16.506 OK, as we Scroll down this file a little bit, you'll start to
00:12:16.506 --> 00:12:20.763 see the the massive ask query of stuff to read. I'm assuming we
00:12:20.763 --> 00:12:24.820 wanna get to the lot the lot reference to the product, so as
00:12:24.820 --> 00:12:28.678 we Scroll down we'll see associated and there should be a
00:12:28.678 --> 00:12:30.673 lot section on here somewhere.
00:12:32.233 --> 00:12:37.007 Here's the lots. OK, so we have buy now available status ID,
00:12:37.007 --> 00:12:41.782 name, custom key ID lot closes at an auction, closes at from
00:12:41.782 --> 00:12:46.870 the the the third party data in the lots. We'll add the property
00:12:46.870 --> 00:12:51.879 there to the last line that says why dot starts or whatever the
00:12:51.879 --> 00:12:53.053 starting price.
00:12:54.563 --> 00:12:58.303 So between lines of 161 and 162 you'll do Y dot.
00:13:00.593 --> 00:13:01.903 Why dot starting Bryce?
00:13:12.973 --> 00:13:15.633 Should be a capital S because it's a property on a table.
00:13:15.233 --> 00:13:15.453 Yeah.
00:13:18.923 --> 00:13:21.146 OK. And then we want to add a column or a comment to the end
00:13:21.146 --> 00:13:21.583 of the line.
00:13:22.543 --> 00:13:25.867 OK, at minimum we are now at least trying to start reading
00:13:25.867 --> 00:13:29.529 that data. So this is the first step is in the first part of the
00:13:29.529 --> 00:13:32.909 query here. This is SQL only capability of just finding the
00:13:32.909 --> 00:13:36.346 data, pulling it in on a dynamic object or dynamically typed
00:13:36.346 --> 00:13:39.726 object which SQL will translate correctly for us to do that
00:13:39.726 --> 00:13:42.994 part. So as we Scroll down, we're gonna see a second spot
00:13:42.994 --> 00:13:43.783 that has lots.
00:13:44.553 --> 00:13:45.373 Or the lot.
00:13:46.303 --> 00:13:46.823 On it.
00:13:49.363 --> 00:13:52.744 And we can see that in this section we now have a new
00:13:52.744 --> 00:13:56.500 indexable lot data. This is we're translating the data from
00:13:56.500 --> 00:14:00.382 what the sequel query is going to give us into an object that
00:14:00.382 --> 00:14:04.076 we're going to keep Inc memory. So we're gonna add to this
00:14:04.076 --> 00:14:08.145 closes at after that. So between lines 272 and 273, you're gonna
00:14:08.145 --> 00:14:08.333 do.
00:14:10.173 --> 00:14:13.853 A starting price equal to X dot starting price.
00:14:14.783 --> 00:14:16.673 Or sorry or X dot log dot starting price.
00:14:19.253 --> 00:14:19.463 Yep.
00:14:22.793 --> 00:14:25.841 OK, now because we have not added it to the model yet, we
00:14:25.841 --> 00:14:29.310 need to go add starting price to the model. If you control period
00:14:29.310 --> 00:14:29.993 on that line.
00:14:34.663 --> 00:14:37.368 It should say generate property starting price which is going to
00:14:37.368 --> 00:14:40.032 generate as a nullable decimal right after closes that which is
00:14:40.032 --> 00:14:40.573 what we want.
00:14:43.043 --> 00:14:46.104 OK, now control. Click on that starting price so that will go
00:14:46.104 --> 00:14:46.993 to its definition.
00:14:48.013 --> 00:14:51.254 Uh, if that doesn't work, we can do like control or F-12 or or
00:14:51.254 --> 00:14:54.546 control F-12. There's different ways of getting to that kind of
00:14:54.546 --> 00:14:57.479 thing. But yeah, we could see that it's here and it's by
00:14:57.479 --> 00:15:00.822 itself. It's after closes at. It needs a space or sorry, a blank
00:15:00.822 --> 00:15:04.115 line between the two properties. So we'll add that. So click on
00:15:04.115 --> 00:15:07.253 the end of the closes that line, do a new line. There we go.
00:15:07.603 --> 00:15:11.416 Umm the I don't know if you have the trailing visualization white
00:15:11.416 --> 00:15:14.940 space extension or not in here, in which case you if there's
00:15:14.940 --> 00:15:18.638 white space on that blank line it would clear it off for us. If
00:15:18.638 --> 00:15:22.046 not, we need to make sure that it gets cleared and then we
00:15:22.046 --> 00:15:22.913 don't have the.
00:15:24.493 --> 00:15:25.353 The.
00:15:26.803 --> 00:15:29.925 The the the summary XML comment on it. So let's just copy the
00:15:29.925 --> 00:15:31.133 other one onto this one.
00:15:35.833 --> 00:15:38.705 And again, we gotta make sure there's a line in between. Yep,
00:15:38.705 --> 00:15:41.530 there we go. And then gets are sets. We place the date slash
00:15:41.530 --> 00:15:43.383 time part with just the starting price.
00:15:45.333 --> 00:15:47.153 And you'll do the same thing and the value part.
00:15:51.173 --> 00:15:54.182 And that can be capitalized or not capitalized. Either way, it
00:15:54.182 --> 00:15:57.095 actually care about that part because it's gonna autumn here
00:15:57.095 --> 00:16:00.104 would have automatically made it with a lower case, but that's
00:16:00.104 --> 00:16:02.396 fine, totally perfectly acceptable to we have a
00:16:02.396 --> 00:16:05.357 capitalized. OK, so now we have our summary XML. So that will
00:16:05.357 --> 00:16:08.127 get out into the XML file whenever that comes back, we'll
00:16:08.127 --> 00:16:11.136 save this file, we'll go ahead and pin it and keep it open for
00:16:11.136 --> 00:16:14.050 the sake of argument in case we're to do something else with
00:16:14.050 --> 00:16:16.867 it, I think we're gonna come back and do it again with our
00:16:16.867 --> 00:16:19.781 second example. But now we go back to the dump reader and we
00:16:19.781 --> 00:16:22.694 can verify that that thing is there. OK. And as we save this
00:16:22.694 --> 00:16:22.933 file.
00:16:23.323 --> 00:16:26.167 Now we know that we have that data on the lot itself, as it's
00:16:26.167 --> 00:16:28.093 as we do that part. So let's Scroll down.
00:16:29.213 --> 00:16:31.985 And we'll find that there should be something else in here that
00:16:31.985 --> 00:16:34.410 handles the lot for translating it onto the product and
00:16:34.410 --> 00:16:35.103 indexable model.
00:16:36.813 --> 00:16:39.551 I think it actually is just straight reading it so lot data
00:16:39.551 --> 00:16:42.562 equals the version dot lot there on line 350. I think that's just
00:16:42.562 --> 00:16:45.209 straight reading it, so that's that should be fine. Let's
00:16:45.209 --> 00:16:47.718 Scroll down and see there's anything else that's doing
00:16:47.718 --> 00:16:49.863 anything with lots further down looks like no.
00:16:51.143 --> 00:16:52.493 Uh, it would have been inside that function.
00:16:55.123 --> 00:16:58.042 Yeah, it would have been in here. And I'm not seeing
00:16:58.042 --> 00:16:59.033 anything here for.
00:17:00.553 --> 00:17:04.396 That stuff. But what we might need to check is we don't need
00:17:04.396 --> 00:17:07.987 to do any custom suggests cause this isn't affecting the
00:17:07.987 --> 00:17:08.743 suggestions.
00:17:09.573 --> 00:17:12.011 It's not going to do anything with variance or categories.
00:17:12.011 --> 00:17:13.623 It's not gonna do anything with roles.
00:17:14.523 --> 00:17:17.538 It's not a filterable attribute. It's not a queryable attribute,
00:17:17.538 --> 00:17:18.883 so it's none of those things.
00:17:19.593 --> 00:17:20.223 Umm.
00:17:30.253 --> 00:17:32.788 But that's OK. There's nothing else that we need to mess with.
00:17:32.788 --> 00:17:33.553 I think we're good.
00:17:34.823 --> 00:17:38.719 So this side should be good. Now the next thing we wanna touch is
00:17:38.719 --> 00:17:42.260 gonna be the. Let's open the elastic searching provider dot
00:17:42.260 --> 00:17:45.153 CS file that's right underneath the dump writer.
00:17:47.763 --> 00:17:48.773 Let's look at that.
00:17:49.543 --> 00:17:51.339 OK, let's just scroll through this real quick and see if
00:17:51.339 --> 00:17:53.073 there's anything had anything to do with lots in here.
00:17:55.263 --> 00:17:57.533 Nope. OK, let's open the next one that config.
00:18:03.633 --> 00:18:04.433 No, nothing.
00:18:04.553 --> 00:18:07.101 Try just the word lot instead of lots plural cause it could be
00:18:07.101 --> 00:18:09.043 that it's like a lot dot something or whatever.
00:18:10.143 --> 00:18:11.773 So, like requires a lot. We don't care.
00:18:12.733 --> 00:18:15.335 Uh, let's move and that's the only spot in this file. OK, so
00:18:15.335 --> 00:18:18.022 we're just double checking the files, making sure that there's
00:18:18.022 --> 00:18:20.155 not settings we would need to add for this, or or
00:18:20.155 --> 00:18:22.885 modifications that would be part of this. OK. And then the next
00:18:22.885 --> 00:18:24.463 one is the Austin searching service.
00:18:25.173 --> 00:18:27.363 Again, I probably not expecting anything to actually change in
00:18:27.363 --> 00:18:29.483 this file, but we are checking it to see if there's anything
00:18:29.483 --> 00:18:30.283 that would be relevant.
00:18:31.553 --> 00:18:34.414 OK, we know that we can open the just module and that it's not
00:18:34.414 --> 00:18:37.410 gonna have anything in it. So if you just want to open it to look
00:18:37.410 --> 00:18:37.683 at it.
00:18:39.233 --> 00:18:41.912 It should say that there's nothing for lots on suggest
00:18:41.912 --> 00:18:42.253 module.
00:18:44.703 --> 00:18:47.483 OK. So then the last two files that would have something
00:18:47.483 --> 00:18:50.703 relevance in both cases would be the index and the search module.
00:18:50.703 --> 00:18:52.703 So the indexer will open that one first.
00:18:53.333 --> 00:18:56.524 So this is actually taking the data that we loaded from the
00:18:56.524 --> 00:18:59.715 dump reader and putting in translating it to the index part
00:18:59.715 --> 00:19:02.906 in here. And as you scroll through this file slowly, you'll
00:19:02.906 --> 00:19:06.257 see the first part of me here is it has an auto map on it that
00:19:06.257 --> 00:19:09.342 basically just automaps the properties from our indexable
00:19:09.342 --> 00:19:12.320 model into the version that's gonna be the type mapping
00:19:12.320 --> 00:19:15.724 descriptor, building stuff, and then just like it with the auto
00:19:15.724 --> 00:19:19.021 mapper plug in. If you were to actually use that you guys use
00:19:19.021 --> 00:19:21.627 that a lot in connect the properties can then be
00:19:21.627 --> 00:19:23.223 overridden with special stuff.
00:19:23.563 --> 00:19:26.189 So with like the name, the custom key, the brand name,
00:19:26.189 --> 00:19:28.720 manufacturer part number, the queryable serializable
00:19:28.720 --> 00:19:31.728 attributes value is aggregate blah blah blah blah blah which I
00:19:31.728 --> 00:19:34.641 know that's a mouthful. You start individually modifying how
00:19:34.641 --> 00:19:37.219 that stuff is going to be triggered and accounted for
00:19:37.219 --> 00:19:39.893 within the index whenever search data is applied to it.
00:19:42.223 --> 00:19:45.491 One of the things that we want to look for here is the price
00:19:45.491 --> 00:19:48.814 range section, which will handle the fact that is a numerical
00:19:48.814 --> 00:19:52.350 value. That is, it's a currency, and they're probably looking for
00:19:52.350 --> 00:19:55.672 a greater than or equal to or less than or equal to depending
00:19:55.672 --> 00:19:59.155 on what we're trying to do here for that stuff, that is probably
00:19:59.155 --> 00:20:02.156 not in this file or is in another section of this file.
00:20:02.156 --> 00:20:05.371 But let's scroll through this function here first with this
00:20:05.371 --> 00:20:08.693 mapper and look at the different stuff so you can see here we
00:20:08.693 --> 00:20:10.783 have attributes going in and then the.
00:20:10.863 --> 00:20:14.138 The attributes look at their unit of measure, the value, the
00:20:14.138 --> 00:20:17.466 key, the ID. The requires roles list looks for the roles. The
00:20:17.466 --> 00:20:20.902 brand filter looks for the brand stuff and that's not the brand
00:20:20.902 --> 00:20:24.016 name like Home Depot. That's like the that's the branding
00:20:24.016 --> 00:20:27.451 franchise store feature. Those pieces. And then like categories
00:20:27.451 --> 00:20:30.726 by name and by their keys, the franchises, the manufacturers
00:20:30.726 --> 00:20:32.283 there should also be vendors.
00:20:33.753 --> 00:20:36.819 There's something here that are commented out that's so I could
00:20:36.819 --> 00:20:39.645 have the file like the lot indexer and the product indexer
00:20:39.645 --> 00:20:42.568 side by side and compare them relatively easily and just and
00:20:42.568 --> 00:20:45.682 just have to ignore the comments that out parts so that it's not
00:20:45.682 --> 00:20:48.843 like misaligning the file as I'm looking at it when I'm comparing
00:20:48.843 --> 00:20:49.083 them.
00:20:49.723 --> 00:20:50.853 UM on there.
00:20:52.223 --> 00:20:55.075 So again, we have the store stuff, we had the vendor stuff
00:20:55.075 --> 00:20:58.168 and then we that below that we have the autocomplete parts that
00:20:58.168 --> 00:21:01.020 that transfer over to the suggestion section. So as far as
00:21:01.020 --> 00:21:03.776 I could tell here with the indexer file, there's nothing
00:21:03.776 --> 00:21:06.821 that's gonna be rolled into the lots part. So we don't have to
00:21:06.821 --> 00:21:09.818 do anything else inside this file. Let's go ahead and go over
00:21:09.818 --> 00:21:10.833 to the search module.
00:21:12.753 --> 00:21:16.133 Because I believe what's gonna happen is it's just automapping
00:21:16.133 --> 00:21:19.352 the fact that it's a decimal value into the index of model.
00:21:19.352 --> 00:21:22.678 So we just need to worry about the search part of it actually
00:21:22.678 --> 00:21:26.166 like registering a special spot that says to look for that value
00:21:26.166 --> 00:21:29.224 that's already gonna be on the model and compare it as a
00:21:29.224 --> 00:21:29.653 decimal.
00:21:29.833 --> 00:21:33.112 You know above below equal to whatever we're gonna do. So as
00:21:33.112 --> 00:21:36.606 we scroll through this file, the search module, this is the part
00:21:36.606 --> 00:21:39.562 that actually builds the internal query in their query
00:21:39.562 --> 00:21:42.949 descriptor language that elastic search uses on their end. The
00:21:42.949 --> 00:21:46.282 first one we have in the file here is the sorting, which will
00:21:46.282 --> 00:21:49.561 translate out like you know, if we're gonna sort by the name
00:21:49.561 --> 00:21:52.947 ascending, then it says to on the sort to do ascending by name
00:21:52.947 --> 00:21:56.226 with a suffix of raw for the actual like raw name of it, not
00:21:56.226 --> 00:21:59.720 one of the subsections where it broke out the name into multiple
00:21:59.720 --> 00:22:00.043 parts.
00:22:00.323 --> 00:22:03.279 For indexing and for fuzzy search, it's just using the raw
00:22:03.279 --> 00:22:04.833 name as it is to do that stuff.
00:22:05.893 --> 00:22:09.636 Similarly, if we wanted to sort by the pricing, it's the pricing
00:22:09.636 --> 00:22:13.033 to index as and we get a sort dot ascending on that piece.
00:22:29.183 --> 00:22:29.533 OK.
00:22:31.323 --> 00:22:33.543 So we are going to collapse the sort function.
00:22:37.233 --> 00:22:39.093 Uh, how do you do that again?
00:22:39.253 --> 00:22:42.043 Line 31, we just got the little box.
00:22:42.053 --> 00:22:42.793 Ah, there we go.
00:22:43.343 --> 00:22:46.572 There you go. OK, so the next one here is aggregations.
00:22:46.572 --> 00:22:50.146 Aggregations are not data that's directly on the main bottle,
00:22:50.146 --> 00:22:53.548 it's data that's gonna be in sublists of of the model. For
00:22:53.548 --> 00:22:57.123 instance, the types would be coming in as a list of types for
00:22:57.123 --> 00:23:00.467 things, the list of stores the list of pricing ranges and
00:23:00.467 --> 00:23:03.926 ratings are ranges that you would be relevant in there. The
00:23:03.926 --> 00:23:07.270 list of attributes written, their individual comparisons,
00:23:07.270 --> 00:23:10.961 and it basically aggregates that data onto the query and allows
00:23:10.961 --> 00:23:14.593 them to return as part of the as lists for our filter sidebar.
00:23:14.993 --> 00:23:18.550 Of the main catalog, so the the types for instance would say
00:23:18.550 --> 00:23:22.224 like what kinds of product types are there in the catalog that
00:23:22.224 --> 00:23:25.665 you could show up. There might be kits, variants, or basic
00:23:25.665 --> 00:23:29.281 regular general products for the vendors list it would be the
00:23:29.281 --> 00:23:32.838 list of vendors that would be available in the store for the
00:23:32.838 --> 00:23:36.279 attributes it would be what attributes can physically show
00:23:36.279 --> 00:23:39.778 up inside the bar that says you know color red, green, blue
00:23:39.778 --> 00:23:40.303 material.
00:23:40.623 --> 00:23:44.041 UM is gonna be, you know, wood, metal, cement, whatever. The the
00:23:44.041 --> 00:23:46.827 materials that's made for in those attributes and it
00:23:46.827 --> 00:23:49.982 aggregates them so that they could display in that data and
00:23:49.982 --> 00:23:52.979 show us how many products conform to that attribute data
00:23:52.979 --> 00:23:56.186 value for stuff. So that's what those things go. And I'm not
00:23:56.186 --> 00:23:59.656 gonna look into those individual ones right now, but that's where
00:23:59.656 --> 00:24:02.969 a lot of stuff does. And again we have another like I've gotta
00:24:02.969 --> 00:24:06.229 commented out one because it's not relevant for products, but
00:24:06.229 --> 00:24:09.489 this would be relevant for a lots or it might be relevant for
00:24:09.489 --> 00:24:10.593 categories of stores.
00:24:11.163 --> 00:24:13.954 In which case you're saying you know this. This stuff is in
00:24:13.954 --> 00:24:17.024 here, and I'm doing it so that I can line up my file in win merge
00:24:17.024 --> 00:24:20.047 when I'm comparing them side by side to look for some for like a
00:24:20.047 --> 00:24:22.745 problem that I'm implementing, or a problem having in the
00:24:22.745 --> 00:24:23.443 implementation.
00:24:24.753 --> 00:24:26.633 Go ahead and collapse that aggregations.
00:24:28.163 --> 00:24:28.653 Umm.
00:24:30.043 --> 00:24:34.821 And then we have the Bing query itself. So let's go ahead and
00:24:34.821 --> 00:24:39.599 expand that first block in there that set on 76, the matching
00:24:39.599 --> 00:24:44.223 prefix. When we check for a query term for something like I
00:24:44.223 --> 00:24:48.925 I'm looking for a Nikon camera and I accidentally type in in
00:24:48.925 --> 00:24:49.233 IOM.
00:24:49.803 --> 00:24:53.238 I I still wanna be able to have that search result come up
00:24:53.238 --> 00:24:56.557 because because of fuzzy matching. So when I do that, my
00:24:56.557 --> 00:24:59.934 camera that is actually the Nikon camera or or you know I
00:24:59.934 --> 00:25:03.544 could have five or six of them inside my catalog, whatever of
00:25:03.544 --> 00:25:06.863 different models of Nikon cameras, I'll have the name of
00:25:06.863 --> 00:25:10.648 that thing off the product go in and it does a suffix of keyword
00:25:10.648 --> 00:25:14.257 in which case it breaks apart the word of the entire title of
00:25:14.257 --> 00:25:17.867 the product into sub pieces and each of the sub pieces one of
00:25:17.867 --> 00:25:20.313 them is probably gonna be the word Nikon.
00:25:20.623 --> 00:25:24.050 And then I'll add fuzziness with auto, in which case it'll say
00:25:24.050 --> 00:25:27.477 like if it's a 5 letter word, it'll probably allow up to three
00:25:27.477 --> 00:25:31.067 characters to be fuzzy, in which case they have to exactly match,
00:25:31.067 --> 00:25:34.330 so the might not come at the with an IMM at the end instead
00:25:34.330 --> 00:25:37.757 of an in that I typed into my search because I fat fingered it
00:25:37.757 --> 00:25:40.912 or I didn't know the correct name of it. It's still gonna
00:25:40.912 --> 00:25:44.448 bring it up and show the user in there with that stuff, and then
00:25:44.448 --> 00:25:47.712 I have boosts for matching whether it's a prefix, the name,
00:25:47.712 --> 00:25:50.431 or as a term. These are individual options within
00:25:50.431 --> 00:25:51.193 Elasticsearch.
00:25:51.353 --> 00:25:54.253 To try and match it and I have boost values for each one of
00:25:54.253 --> 00:25:57.396 those things for to weight that search value for how closely you
00:25:57.396 --> 00:25:59.523 matched what you what was going on with it.
00:26:01.173 --> 00:26:04.328 So that's how the the basic search functionality works. For
00:26:04.328 --> 00:26:07.377 just checking a particular property with a particular set
00:26:07.377 --> 00:26:10.585 of values of the search term for. So you can see we have our
00:26:10.585 --> 00:26:13.477 form dot query, that's the search term that the person
00:26:13.477 --> 00:26:15.843 physically typed into the storefront search.
00:26:17.053 --> 00:26:20.811 So by batching that stuff we get all that wonderfulness in there
00:26:20.811 --> 00:26:24.338 for the query and that's the basic check of of what the what
00:26:24.338 --> 00:26:27.865 the name is. You'll see that custom key and SKU is basically
00:26:27.865 --> 00:26:31.276 this exact same thing and it has its own set of boosts for
00:26:31.276 --> 00:26:34.803 matching. So I might heavily weight the the name and heavily
00:26:34.803 --> 00:26:38.214 weight the skew if the person typed the actual skew in for
00:26:38.214 --> 00:26:39.313 what my values are.
00:26:40.663 --> 00:26:43.998 And you can see like match Bright brand name with a massive
00:26:43.998 --> 00:26:47.501 boost. We have A and our default values for the boost. We have
00:26:47.501 --> 00:26:50.836 brand names have a really high matching values. So if I had
00:26:50.836 --> 00:26:54.227 into the brand name property of the products, the word Nikon
00:26:54.227 --> 00:26:57.785 then that you would also give it a massive boost to say OK this
00:26:57.785 --> 00:27:01.288 is really close to Nikon. When he typed in Nikon. So let's get
00:27:01.288 --> 00:27:04.123 that up there as much as possible for matching it.
00:27:05.523 --> 00:27:08.269 As your keywords category, that stuff they start getting into
00:27:08.269 --> 00:27:11.148 more and more fuzzy matching and they have lower and lower boost
00:27:11.148 --> 00:27:11.813 values on them.
00:27:13.043 --> 00:27:15.901 So let's ignore those for the moment. Go ahead and expand the
00:27:15.901 --> 00:27:18.345 queryable serializable attributes that aggregate one
00:27:18.345 --> 00:27:19.313 that really long one.
00:27:21.013 --> 00:27:24.016 This one gets into fuzzy matching, where basically I
00:27:24.016 --> 00:27:27.700 aggregated all the text from all of our our creatable attributes
00:27:27.700 --> 00:27:30.986 together and made it into one long string for it to break
00:27:30.986 --> 00:27:34.160 apart and try to imagine a value. I won't add nearly as
00:27:34.160 --> 00:27:34.443 high.
00:27:34.683 --> 00:27:37.728 Hey, of a boost value to this query, but if it does match
00:27:37.728 --> 00:27:40.931 something in those values then I know that I wanna keep that
00:27:40.931 --> 00:27:44.344 inside the thing, so maybe they included not just the word Nikon
00:27:44.344 --> 00:27:47.180 in the search thing, but they said blue if one of the
00:27:47.180 --> 00:27:50.383 attributes that's queryable serializable on there it has the
00:27:50.383 --> 00:27:51.223 word blue in it.
00:27:52.363 --> 00:27:54.869 Then that's a reference that will help weight this one a
00:27:54.869 --> 00:27:57.638 little bit higher than the pink one. That doesn't say blue, so
00:27:57.638 --> 00:28:00.408 that affects my query and gets my boost up a little bit higher
00:28:00.408 --> 00:28:01.463 for that stuff on there.
00:28:03.063 --> 00:28:06.521 And then we have the function score one the function score one
00:28:06.521 --> 00:28:09.485 really gets into the nitty gritty of a whole bunch of
00:28:09.485 --> 00:28:10.473 random properties.
00:28:11.673 --> 00:28:14.811 Ran up in that I've I've specified each one, but any one
00:28:14.811 --> 00:28:18.444 of these could have some kind of value that says that it at least
00:28:18.444 --> 00:28:21.967 somewhat matched what they were typing in, and so we check them
00:28:21.967 --> 00:28:25.325 for a whole bunch of different things and we give them small
00:28:25.325 --> 00:28:28.792 boosts on their stuff. So like instead of 100 it might be like
00:28:28.792 --> 00:28:32.260 A5 or A1 or a .25 or something like that. Really small just to
00:28:32.260 --> 00:28:35.453 say that it was some kind of value that gave it to let it
00:28:35.453 --> 00:28:38.811 show up inside the results and that. But it's gonna show it,
00:28:38.811 --> 00:28:41.013 like really low in the relevancy score.
00:28:41.673 --> 00:28:44.785 For the stuff, so we're, we're we're doing a broad spectrum
00:28:44.785 --> 00:28:47.948 shotgun approach of let's find something on the product that
00:28:47.948 --> 00:28:51.164 matched what they what they were typing in, whatever they had
00:28:51.164 --> 00:28:54.431 typed in it, because they all get to a fuzziness auto. It's an
00:28:54.431 --> 00:28:57.698 aura operator and then they use an analyzer that will break it
00:28:57.698 --> 00:29:00.395 apart, whatever the value is into individual words,
00:29:00.395 --> 00:29:03.403 capitalizations, fuzzy matching, all of that stuff there.
00:29:05.023 --> 00:29:08.153 For what we're trying to do, we're not going beyond this
00:29:08.153 --> 00:29:11.504 point and we're actually looking for a specific statement of
00:29:11.504 --> 00:29:12.053 that, our.
00:29:13.913 --> 00:29:17.100 At that hour starting price was above or below some certain
00:29:17.100 --> 00:29:19.703 value that we had we were selecting from the UI.
00:29:20.983 --> 00:29:22.733 So as we Scroll down a little bit further.
00:29:24.903 --> 00:29:28.255 We have the brand name, we have the with lots. It has the lot so
00:29:28.255 --> 00:29:31.555 that you know doesn't have a lot on there as a as a on our form
00:29:31.555 --> 00:29:34.906 with a width lots true and then we start getting our aggregates.
00:29:34.906 --> 00:29:37.691 The price ranges query modification is the closest to
00:29:37.691 --> 00:29:40.888 what we want to look for. So let's go ahead and control click
00:29:40.888 --> 00:29:44.033 on that function name and go into where that one gets built.
00:29:46.503 --> 00:29:49.507 Go ahead, pin this file open because it is going to be
00:29:49.507 --> 00:29:52.674 relevant and you'll see that this file is a separate file
00:29:51.323 --> 00:29:51.943 That's not.
00:29:52.674 --> 00:29:52.893 out.
00:29:54.213 --> 00:29:54.683 That's fine.
00:29:55.983 --> 00:29:57.333 Yeah, didn't mean to do that.
00:29:56.683 --> 00:29:59.433 I think you just have to drag it, drag it by the tab name.
00:30:00.743 --> 00:30:01.413 There we go.
00:30:00.863 --> 00:30:01.343 Yeah, they go.
00:30:02.933 --> 00:30:04.153 There we go and pin that there we go.
00:30:05.643 --> 00:30:08.294 Go ahead on the right side in the solution explorer at the top
00:30:08.294 --> 00:30:10.650 there's a double arrow, one pointing left, one pointing
00:30:10.650 --> 00:30:10.903 right.
00:30:13.083 --> 00:30:15.441 And that will let you jump to these to the where the active
00:30:15.441 --> 00:30:15.913 document is.
00:30:16.933 --> 00:30:20.218 There we go. So you can see in the elastic search under score
00:30:20.218 --> 00:30:23.239 base folder. Here we have a whole bunch of search module
00:30:23.239 --> 00:30:26.577 based out mods. This is because like franchises and categories
00:30:26.577 --> 00:30:29.757 and stuff are applicable to multiple types of searches that
00:30:29.757 --> 00:30:32.618 we have for stores, vendors, manufacturers, all those
00:30:32.618 --> 00:30:35.745 different things. So we added these mods down here as an A
00:30:35.745 --> 00:30:38.818 generic way. They're using generics and they're done in a
00:30:38.818 --> 00:30:41.998 way that basically says as long as it conforms to some core
00:30:41.998 --> 00:30:45.124 statement of I intend to have pricing ranges on this thing
00:30:45.124 --> 00:30:47.403 like lots and products would both do that.
00:30:48.493 --> 00:30:51.133 Then I will allow this to be done here and I can only have to
00:30:51.133 --> 00:30:53.901 write the code once and I don't. I don't have to rewrite it with
00:30:53.901 --> 00:30:56.541 all the specifics of each one, copy and paste it if there's a
00:30:56.541 --> 00:30:58.883 bug I have to fix, I don't have to fix it in one spot.
00:31:00.443 --> 00:31:03.791 So in the pricing range thing here we see that we have on our
00:31:03.791 --> 00:31:07.247 query that if we add it, if if there were any pricing ranges in
00:31:07.247 --> 00:31:10.649 the form we add on to the query a Boolean check that says that
00:31:10.649 --> 00:31:13.889 it matches one of those things at that particular weight or
00:31:13.889 --> 00:31:17.237 which is what the boosting is. So the should there on line 48
00:31:17.237 --> 00:31:20.747 it says create the pricing range query lambdas and passes in the
00:31:20.747 --> 00:31:23.123 form to it. So go to that one's definition.
00:31:26.143 --> 00:31:29.158 You can see here this is how it's actually building the price
00:31:29.158 --> 00:31:32.172 range queries on here. Now the price range queries themselves
00:31:32.172 --> 00:31:34.847 are dynamic, either by an automated check through like
00:31:34.847 --> 00:31:37.764 what you're pricing. Data is throughout the entire website,
00:31:37.764 --> 00:31:40.633 or by specifying those values manually within settings. It
00:31:40.633 --> 00:31:43.696 does it a couple of different ways, but All in all the pricing
00:31:43.696 --> 00:31:46.711 data will have loaded into this form and made it available to
00:31:46.711 --> 00:31:49.823 what the form pricing are. And so we're gonna loop through each
00:31:49.823 --> 00:31:52.789 one and say that it must match one of these things when they
00:31:52.789 --> 00:31:55.804 get selected and you can see that it breaks apart the text on
00:31:55.804 --> 00:31:56.533 that that says.
00:31:56.693 --> 00:31:59.712 You know, if there's a less than than do it this way, if there's
00:31:59.712 --> 00:32:01.803 a A+, that means anything above that amount.
00:32:03.163 --> 00:32:06.594 And then the last one is the fall back that says it must be
00:32:06.594 --> 00:32:10.253 between between a minimum and a maximum value. So it's a range.
00:32:11.313 --> 00:32:15.340 And an individually posts these values in here for that stuff.
00:32:15.340 --> 00:32:19.367 Now the question I'm gonna put to lie in here is which way did
00:32:19.367 --> 00:32:22.946 we intend to have this be handled? Are we just doing it
00:32:22.946 --> 00:32:26.973 must match? Are we just doing a? This is the maximum or are we
00:32:26.973 --> 00:32:30.744 doing a this is it must be between two values like how the
00:32:30.744 --> 00:32:34.515 pricing ranges queries work for the pricing of the current
00:32:34.515 --> 00:32:34.963 prices.
00:32:35.793 --> 00:32:39.116 An interesting question. For this specific we're building
00:32:39.116 --> 00:32:42.268 this sort of kind of for a client, but also for core a
00:32:42.268 --> 00:32:43.643 little bit more vaguely.
00:32:44.943 --> 00:32:50.893 The the specific requirement is an account will have a limit.
00:32:51.903 --> 00:32:56.317 Above which they should not see any lot whose starting prices is
00:32:56.317 --> 00:33:00.460 basically a greater than their amount. So basically if a lot
00:33:00.460 --> 00:33:04.671 has a $10,000 starting price and my account like deems that I
00:33:04.671 --> 00:33:08.814 have a limit starting price limit of 5000 then I wouldn't. I
00:33:08.814 --> 00:33:13.024 wouldn't be able to see that lot in the results. So it should
00:33:13.024 --> 00:33:16.692 filter out anything. So basically it's a less than or
00:33:16.692 --> 00:33:17.303 equal to.
00:33:17.903 --> 00:33:20.406 Umm. And then that amount will be passed in. So it's basically
00:33:18.613 --> 00:33:19.543 Yes, OK.
00:33:20.406 --> 00:33:23.028 just always a less than or equal to in the future. I could see it
00:33:22.403 --> 00:33:23.733 So what we wanna do?
00:33:23.028 --> 00:33:25.293 doing a range, but I don't think we need that right now.
00:33:26.013 --> 00:33:29.563 So what we wanna do is because part of the logic that we want
00:33:29.563 --> 00:33:32.884 is inside this file, let's go ahead and clone the pricing
00:33:32.884 --> 00:33:36.262 ranges file. So copy and paste it over there and then what
00:33:36.262 --> 00:33:39.869 we're gonna do is we're gonna say it's gonna be dot dot credit
00:33:39.869 --> 00:33:40.213 limit.
00:33:40.973 --> 00:33:41.533 Uh.
00:33:42.563 --> 00:33:43.353 Uh.
00:33:44.513 --> 00:33:46.373 You saying I'm copying this file right here?
00:33:46.583 --> 00:33:48.997 Yeah, you're gonna copy the pricing ranges file, so just
00:33:48.943 --> 00:33:49.363 And.
00:33:48.997 --> 00:33:49.633 copy and paste.
00:33:50.733 --> 00:33:51.803 Right in the same folder.
00:33:54.183 --> 00:33:57.414 And they're gonna take the word, copped the dash, copy out, and
00:33:57.414 --> 00:33:59.433 you're gonna change the the mod to say.
00:34:01.893 --> 00:34:04.943 Starting price credit limit.
00:34:15.803 --> 00:34:16.113 Yeah.
00:34:17.103 --> 00:34:19.979 And that will be our new file name. So we'll open this new
00:34:19.979 --> 00:34:20.223 file.
00:34:22.013 --> 00:34:24.732 And inside here at the very top there online one there's the
00:34:24.732 --> 00:34:27.274 search module based on model pricing ranges, you need to
00:34:27.274 --> 00:34:29.503 update that pricing ranges to match the new name.
00:34:31.863 --> 00:34:33.775 Or stock up will complain because it doesn't match the
00:34:33.775 --> 00:34:34.123 file name.
00:34:36.103 --> 00:34:39.446 And a couple lines below that online four, it's got the
00:34:39.446 --> 00:34:43.027 pricing ranges. So you're just update that to say that it's
00:34:43.027 --> 00:34:45.833 it's actually the starting price credit limit.
00:34:59.713 --> 00:35:03.494 OK. And then at the top here, we've got a or a lunch. Sorry
00:35:03.494 --> 00:35:06.393 lineland teen. And it has a constant strings.
00:35:07.213 --> 00:35:09.233 Section. Let's go and expand that.
00:35:11.523 --> 00:35:14.797 Now the the range game for record pricing ranges, that's
00:35:14.797 --> 00:35:18.531 not really gonna be relevant to this in the same way. So what we
00:35:18.531 --> 00:35:22.150 wanna do is change this name to say instead of pricing ranges,
00:35:22.150 --> 00:35:23.873 it's gonna say maximum limits.
00:35:25.833 --> 00:35:26.573 Value.
00:35:29.203 --> 00:35:31.901 And we'll just leave it like that. And then in the count in
00:35:31.901 --> 00:35:34.239 the in the string content instead of record pricing
00:35:34.239 --> 00:35:35.453 drainages, we're gonna say.
00:35:35.793 --> 00:35:38.863 Uh Max starting price limit?
00:35:39.603 --> 00:35:41.193 So it's gonna be record dash.
00:35:41.343 --> 00:35:44.718 Uh Max starting price limit as and it's gonna be that dashed
00:35:44.718 --> 00:35:47.153 format instead of camel case or snake case.
00:35:53.513 --> 00:35:55.383 And then we won't need the other two constants.
00:35:58.303 --> 00:36:01.839 We'll just drop those, OK. And then instead of price ranges,
00:36:01.839 --> 00:36:04.273 query modification, we're gonna be doing.
00:36:06.003 --> 00:36:10.228 Starting starting price, credit limit, query modification query,
00:36:10.228 --> 00:36:10.553 yeah.
00:36:17.493 --> 00:36:20.662 OK. And then what we're gonna do is if there's no setting for it
00:36:20.662 --> 00:36:23.636 that then it would turn it off. So we'll ignore that for the
00:36:23.636 --> 00:36:26.708 moment. We'll deal with that the settings section and then for
00:36:26.708 --> 00:36:29.535 the form dot pricing ranges instead of pricing ranges, we
00:36:29.535 --> 00:36:30.023 would say.
00:36:31.463 --> 00:36:32.363 A credit limit.
00:36:36.253 --> 00:36:42.071 And we'll do a if the credit limit is null or is less than or
00:36:42.071 --> 00:36:43.103 equal to 0.
00:36:44.163 --> 00:36:45.473 Then we will dump out.
00:36:48.133 --> 00:36:50.463 Are you talking this line or this line?
00:36:50.013 --> 00:36:52.173 Yeah, the the line 39.
00:36:53.523 --> 00:36:53.953 OK.
00:36:54.313 --> 00:36:58.671 So if the form credit limit is null, meaning not that has value
00:36:58.671 --> 00:37:01.463 or the value is less than or equal to 0.
00:37:07.103 --> 00:37:09.033 You can pattern match on this.
00:37:09.253 --> 00:37:11.523 Umm, which is fun.
00:37:12.803 --> 00:37:13.803 Uh, you can do.
00:37:13.083 --> 00:37:15.438 Let's let's let him have him type it out manually and then
00:37:15.438 --> 00:37:17.473 use the Visual Studio to pattern match it for him.
00:37:18.593 --> 00:37:19.033 Faster.
00:37:19.693 --> 00:37:23.420 So Capital H of your on your you only need a capital H because
00:37:20.323 --> 00:37:21.063 Has value.
00:37:23.420 --> 00:37:24.603 this is C# it's got.
00:37:26.153 --> 00:37:26.503 That.
00:37:27.513 --> 00:37:28.423 And then.
00:37:30.083 --> 00:37:30.613 Or.
00:37:33.733 --> 00:37:36.543 Uh format credit limit is less than or equal to 0M.
00:37:40.653 --> 00:37:43.347 So capital C make sure you're getting that that typing as
00:37:43.347 --> 00:37:45.763 you're as you're typing it less than or equal to 0.
00:37:46.553 --> 00:37:47.003 M.
00:37:50.473 --> 00:37:53.103 And I think you'll want a not on that first half, right?
00:37:53.683 --> 00:37:57.073 He will. I'm going to put an e-mail on that zero.
00:37:59.753 --> 00:38:00.993 Put a one on the 0.
00:38:01.163 --> 00:38:03.373 And M like M for monkey.
00:38:02.413 --> 00:38:03.153 The letter M.
00:38:04.593 --> 00:38:04.793 Yep.
00:38:05.333 --> 00:38:06.763 And then get rid of that space after it.
00:38:09.373 --> 00:38:09.593 Yeah.
00:38:11.833 --> 00:38:14.784 A knot right there. Yep. So it. So if it doesn't have a value,
00:38:12.573 --> 00:38:13.133 Yeah, yeah.
00:38:14.784 --> 00:38:17.548 meaning that it's null or the value is there but it's less
00:38:17.548 --> 00:38:20.452 than or equal to 0, then we're gonna return out and not apply
00:38:20.452 --> 00:38:20.593 it.
00:38:21.773 --> 00:38:24.401 So because that property is not there, which is why you get your
00:38:24.401 --> 00:38:26.826 rights wiggly. Let's control period on that line so that we
00:38:26.826 --> 00:38:28.403 can generate the property on the form.
00:38:33.253 --> 00:38:34.333 Generate property credit limit.
00:38:35.453 --> 00:38:35.663 Yep.
00:38:38.053 --> 00:38:40.828 And then control click on it so that we will go to its
00:38:40.828 --> 00:38:41.383 definition.
00:38:43.103 --> 00:38:45.662 Because it generated as object, we're gonna change it to decimal
00:38:45.662 --> 00:38:46.213 question mark.
00:38:52.813 --> 00:38:56.036 And then just like with that vendor ID's all copy the
00:38:56.036 --> 00:38:59.975 documentation and the API member off of it and put it onto credit
00:38:59.975 --> 00:39:00.333 limit.
00:39:00.953 --> 00:39:02.893 And then make sure there's a blank line between the
00:39:02.893 --> 00:39:03.303 properties.
00:39:09.643 --> 00:39:12.725 OK. And then we'll change the text on that one to say instead
00:39:12.725 --> 00:39:15.509 of get sets the vendor identifiers all will say gets or
00:39:15.509 --> 00:39:16.603 sets the credit limit.
00:39:21.133 --> 00:39:23.303 And then the value, the credit limit.
00:39:28.553 --> 00:39:32.217 Yep. And then on the API line 319 where it says name of vendor
00:39:32.217 --> 00:39:34.893 ID's all put the credit limit property there.
00:39:37.593 --> 00:39:39.663 The data type will be decibel, question mark.
00:39:48.013 --> 00:39:50.203 And then we get to keep the decimal value of null.
00:39:51.493 --> 00:39:54.463 The default value or not OK, so now we have our property on our
00:39:54.463 --> 00:39:56.413 form which is great. So we save the form.
00:39:57.433 --> 00:39:59.593 And then we switch back over to the file we were just in.
00:40:02.433 --> 00:40:04.863 Be this guy, yeah.
00:40:04.163 --> 00:40:04.363 Yeah.
00:40:05.093 --> 00:40:08.763 Yeah. There you go. OK. So then next, we're gonna do instead of
00:40:08.763 --> 00:40:12.262 range name for pricing for for record pricing ranges, you're
00:40:12.262 --> 00:40:15.875 gonna use the property name or the the constant we have at the
00:40:15.875 --> 00:40:16.793 top of the file.
00:40:22.143 --> 00:40:22.333 Yep.
00:40:23.053 --> 00:40:29.383 And then put it where that first one is on 46. No, I'm sorry, 44.
00:40:32.923 --> 00:40:35.291 OK. And then instead of searching boost pricing ranges
00:40:35.291 --> 00:40:37.143 are gonna do searching boost credit limit.
00:40:44.043 --> 00:40:47.307 And then while we're here, before we go over to that one,
00:40:47.307 --> 00:40:50.853 uh, instead of create price ring range query lambdas do create
00:40:50.853 --> 00:40:51.923 credit limit query.
00:40:59.663 --> 00:41:00.953 And you could take the lambdas off.
00:41:04.933 --> 00:41:05.393 There we go.
00:41:07.063 --> 00:41:08.663 And the minimum should match this one.
00:41:09.403 --> 00:41:12.543 OK, so now we're going to do on that. Searching boost credit
00:41:12.543 --> 00:41:15.374 limit. We're going to create that property. So control
00:41:15.374 --> 00:41:16.713 period, generate property.
00:41:20.163 --> 00:41:23.538 And then we go over to its definition and you can see
00:41:23.538 --> 00:41:24.913 there's another boost.
00:41:25.633 --> 00:41:29.933 I'll let's look for the pricing one in here. Ohh it put it into
00:41:29.933 --> 00:41:33.023 the manufacturers file. OK before we do that.
00:41:34.213 --> 00:41:36.323 Go ahead and make sure the the file stays open.
00:41:37.413 --> 00:41:38.743 Right now it's in the preview mode.
00:41:40.033 --> 00:41:42.905 I normally turn that preview mode off. It's that little. It's
00:41:42.905 --> 00:41:45.684 that little icon right next to the X, just like the pin one
00:41:45.684 --> 00:41:48.416 would be when you're in that preview, but you can set up a
00:41:48.416 --> 00:41:50.223 double click it or anything like that.
00:41:50.973 --> 00:41:51.403 OK.
00:41:52.003 --> 00:41:53.063 So go ahead and pin it now.
00:41:54.873 --> 00:41:57.597 Go ahead and do the sync button on the solution Explorer, which
00:41:57.597 --> 00:41:59.343 is the arrow pointing left and pointing.
00:42:00.333 --> 00:42:00.643 Yep.
00:42:00.843 --> 00:42:02.723 There we go. OK, now Scroll down a smidge.
00:42:04.943 --> 00:42:08.560 Uh, OK, so you see how it's got mod sat pricing ranges and mods
00:42:08.560 --> 00:42:12.008 that manufacturers we need to make a file this mods starting
00:42:12.008 --> 00:42:15.569 price credit limit. So copy the manufacturers one that has our
00:42:15.569 --> 00:42:16.643 new property in it.
00:42:25.223 --> 00:42:27.413 Yep. And so it'll be starting price credit limit.
00:42:28.193 --> 00:42:29.563 And getting rid of the word copy.
00:42:41.123 --> 00:42:43.683 OK, now let's open that copied file.
00:42:45.373 --> 00:42:49.663 And then trash everything after line 14 basically.
00:42:54.673 --> 00:42:57.117 OK. And then let's go ahead and add the two closing braces that
00:42:57.117 --> 00:42:59.103 we need to close the class and close the namespace.
00:43:02.643 --> 00:43:05.729 And then the new line at the end so that we are have a blank line
00:43:05.729 --> 00:43:06.243 at the end.
00:43:07.783 --> 00:43:11.132 Yep, OK. And then over in the manufacturers file that we had
00:43:08.993 --> 00:43:09.823 Is that important?
00:43:11.132 --> 00:43:13.493 kept open click on the manufacturers file.
00:43:14.903 --> 00:43:16.553 We want to get that one out of there.
00:43:17.823 --> 00:43:19.973 So we take out line 13 and 14.
00:43:24.673 --> 00:43:29.179 OK, let's copy the the. Let's go ahead and copy that search boost
00:43:29.179 --> 00:43:31.023 all manufacturers property.
00:43:33.183 --> 00:43:36.436 So that we can just use it as a template for the other one. You
00:43:36.436 --> 00:43:38.673 wanna copy the like of lines 13 to 21? Yep.
00:43:39.503 --> 00:43:40.573 And go back over to credit limit.
00:43:42.293 --> 00:43:43.733 And paste it in after that one.
00:43:48.503 --> 00:43:52.066 That's good enough. We just using as the template. So we
00:43:52.066 --> 00:43:56.005 want the comments, we want the attributes and we want the body
00:43:56.005 --> 00:43:58.693 that does the the get and the private set.
00:44:02.853 --> 00:44:03.803 I'm sorry. Say that again.
00:44:04.873 --> 00:44:07.726 We're changing how is is currently says public static
00:44:07.726 --> 00:44:11.213 double get with internal set. We wanted to format like that other
00:44:11.213 --> 00:44:14.382 one is where it's internal static and it has the the getter
00:44:14.382 --> 00:44:16.073 of the setter that that one has.
00:44:18.553 --> 00:44:21.783 OK, so I'm changing this to.
00:44:22.843 --> 00:44:26.503 Not not there on line 13. The property itself, not the class.
00:44:22.923 --> 00:44:23.643 Barry, is it?
00:44:27.023 --> 00:44:27.993 OK. Gotcha.
00:44:29.123 --> 00:44:30.453 So I'm taking that.
00:44:33.833 --> 00:44:34.333 Yes.
00:44:33.993 --> 00:44:37.002 Do you want? Yeah, you'll want that property to be internal.
00:44:37.002 --> 00:44:37.693 Static double.
00:44:38.393 --> 00:44:39.773 Rather than public static double.
00:44:42.173 --> 00:44:44.543 Service change public to internal on line 13.
00:44:45.133 --> 00:44:45.383 Yeah.
00:44:47.773 --> 00:44:48.593 Probably to internal.
00:44:49.313 --> 00:44:53.069 And for the folks who are newer, I actually really for anybody do
00:44:53.069 --> 00:44:56.483 you, are you guys familiar with the internal keyword in C#?
00:44:57.423 --> 00:44:59.003 Anybody not familiar with it?
00:44:59.763 --> 00:45:00.003 Yeah.
00:45:00.343 --> 00:45:01.033 Yeah.
00:45:03.283 --> 00:45:04.333 OK, well for anybody.
00:45:03.353 --> 00:45:06.017 Internal means that it it's effectively public, but it
00:45:06.017 --> 00:45:09.213 public to the DLL inside itself. It's not public outside the DLL.
00:45:09.663 --> 00:45:13.004 Yep. So even though that the even though this class can be
00:45:13.004 --> 00:45:16.684 accessed as if it were public to any other class inside the same
00:45:16.684 --> 00:45:19.912 assembly and and and and practical terms inside the same
00:45:19.912 --> 00:45:23.366 project, anything outside of this can't access this class or
00:45:23.366 --> 00:45:26.707 any of its members because they're internals it's internal
00:45:26.707 --> 00:45:27.613 to the assembly.
00:45:27.153 --> 00:45:27.373 Yeah.
00:45:28.333 --> 00:45:30.543 OK, delete everything at the.
00:45:28.863 --> 00:45:31.783 You know in Java they call it package private. Sorry.
00:45:31.753 --> 00:45:32.513 Yeah, yeah.
00:45:32.063 --> 00:45:32.333 Yeah.
00:45:33.263 --> 00:45:37.098 Umm on the end of line 13 where it's got get internal set,
00:45:37.098 --> 00:45:38.333 delete all of that.
00:45:39.643 --> 00:45:40.753 Everything after the word limit.
00:45:43.223 --> 00:45:46.827 Yeah. Now copy lines 21 to 24 and we don't want that semi
00:45:46.827 --> 00:45:47.573 colon there.
00:45:50.173 --> 00:45:53.513 Copy lines 21 to 24 and put them after line 13.
00:46:00.153 --> 00:46:04.620 Great. Now we want to copy the comments and the 20 the
00:46:04.620 --> 00:46:08.113 attributes on 22 and 23 to before line 13.
00:46:15.053 --> 00:46:18.103 OK, now get rid of the extra properties. So basically 23 to
00:46:18.103 --> 00:46:19.273 32, delete all of that.
00:46:23.623 --> 00:46:24.953 And get rid of that blank line. There you go.
00:46:25.643 --> 00:46:29.142 So that's what we wanted to do. Now, instead of searching boosts
00:46:29.142 --> 00:46:32.372 all manufacturers, we want searching boosts credit limit as
00:46:32.372 --> 00:46:33.503 the app settings key.
00:46:38.323 --> 00:46:40.784 And the default value for the boost here is gonna be 110. I
00:46:40.784 --> 00:46:43.204 don't see a reason to change that right now, so let's just
00:46:43.204 --> 00:46:43.983 leave it like that.
00:46:45.143 --> 00:46:47.711 But now we have our separate property that has on here we
00:46:47.711 --> 00:46:50.457 have all the stuff in it. Let's go and update the comment too
00:46:50.457 --> 00:46:52.627 instead of boost all manufacturers boosts credit
00:46:52.627 --> 00:46:52.893 limit.
00:46:58.823 --> 00:47:00.363 Yep, there in the line above.
00:47:05.423 --> 00:47:08.851 And then on line one, there's the mods that manufacturers
00:47:08.851 --> 00:47:11.983 change that to mods dot starting price credit limit.
00:47:22.063 --> 00:47:24.512 OK, so now we can save this file and this file has our setting
00:47:24.512 --> 00:47:26.962 at. If we're gonna add more if we end up adding more settings,
00:47:26.962 --> 00:47:28.323 we're gonna add them to this file.
00:47:29.373 --> 00:47:31.612 Go ahead and pin this one and you can go ahead and close the
00:47:31.612 --> 00:47:32.163 manufacturer 1.
00:47:38.043 --> 00:47:40.642 This says I had. It's on this file. I didn't change anything
00:47:40.642 --> 00:47:41.153 here, did I?
00:47:41.483 --> 00:47:43.483 It's fine, just save and close, it's fine.
00:47:46.683 --> 00:47:47.003 OK.
00:47:48.613 --> 00:47:51.828 So now we have our credit limit here. Let's go back over to the
00:47:51.828 --> 00:47:55.093 you can close the pricing ranges one, that's the tab to the left
00:47:55.093 --> 00:47:57.253 of the one that you currently have active.
00:48:00.413 --> 00:48:03.589 OK. Umm and then let's go over to the credit limit one which is
00:48:03.589 --> 00:48:05.723 2 to the right of the one you have active.
00:48:09.033 --> 00:48:12.243 OK, so now we have our create limit query. We have our boost
00:48:12.243 --> 00:48:15.663 there. Let's copy that function name on line 46 that says create
00:48:15.663 --> 00:48:16.663 credit limit query.
00:48:17.703 --> 00:48:20.396 And then we're going to Scroll down to where it does it. Did
00:48:20.396 --> 00:48:22.912 the create pricing ranges, whatever, which should be for
00:48:22.912 --> 00:48:23.133 down.
00:48:24.753 --> 00:48:27.963 So later there we go line 115.
00:48:28.763 --> 00:48:30.383 So gonna replace that name with this one.
00:48:33.263 --> 00:48:35.971 OK. And then the the comment on it for the summary is gonna be
00:48:35.971 --> 00:48:38.163 instead of pricing range is gonna be credit limit?
00:48:43.643 --> 00:48:51.753 OK, now our form for the value instead of having a credit limit
00:48:51.753 --> 00:48:52.133 of.
00:48:54.543 --> 00:48:57.278 Instead of having this pricing range queries and some of this
00:48:57.278 --> 00:48:59.925 other stuff in here, we're gonna do some slightly different
00:48:59.925 --> 00:49:02.528 stuff. We are gonna have good have. We're gonna have a one
00:49:02.528 --> 00:49:02.793 query.
00:49:03.873 --> 00:49:08.563 But into the queries. So what? We'll keep it as a list. So on
00:49:08.563 --> 00:49:11.513 line 118, click on that variable name.
00:49:12.483 --> 00:49:14.403 And press control R twice.
00:49:17.523 --> 00:49:20.486 OK, so this is gonna activate the rename and then the rename.
00:49:20.486 --> 00:49:22.303 We're gonna say credit limit queries.
00:49:28.663 --> 00:49:30.873 And then you'll be able to hit enter to to save it.
00:49:31.973 --> 00:49:35.328 OK. And then the form instead of price ranges, we're gonna be
00:49:35.328 --> 00:49:36.843 looking at the credit limit?
00:49:41.603 --> 00:49:42.623 We're not renaming that.
00:49:43.443 --> 00:49:45.363 So we escape off of that case. We don't rename that.
00:49:47.393 --> 00:49:50.081 We already have the property that we named that we want on
00:49:50.081 --> 00:49:51.813 there. So just form dot credit limit.
00:49:55.203 --> 00:49:57.980 There we go. And then it says same. Check that we wanna do
00:49:57.980 --> 00:49:58.733 where it's it's.
00:50:00.473 --> 00:50:03.345 Uh, not has value and the less than or equal to null. So just
00:50:03.345 --> 00:50:05.893 like when I go copy it from the other one that's fine.
00:50:09.153 --> 00:50:11.441 It would be. It was in the same file, it was just, it was just a
00:50:11.441 --> 00:50:11.793 scroll up.
00:50:17.143 --> 00:50:18.093 Uh. For there? Yeah.
00:50:19.583 --> 00:50:19.993 Uh.
00:50:21.133 --> 00:50:22.463 Uh, yeah, they're line 39.
00:50:24.883 --> 00:50:26.043 Was just copy that guy.
00:50:34.753 --> 00:50:35.663 This line right?
00:50:36.123 --> 00:50:37.603 So we're replacing that whole thing, yeah.
00:50:40.503 --> 00:50:43.379 So basically it says is if it didn't pass anything there for
00:50:43.379 --> 00:50:46.303 us to actually check against, then we return the empty array.
00:50:47.703 --> 00:50:50.680 So basically meaning that the the query itself is gonna be not
00:50:50.680 --> 00:50:51.483 modified in Toto.
00:50:53.023 --> 00:50:56.235 We have a regex here that's gonna start processing the
00:50:56.235 --> 00:50:59.563 individual pricing ranges that would have been coming in
00:50:59.563 --> 00:51:03.125 previously. Since we're not needing to do that, we only have
00:51:03.125 --> 00:51:06.921 one static decimal value to deal with. We don't need that stuff.
00:51:06.921 --> 00:51:10.483 What we're gonna do is instead of that stuff as we basically
00:51:10.483 --> 00:51:14.046 the part of the query that we really want here is the online
00:51:14.046 --> 00:51:17.783 1:30. So from 1:30 to 1:36, take that and drag it above the for
00:51:17.783 --> 00:51:19.243 loop and above the regex.
00:51:22.713 --> 00:51:25.363 Taking it at it like cutting, cutting it out of here.
00:51:24.893 --> 00:51:28.542 So yeah, you can cut it, you can click and drag it whatever to
00:51:28.542 --> 00:51:30.743 get it up to between lines one 22123.
00:51:35.853 --> 00:51:38.293 OK, now you can trash the four loop in the regex.
00:51:44.283 --> 00:51:45.363 The.
00:51:45.443 --> 00:51:46.333 The whole thing.
00:51:47.063 --> 00:51:47.303 Yeah.
00:51:51.873 --> 00:51:53.923 I believe well, actually now that I'm seeing more of it,
00:51:53.923 --> 00:51:55.433 let's scroll back up before we delete it.
00:51:57.713 --> 00:51:58.763 RX.
00:52:00.013 --> 00:52:02.226 For contains a. Please it doesn't no because we only
00:52:02.226 --> 00:52:04.815 wanted that one less than the rest of has to do with matching
00:52:04.815 --> 00:52:07.488 ranges. So yeah, we can collapse the entire for loop and delete
00:52:07.488 --> 00:52:07.613 it.
00:52:10.613 --> 00:52:12.475 If you collapse it, you don't have to keep scrolling through
00:52:12.475 --> 00:52:12.963 the whole thing.
00:52:14.623 --> 00:52:15.743 Yes. So just, just.
00:52:14.683 --> 00:52:15.883 And the regex too, right?
00:52:16.533 --> 00:52:18.093 Yeah, the rejects. We're not using it.
00:52:20.883 --> 00:52:24.331 OK, so we have that blank line scroll up so that we see this in
00:52:24.331 --> 00:52:27.780 whole function in view. Let's go ahead and DNN indent the lines
00:52:27.780 --> 00:52:31.336 124 to 129 because it doesn't to be that far over. I believe it's
00:52:31.336 --> 00:52:32.953 just too intense to Shift tab.
00:52:33.953 --> 00:52:36.951 There we go. OK, so now the name has that temp pricing range.
00:52:36.951 --> 00:52:39.948 We're just gonna put a name in this gonna be another constant
00:52:39.948 --> 00:52:42.753 value. Just like at the top. So let's go back to the top.
00:52:45.663 --> 00:52:48.948 And then we'll add a second constant here that says range
00:52:48.948 --> 00:52:52.402 name for record bin last Max value. We'll we'll we'll say it
00:52:52.402 --> 00:52:56.027 as inner, just copy the previous line. You don't need to retype
00:52:56.027 --> 00:52:56.933 the whole thing.
00:53:01.873 --> 00:53:04.273 And then add the word word, dash inner to the end of it.
00:53:06.633 --> 00:53:09.568 It's as good as name is any for right now. And then add inner to
00:53:09.568 --> 00:53:11.103 the end of the the constant name.
00:53:15.793 --> 00:53:17.993 I'm gonna Jordan afterward, but either way is fine.
00:53:20.113 --> 00:53:21.783 OK. And get rid of the blank line on 22.
00:53:20.413 --> 00:53:21.183 You only switch it.
00:53:22.983 --> 00:53:25.793 Got it. It's fine. Leave it. But get rid of the blank line on 22.
00:53:28.703 --> 00:53:30.643 OK. And then copy that name.
00:53:33.043 --> 00:53:34.333 And scroll back down to where we were.
00:53:37.583 --> 00:53:41.063 And replace that temp pricing range on 1/26 with that new
00:53:41.063 --> 00:53:41.363 name.
00:53:42.603 --> 00:53:45.449 OK. And then the boost instead of search boost pricing ranges
00:53:45.449 --> 00:53:47.193 is gonna be searchboost credit limit?
00:53:52.823 --> 00:53:54.163 And then instead of the.
00:53:57.283 --> 00:54:01.946 Uh pricing to index as we want to. The P dot lot dot starting
00:54:01.946 --> 00:54:02.473 amount.
00:54:04.013 --> 00:54:05.063 So line 128.
00:54:09.253 --> 00:54:10.403 And what was the value again?
00:54:11.163 --> 00:54:13.933 It was P dot lot dot starting amount.
00:54:16.253 --> 00:54:17.123 For starting price.
00:54:20.093 --> 00:54:22.701 OK. And then it may be flattened out of the main model, so try
00:54:22.701 --> 00:54:23.653 try taking the lot out.
00:54:29.043 --> 00:54:30.513 OK, where did that end up being?
00:54:33.603 --> 00:54:36.162 Uh, OK, so it's doing it as indexable model, scroll to the
00:54:36.162 --> 00:54:36.813 very top again.
00:54:39.083 --> 00:54:43.143 We have a case right, a type value. So we have the.
00:54:44.623 --> 00:54:47.644 Was it the search for it was the index model, so T index model is
00:54:47.644 --> 00:54:50.390 an indexable model based on line 17 go to the definition of
00:54:50.390 --> 00:54:52.633 indexable model based by control clicking on it.
00:54:54.183 --> 00:54:56.193 So that's the that's the type when you want the thing that
00:54:56.193 --> 00:54:57.453 it's inheriting. Yeah, there you go.
00:54:59.163 --> 00:55:02.539 And then Scroll down a little, is there a section here that's
00:55:02.539 --> 00:55:03.683 for lot specifically?
00:55:05.293 --> 00:55:06.083 Looks like no.
00:55:07.133 --> 00:55:09.763 Umm. OK then let's go into the product section.
00:55:14.543 --> 00:55:17.011 So there's the has products. Where did we store that on the
00:55:17.011 --> 00:55:18.863 indexable model or did we not do that there?
00:55:22.333 --> 00:55:23.883 Uh, let's go ahead and just add.
00:55:26.523 --> 00:55:29.963 On the base property section, no. Trying to think of a good
00:55:29.963 --> 00:55:31.053 spot to stick this.
00:55:33.163 --> 00:55:34.583 I guess in the pricing section.
00:55:36.923 --> 00:55:39.219 Yeah. So let's do instead of pricing to indexes, as we're
00:55:39.219 --> 00:55:41.635 gonna add a second line. So you can copy that line for right
00:55:41.635 --> 00:55:41.793 now.
00:55:43.683 --> 00:55:46.083 I'm going to add another one. That is the you'll want the
00:55:46.083 --> 00:55:48.483 comment too, because you're gonna have to add the comment
00:55:48.483 --> 00:55:48.773 anyway.
00:55:56.353 --> 00:56:00.063 OK, so the this one, we're gonna call it a starting price.
00:56:03.943 --> 00:56:05.133 And we're gonna make it nullable.
00:56:08.683 --> 00:56:10.716 The question Mark has to be after the decimal, not the
00:56:10.716 --> 00:56:11.233 property name.
00:56:10.903 --> 00:56:11.593 But yeah.
00:56:14.173 --> 00:56:16.506 There we go and then change the comments to reflect that you
00:56:16.506 --> 00:56:18.763 were saying starting price instead of pricing to index as.
00:56:30.893 --> 00:56:33.905 OK, so now we have our property here. If it's in store it too
00:56:33.905 --> 00:56:37.015 and I believe the automaker is gonna map it onto this spot from
00:56:37.015 --> 00:56:39.784 the other side, from our dump reader. So back to the the
00:56:39.784 --> 00:56:41.533 pricing, the the credit limit file.
00:56:42.713 --> 00:56:45.637 And it should recognize that that five replies there now. So
00:56:45.637 --> 00:56:47.603 if we scroll back down to where it's at.
00:56:48.513 --> 00:56:50.393 Now it recognizes the P dot starting price.
00:56:51.153 --> 00:56:55.293 OK. So then we have a the field starting price must be less than
00:56:55.293 --> 00:56:59.242 and instead of using a config value, we're gonna put past the
00:56:59.242 --> 00:57:00.643 form dot credit limit.
00:57:03.053 --> 00:57:06.602 So line 129 we're replacing that config value with form dot
00:57:06.602 --> 00:57:07.963 credit limit dot value.
00:57:15.153 --> 00:57:17.225 And then the relationship is that it must be within that
00:57:17.225 --> 00:57:17.443 range.
00:57:19.603 --> 00:57:21.063 Mouse over it. What's it complaining about?
00:57:25.493 --> 00:57:28.225 Cannot convert. Could change it from decimal to double. OK, so
00:57:28.225 --> 00:57:29.223 just cast it to double.
00:57:35.503 --> 00:57:38.521 That's easy enough for the for the thing run time to do so. OK,
00:57:38.521 --> 00:57:41.397 so now we have our query that's actually going to filter the
00:57:41.397 --> 00:57:44.462 information to what we wanted to do is gonna add it to a list of
00:57:44.462 --> 00:57:46.113 queries in there and send it back.
00:57:47.373 --> 00:57:50.508 In theory, what I would probably do is you know, if I wanted to
00:57:50.508 --> 00:57:53.300 take more effort on this, I would make it so that it was
00:57:53.300 --> 00:57:56.483 only one in the first place and we were trying to add a a range.
00:57:56.483 --> 00:57:59.422 But it's gonna be physically easier to apply it, especially
00:57:59.422 --> 00:58:02.312 with relationship to how the pricing one actually works in
00:58:02.312 --> 00:58:05.153 the other area with less refactoring of what we're having
00:58:05.153 --> 00:58:08.288 to do here. So we're gonna keep it like this, even though we're
00:58:08.288 --> 00:58:11.374 only adding ever adding one and just put it right there and it
00:58:11.374 --> 00:58:13.823 should be fine. So the next thing we wanna do is.
00:58:15.093 --> 00:58:19.843 On the create pricing range, lambdas we're gonna there.
00:58:21.243 --> 00:58:23.637 I don't think we're calling that function from from here. That
00:58:23.637 --> 00:58:26.031 was part of something that has been called on the other parts.
00:58:26.031 --> 00:58:28.425 But let's scroll up to the top and look for the functions that
00:58:28.425 --> 00:58:30.819 were missing and make sure that we're good. So like that first
00:58:30.819 --> 00:58:32.453 error state you can see in the scroll bar.
00:58:34.283 --> 00:58:37.445 Search for you additional assignments for pricing ranges.
00:58:37.445 --> 00:58:40.553 So instead of four pricing ranges, do four credit limit.
00:58:46.753 --> 00:58:48.033 OK. And then?
00:58:49.313 --> 00:58:52.220 We really don't need an aggregation on here, so
00:58:52.220 --> 00:58:55.673 honestly, let's just make this function like do nothing.
00:58:57.993 --> 00:59:00.093 So not this one. You scrolled past the one that we were in.
00:59:01.323 --> 00:59:04.703 Go back up. Yeah. So this for this one.
00:59:05.693 --> 00:59:08.064 Let's let's make sure that this function is centered into the
00:59:08.064 --> 00:59:10.283 view, not not the top of it being the center of the view.
00:59:11.683 --> 00:59:14.084 There you go. OK, so all this stuff that we're doing in here
00:59:14.084 --> 00:59:16.564 for like the model, the pricing ranges that we would give back
00:59:16.564 --> 00:59:18.925 for credit limits and stuff, let's let's we don't need that
00:59:18.925 --> 00:59:21.523 for the front end. So let's take all of that out of this function
00:59:21.523 --> 00:59:23.373 and then write a comment that says do nothing.
00:59:26.143 --> 00:59:28.880 So it's very intended in pointed stating that you know we're
00:59:28.880 --> 00:59:31.393 doing nothing here and you'll have to have a capital D.
00:59:33.423 --> 00:59:34.823 Comments should start with a capital letter.
00:59:37.383 --> 00:59:40.244 OK, so now our function here is gonna. Basically is is
00:59:40.244 --> 00:59:43.417 intentionally showing is that we're doing nothing. We're not
00:59:43.417 --> 00:59:46.695 adding anything in for the view model to come back with or for
00:59:46.695 --> 00:59:49.608 that stuff. And then the aggregations here I believe is
00:59:49.608 --> 00:59:52.625 the same thing. This is the aggregations to create a tree
00:59:52.625 --> 00:59:55.746 for our or our list for our filter sidebar. We're not doing
00:59:55.746 --> 00:59:58.919 that for these guys. So instead of all of this stuff, you're
00:59:58.919 --> 01:00:01.937 gonna trash everything except that last line that has the
01:00:01.937 --> 01:00:05.214 return return query. Yep. Get rid of all that, and then you're
01:00:05.214 --> 01:00:07.763 gonna have a comment again that says do nothing.
01:00:11.143 --> 01:00:13.957 And then we're gonna rename it for to say instead of four
01:00:13.957 --> 01:00:16.383 pricing ranges. It's gonna say four credit limit.
01:00:17.353 --> 01:00:19.323 And it will adjust the comment as well to match it.
01:00:24.213 --> 01:00:26.363 And did we adjust the comment on the previous function?
01:00:28.713 --> 01:00:29.643 If you scroll up a notch.
01:00:31.483 --> 01:00:34.747 Yeah. So instead of four pricing ranges on 53, it'll be four
01:00:34.747 --> 01:00:35.443 credit limit.
01:00:43.373 --> 01:00:46.020 OK, so let's Scroll down now we only have 1 error left. What's
01:00:46.020 --> 01:00:48.331 the last error? It's probably just that is a duplicate
01:00:48.331 --> 01:00:51.062 function. We're no longer having this function, so we don't need
01:00:51.062 --> 01:00:53.456 it. Let's just trash the function itself, so collapse it
01:00:53.456 --> 01:00:55.053 online 100 and then delete the whole.
01:01:03.183 --> 01:01:06.889 There we go. OK, now we have the modifications that the the, the
01:01:06.889 --> 01:01:10.195 the core code around what we would need to do to make the
01:01:10.195 --> 01:01:13.787 modifications. Now we need to make sure that the query part of
01:01:13.787 --> 01:01:17.322 it actually calls this so that it appends it to the query. So
01:01:17.322 --> 01:01:20.514 to get to that we can use the pricing range as one as a
01:01:20.514 --> 01:01:23.593 reference. So go open the pricing ranges file that's.
01:01:24.643 --> 01:01:26.743 That's over there, so bods dot pricing ranges.
01:01:30.803 --> 01:01:33.779 I'm sorry, this is the the the config side. We want the other
01:01:33.779 --> 01:01:36.419 side that's not the config folder, so scroll up in the
01:01:36.419 --> 01:01:39.443 solution Explorer and it's the one that pricing ranges in that
01:01:39.443 --> 01:01:41.123 folder from there. Yeah, that one.
01:01:41.303 --> 01:01:42.323 This get hurt here.
01:01:42.663 --> 01:01:46.564 Yeah. So if you right click the pricing ranges query
01:01:46.564 --> 01:01:47.963 modification on 31.
01:01:49.273 --> 01:01:52.651 And save or actually you got the three reference you have. You
01:01:52.651 --> 01:01:55.653 have code lens on so you have 3 references right there.
01:01:56.393 --> 01:01:58.673 Between 30 and 31, yeah. Click on that.
01:01:59.923 --> 01:02:02.774 And then we wanna go to each of those three spots in turn and
01:02:02.774 --> 01:02:05.671 append this stuff. Now we could see the first one is auctions,
01:02:05.671 --> 01:02:08.200 the second one is lots. Technically I would do that to
01:02:08.200 --> 01:02:11.006 those things, but we're doing them to them right now because
01:02:11.006 --> 01:02:13.857 of you know, we're just trying to do this quick and dirty and
01:02:13.857 --> 01:02:16.754 we're almost out of time anyway. So let's just go to the third
01:02:16.754 --> 01:02:19.605 one, which is the product one, and that's the one we're gonna
01:02:19.605 --> 01:02:20.663 modify and add this to.
01:02:22.053 --> 01:02:24.483 So we double click that one copy and paste that line.
01:02:28.953 --> 01:02:30.623 Or you could press control D to duplicate.
01:02:33.033 --> 01:02:35.600 And in Visual Studio and in Visual Studio code, you don't
01:02:35.600 --> 01:02:38.255 have to select the line to copy and paste it, just get your
01:02:38.255 --> 01:02:40.821 cursor on the line and then control C Control V and we'll
01:02:40.821 --> 01:02:42.813 just duplicate the line really fast as well.
01:02:44.033 --> 01:02:44.483 OK.
01:02:44.653 --> 01:02:47.397 Believe you copied it and on and depended it to the end of the
01:02:47.397 --> 01:02:48.443 previous line currently.
01:02:49.163 --> 01:02:51.453 So you need to go over and add a carriage returns, so it'll.
01:02:52.253 --> 01:02:53.063 Put it to the next line.
01:02:53.873 --> 01:02:55.783 Yeah, I just, uh, copied it.
01:02:54.953 --> 01:02:56.795 Or you can delete it and paste it again. Whatever you're gonna
01:02:56.795 --> 01:02:56.883 do.
01:02:58.363 --> 01:03:01.179 OK. So pricing ranges, query modification on that second
01:03:01.179 --> 01:03:04.193 line, we're gonna change to credit limit query modification.
01:03:11.933 --> 01:03:13.923 And did we call it starting price credit limit?
01:03:15.203 --> 01:03:17.525 Or credit limit starting price. What did we fully call that
01:03:17.525 --> 01:03:17.873 function?
01:03:26.923 --> 01:03:27.743 That's not it.
01:03:27.513 --> 01:03:29.758 We can jump over back into the file and look at it so we can
01:03:29.758 --> 01:03:30.273 find it again.
01:03:31.423 --> 01:03:33.563 Or impressed credit limit, I do believe.
01:03:34.173 --> 01:03:36.503 It's 11. Further over. You're look at the price range is fine.
01:03:36.503 --> 01:03:37.613 We need the credit limit file.
01:03:39.553 --> 01:03:41.755 Uh, that's the config settings. Let's just close that file for
01:03:41.755 --> 01:03:42.943 right now so it's out of the way.
01:03:45.143 --> 01:03:45.653 OK.
01:03:46.883 --> 01:03:48.203 It's all the way on the right.
01:03:47.373 --> 01:03:49.493 I think it's the last time in the view, yeah.
01:03:49.443 --> 01:03:50.503 Yeah, all the way in there. I.
01:03:51.733 --> 01:03:52.653 Overweight the right.
01:03:52.923 --> 01:03:53.153 Yeah.
01:03:54.193 --> 01:03:55.743 Yep, and then scroll the top.
01:03:59.063 --> 01:04:00.793 Setting price credit limit yet?
01:03:59.373 --> 01:04:01.759 Starting phrase credit limit query modification. That's the
01:04:01.759 --> 01:04:04.146 full name we want, so you might as well just copy that name
01:04:04.146 --> 01:04:06.413 right there by double click copy, and then let's go back
01:04:06.413 --> 01:04:08.243 over to the file that we were trying to edit.
01:04:07.433 --> 01:04:09.653 Tim had that one down. He remembered that.
01:04:11.173 --> 01:04:11.763 Nice.
01:04:12.473 --> 01:04:13.703 Switch back over to search module.
01:04:12.853 --> 01:04:13.743 And attention fun.
01:04:16.663 --> 01:04:19.037 OK. And then just double click and paste it so that it replaces
01:04:19.037 --> 01:04:21.410 the thing and then the setting value, that's all the way on the
01:04:21.410 --> 01:04:21.633 right.
01:04:24.993 --> 01:04:27.422 So squirrel, right? Yeah. Instead of surprising ranges
01:04:27.422 --> 01:04:29.233 enabled, we want credit limited enabled.
01:04:36.223 --> 01:04:38.716 OK, that's not there. So we need to go to where like the
01:04:38.716 --> 01:04:41.515 searching price ranges enabled is. So like control click on the
01:04:41.515 --> 01:04:41.953 one above.
01:04:44.243 --> 01:04:46.645 I don't know if they're on the same file. If you're in separate
01:04:46.645 --> 01:04:49.009 mod files. This is for pricing ranges, so it's a mod file. Use
01:04:49.009 --> 01:04:51.373 the double arrow in the solution explorer to jump to where the
01:04:51.373 --> 01:04:51.673 file is.
01:04:52.833 --> 01:04:56.183 So we're just confirming that it's in that same spot. OK. Yep.
01:04:56.183 --> 01:04:59.213 We have our starting price credit limit file already. So
01:04:59.213 --> 01:05:01.553 just copy this this property from 13 to 21.
01:05:03.553 --> 01:05:06.395 And then we're going to go over the starting price credit limit
01:05:06.395 --> 01:05:08.793 config mod file, and we're gonna add it into the top.
01:05:11.953 --> 01:05:12.143 Yep.
01:05:13.663 --> 01:05:16.243 Black line between and. Then instead of pricing ranges,
01:05:16.243 --> 01:05:18.824 you're going to say, uh, starting price credit limit or
01:05:18.824 --> 01:05:19.653 just credit limit.
01:05:23.383 --> 01:05:26.990 And then you're going to change the. The setting is key to, say
01:05:26.990 --> 01:05:27.723 credit limit.
01:05:32.583 --> 01:05:34.463 And then you could save and close this file, because I think
01:05:34.463 --> 01:05:35.233 we have to open it again.
01:05:39.013 --> 01:05:40.670 And you can close this file because we're not gonna mess
01:05:40.670 --> 01:05:40.903 with it.
01:05:43.223 --> 01:05:46.584 Control F4 is the default hotkey to close that a file in Visual
01:05:46.584 --> 01:05:49.734 Studio OK, Scroll back to the left. OK, so now we have that
01:05:49.734 --> 01:05:53.042 thing in there, so this part's gonna be handled. So let's save
01:05:53.042 --> 01:05:55.983 the file and then switch back over to the credit limit.
01:05:56.773 --> 01:05:59.823 Uh CS file, the one that's at the at the end.
01:06:01.823 --> 01:06:04.573 Do enable and ignore future errors on that yellow bar.
01:06:05.493 --> 01:06:06.503 Kind of brown, but whatever.
01:06:07.783 --> 01:06:08.353 At the top.
01:06:09.273 --> 01:06:09.903 Topic a screen.
01:06:10.743 --> 01:06:11.443 Ah, OK.
01:06:12.043 --> 01:06:13.673 Enable and ignore future errors.
01:06:16.333 --> 01:06:17.093 How to shut up?
01:06:18.033 --> 01:06:19.123 OK so.
01:06:19.443 --> 01:06:23.232 Uh, Scroll down in this or actually hit control M control
01:06:23.232 --> 01:06:23.363 O.
01:06:27.023 --> 01:06:29.973 You gotta do it fast. Him as in the as in monkey.
01:06:34.073 --> 01:06:36.657 OK, that collapsed all so we could see just the the function
01:06:36.657 --> 01:06:39.072 headers. OK, so we have the starting price credit limit,
01:06:39.072 --> 01:06:41.402 search view, additional assignments for credit limits.
01:06:41.402 --> 01:06:44.072 That's when we're gonna need to find and then the aggregations
01:06:44.072 --> 01:06:46.486 and stuff that's inside the file. I think what we really
01:06:46.486 --> 01:06:48.986 need to do is focus on the search form base to just scroll
01:06:48.986 --> 01:06:51.486 through it and find all the spots where it's pending stuff
01:06:51.486 --> 01:06:54.155 because Republican find pricing ranges in there multiple times
01:06:54.155 --> 01:06:56.782 and just do it instead of have to jump back and forth between
01:06:56.782 --> 01:06:59.451 files over and over. So go back to search for and base dot CS,
01:06:59.451 --> 01:07:01.993 which is the file left with the one that you've got active.
01:07:03.013 --> 01:07:03.983 Score the top.
01:07:05.443 --> 01:07:07.529 This search form close the search form. We don't need that
01:07:07.529 --> 01:07:07.883 one right.
01:07:11.313 --> 01:07:13.613 Close the suggest module. We don't need that right now.
01:07:16.863 --> 01:07:18.393 Where's that? I'll learn.
01:07:17.373 --> 01:07:19.918 It's you, it's. It's two to the right of the of the file that
01:07:19.918 --> 01:07:20.493 you have open.
01:07:21.933 --> 01:07:24.464 Close that one case. You don't need to open Ohly search
01:07:24.464 --> 01:07:26.633 service. close that one. We don't need to open.
01:07:29.503 --> 01:07:31.503 The config file close that we don't need it open.
01:07:35.103 --> 01:07:36.613 The provider will keep for a second.
01:07:39.283 --> 01:07:41.975 Where was the file that we were editing a moment ago that we
01:07:41.975 --> 01:07:43.873 just added that into the thing to call it?
01:07:46.643 --> 01:07:48.503 It's got to be one of the files that we have open left.
01:07:56.393 --> 01:07:58.450 That's just start clicking through. We gotta. We gotta.
01:07:58.450 --> 01:08:00.765 We're out of time. We gotta. We gotta move through the list of
01:08:00.765 --> 01:08:02.933 what we got here. So it's not this one. So close this one.
01:08:07.063 --> 01:08:09.333 It's not this one to close that one.
01:08:11.313 --> 01:08:13.203 It's not that one so close that one.
01:08:14.963 --> 01:08:16.753 Is it the elastic searching provider at the end?
01:08:21.423 --> 01:08:23.083 No, this one is know what it's on it.
01:08:27.043 --> 01:08:29.044 It's not this one, so let's close this one. I think we ended
01:08:29.044 --> 01:08:30.193 up closing the one that we needed.
01:08:31.993 --> 01:08:35.125 So do you do the reference on this one cause is gonna open the
01:08:35.125 --> 01:08:38.307 file for us cause and we have a reference to it now. So between
01:08:38.307 --> 01:08:39.103 24 and 30 there.
01:08:39.853 --> 01:08:41.423 It has the reference thing on code lens.
01:08:46.103 --> 01:08:48.804 Double click that so we can open the correct file. Pin this one
01:08:48.804 --> 01:08:49.733 open so it stays open.
01:08:50.453 --> 01:08:53.043 This is the one we care about. School or the top of this file.
01:08:53.723 --> 01:08:55.978 And we're going to scroll through it slowly until we find
01:08:55.978 --> 01:08:57.533 the spots that we would need to modify.
01:08:59.743 --> 01:09:02.863 So there's the name region. OK, keep going.
01:09:05.313 --> 01:09:05.953 Keep going.
01:09:07.383 --> 01:09:08.053 Keep going.
01:09:09.323 --> 01:09:09.993 Keep going.
01:09:11.473 --> 01:09:12.193 Keep going.
01:09:13.793 --> 01:09:14.503 Keep going.
01:09:16.343 --> 01:09:17.673 OK. So it's gonna be around here.
01:09:19.753 --> 01:09:22.258 OK. So that's where we added that one. So can you keep
01:09:22.258 --> 01:09:22.713 scrolling?
01:09:25.513 --> 01:09:26.083 Keep going.
01:09:27.713 --> 01:09:30.704 Additional assignments. OK, they're line 332. Clone that
01:09:30.704 --> 01:09:33.958 line and then replace the stuff from pricing ranges to credit
01:09:33.958 --> 01:09:34.273 limit.
01:09:36.483 --> 01:09:38.973 So remember control D to duplicate a line.
01:09:48.273 --> 01:09:49.863 OK. And then the setting at the end?
01:09:50.603 --> 01:09:52.633 Is going to be that same credit limit thing.
01:09:58.403 --> 01:09:59.953 OK, so that creates gets that one.
01:10:00.793 --> 01:10:02.873 And then go back to the left and then start scrolling down again.
01:10:03.853 --> 01:10:06.195 OK. We don't care what the brand names one. OK. And then the
01:10:06.195 --> 01:10:08.383 brand names when there. OK. So that one that's all done.
01:10:10.183 --> 01:10:13.151 I don't know if there's anywhere else we need to actually mess
01:10:13.151 --> 01:10:16.119 with right now, but since we're out of time, basically, that's
01:10:16.119 --> 01:10:19.087 it. That's gonna build it and run it. And that should actually
01:10:19.087 --> 01:10:22.055 apply it when we do an index and then run a search with it. As
01:10:22.055 --> 01:10:24.693 far as the back end is concerned, we still need to add.
01:10:25.813 --> 01:10:29.528 The data into the pricing factory context probably to get
01:10:29.528 --> 01:10:33.628 the hook for filling that form in automatically like we do with
01:10:33.628 --> 01:10:34.653 the roles piece.
01:10:37.203 --> 01:10:40.052 So for anyone who could stay on long enough, I can. I can keep
01:10:40.052 --> 01:10:42.811 going on this a couple more minutes and then and and call it
01:10:42.811 --> 01:10:45.525 a victory. Or if we want to continue this next week and and
01:10:45.525 --> 01:10:48.284 do the last, you know, 1520 minutes of what we wanna do with
01:10:48.284 --> 01:10:50.003 what do we wanna handle that Brendan.
01:10:52.693 --> 01:10:56.835 Uh, if we're at time, nobody's obligated to stick around. And
01:10:56.835 --> 01:11:00.709 if you guys need to drop, which I do, I've got plans this
01:11:00.709 --> 01:11:03.983 afternoon. And so I'll be. I'll be dropping but.
01:11:05.823 --> 01:11:08.207 But I think it looks sounds like a pretty pretty close to getting
01:11:08.207 --> 01:11:10.266 done, so we should be able to finish this up next week I
01:11:10.266 --> 01:11:10.483 think.
01:11:10.293 --> 01:11:13.150 Yeah, since this is a server side only affect like we don't
01:11:13.150 --> 01:11:16.197 have to build a front end UI for it, there's just the front end
01:11:16.197 --> 01:11:18.958 or the the back end part to assign that that credit limit
01:11:18.958 --> 01:11:19.863 value to deal with.
01:11:19.333 --> 01:11:19.593 Right.
01:11:21.463 --> 01:11:24.632 So let's go ahead and I'll. I'll keep going with him here unless
01:11:24.632 --> 01:11:25.753 you need to leave Nick.
01:11:26.653 --> 01:11:27.493 No, I can stay.
01:11:28.133 --> 01:11:31.585 OK. And anybody else, nobody's obligated to stick around. It is
01:11:28.343 --> 01:11:29.733 OK, so let's go.
01:11:31.585 --> 01:11:35.038 end of the day. So if you guys have, you know, if you guys need
01:11:35.038 --> 01:11:36.063 to drop, feel free.
01:11:36.743 --> 01:11:39.013 Uh, I am. I am going to lead by example.
01:11:37.003 --> 01:11:37.213 Yeah.
01:11:40.093 --> 01:11:43.603 So I will uh, I will talk to you next week.
01:11:41.693 --> 01:11:42.113 OK.
01:11:44.853 --> 01:11:45.943 You, Brent, have a good weekend.
01:11:44.873 --> 01:11:45.093 Yeah.
01:11:46.193 --> 01:11:46.803 Yep, see ya.
01:11:49.553 --> 01:11:52.543 OK, Nick, the go ahead and.
01:11:55.873 --> 01:11:56.973 You control T.
01:12:00.883 --> 01:12:04.698 And inside there do pricing factory context model as one
01:12:04.698 --> 01:12:05.033 word.
01:12:06.933 --> 01:12:08.053 Camel case that if can.
01:12:13.723 --> 01:12:14.563 Context model.
01:12:14.173 --> 01:12:15.173 Context model.
01:12:15.953 --> 01:12:16.473 Yes.
01:12:17.693 --> 01:12:18.123 That.
01:12:18.993 --> 01:12:20.723 There we go. That's the class I was looking for.
01:12:21.583 --> 01:12:24.813 OK, so press enter to make it stick there.
01:12:26.413 --> 01:12:28.623 OK, now Scroll down in this until you see the word roll.
01:12:32.103 --> 01:12:33.073 Or user roles.
01:12:34.423 --> 01:12:38.244 That's it. Go to the references for user roles. You scroll past
01:12:38.244 --> 01:12:38.423 it.
01:12:40.363 --> 01:12:40.793 Up.
01:12:41.783 --> 01:12:42.173 There we go.
01:12:43.363 --> 01:12:45.400 It's still building the references, but just click there
01:12:45.400 --> 01:12:46.293 so that it can open that.
01:12:49.823 --> 01:12:52.293 Can I control click into this or I had to wait for this to load?
01:12:51.953 --> 01:12:55.279 No, just I. If it's not letting you click on it directly the the
01:12:55.279 --> 01:12:58.555 the code lens part, then you'll have to wait for it to load and
01:12:58.555 --> 01:12:59.783 then we can click on it.
01:13:01.213 --> 01:13:01.663 There we go.
01:13:01.293 --> 01:13:01.773 Gotcha.
01:13:02.523 --> 01:13:03.593 So then click on it now.
01:13:04.553 --> 01:13:07.208 And we're going to look through this list for where that gets
01:13:07.208 --> 01:13:07.593 assigned.
01:13:08.313 --> 01:13:09.813 Uh in the thing?
01:13:12.763 --> 01:13:15.679 OK. So that's in the pricing factor context model, it's just
01:13:15.679 --> 01:13:18.595 it's just new assigning it in with that piece and invalid by
01:13:18.595 --> 01:13:19.743 user role, the discount.
01:13:22.993 --> 01:13:27.084 So what we want here is we want to another property just like
01:13:27.084 --> 01:13:31.043 user roles on this on this object that is for credit limit.
01:13:32.393 --> 01:13:35.580 So go ahead and add another property that is credit limit
01:13:35.580 --> 01:13:37.283 and there's a decimal nullable.
01:13:38.863 --> 01:13:40.893 OK. Are these in any particular order?
01:13:42.113 --> 01:13:43.343 Now just put it there, it's fine.
01:13:45.243 --> 01:13:47.113 I'll move it if I need to move it on the PR.
01:13:50.123 --> 01:13:52.063 And then instead of list string it's going to be decimal.
01:13:52.873 --> 01:13:53.813 And still gonna be knowable.
01:13:58.743 --> 01:14:00.403 OK, now copy that line.
01:14:01.343 --> 01:14:04.278 So control C to just copy it, don't you? You don't need to
01:14:04.278 --> 01:14:05.323 select it to copy it.
01:14:06.333 --> 01:14:06.713 Yeah.
01:14:06.793 --> 01:14:09.757 The copying just hitting the cursor on the line press control
01:14:09.757 --> 01:14:12.673 C it is now in your clipboard and then scroll up to the top.
01:14:14.343 --> 01:14:16.543 Control click the interface that it's inheriting.
01:14:20.213 --> 01:14:23.242 And then find the user roles property just like that one
01:14:23.242 --> 01:14:23.773 before it.
01:14:25.043 --> 01:14:28.508 And then after that one pays there. So press a new line and
01:14:28.508 --> 01:14:29.143 then paste.
01:14:30.773 --> 01:14:32.690 And see how it dropped it in there. Get rid of the extra
01:14:32.690 --> 01:14:33.363 blank line below it.
01:14:34.583 --> 01:14:37.847 Grab the comment from the user roles above it. Use it to to
01:14:37.847 --> 01:14:39.153 populate that one below.
01:14:43.333 --> 01:14:44.953 And then you could take the public off of it.
01:14:51.073 --> 01:14:52.793 Instead of user roles, it would be the credit limit.
01:15:02.403 --> 01:15:03.633 OK, so we saved that.
01:15:05.113 --> 01:15:08.656 Now our pricing factory context for sure has the piece on it
01:15:08.656 --> 01:15:09.643 that we need the.
01:15:09.723 --> 01:15:13.637 The the part that's gonna fill it in if we go back to that
01:15:13.637 --> 01:15:17.153 references on the user roles that's on the concrete.
01:15:18.203 --> 01:15:18.813 The class.
01:15:22.273 --> 01:15:25.233 So the references on user roles.
01:15:26.583 --> 01:15:27.913 It's calculating it again.
01:15:36.273 --> 01:15:37.413 Yeah. To bring that up.
01:15:56.893 --> 01:15:59.469 Go ahead and click the little button on the top right of that
01:15:59.469 --> 01:16:00.923 thing. That puts it to the window.
01:16:08.713 --> 01:16:09.703 There we go. OK.
01:16:11.543 --> 01:16:14.093 So collapse the first one.
01:16:16.653 --> 01:16:17.633 What's the 2nd?
01:16:19.463 --> 01:16:22.573 Collapse or we want to make sure I can read that part, collapse
01:16:22.573 --> 01:16:23.253 the third one.
01:16:26.263 --> 01:16:27.523 Uh collapse the 4th one.
01:16:31.123 --> 01:16:33.993 Uh collapse? The fifth one.
01:16:37.223 --> 01:16:38.583 Collapse the 6th one.
01:16:40.863 --> 01:16:42.083 We'll watch the.
01:16:45.673 --> 01:16:47.063 Or double click on that next one.
01:16:47.773 --> 01:16:48.773 So where it says 120?
01:16:53.243 --> 01:16:55.783 Racing factory context and passes in the roles.
01:16:54.053 --> 01:16:54.483 Yeah.
01:16:58.263 --> 01:17:01.207 So we need to add a property to pass in. No, we're doing it to
01:17:01.207 --> 01:17:03.777 the form. We just need to transfer to the form. OK, so
01:17:03.777 --> 01:17:05.553 then we don't need to do it to these.
01:17:07.213 --> 01:17:10.743 So back in the list the the code lens list down there.
01:17:11.583 --> 01:17:14.430 So collapse that one and the ones that come after it that are
01:17:14.430 --> 01:17:16.083 the same thing over and over again.
01:17:17.283 --> 01:17:18.673 And make that part of the window taller.
01:17:22.153 --> 01:17:24.743 There we go. OK. So we don't care about any of those. So
01:17:24.743 --> 01:17:27.514 collapse all of those until we get down to the one that says
01:17:27.514 --> 01:17:27.923 services.
01:17:33.713 --> 01:17:35.793 OK. So that one, we want that 983.
01:17:38.953 --> 01:17:42.158 And then what we're going to do here is we're gonna focus on the
01:17:42.158 --> 01:17:45.364 code. The account has the credit limit. So inside the account is
01:17:45.364 --> 01:17:48.323 not null part where it has like the account ID, account ID,
01:17:48.323 --> 01:17:49.753 account type ID, price point.
01:17:52.383 --> 01:17:53.553 We thought scroll back down.
01:17:55.583 --> 01:17:59.628 So but after line 995 add pricing factory context dot
01:17:59.628 --> 01:18:03.223 credit limit equal to account dot credit limit.
01:18:06.213 --> 01:18:07.213 So after that line.
01:18:11.863 --> 01:18:12.333 OK.
01:18:13.563 --> 01:18:16.528 Pricing factory contacts dot credit limit equal to account
01:18:16.528 --> 01:18:17.383 dot credit limit.
01:18:19.523 --> 01:18:21.513 And you say that just one more time.
01:18:22.663 --> 01:18:26.002 So just like the properties above it, you gotta have a lower
01:18:26.002 --> 01:18:28.793 case variable instance of pricing factory context.
01:18:30.013 --> 01:18:30.883 Yeah. OK.
01:18:31.103 --> 01:18:32.783 So you want that you're doing that again?
01:18:33.613 --> 01:18:34.953 Dot credit limit.
01:18:37.113 --> 01:18:37.943 Equal to.
01:18:39.263 --> 01:18:40.683 Account dot credit limit.
01:18:41.753 --> 01:18:43.743 Because that's where the that's where the limit comes from.
01:18:45.203 --> 01:18:46.103 It might just be credit.
01:18:49.583 --> 01:18:52.890 Yeah, there's our decimal that's going to give us the value that
01:18:52.890 --> 01:18:56.095 we want. So now that whenever the pricing factory context gets
01:18:56.095 --> 01:18:59.097 built, which is anytime and get these things get run, it's
01:18:59.097 --> 01:19:01.946 gonna, it's gonna pull that property out and pull it in
01:19:01.946 --> 01:19:04.897 there. Now we do need to modify the query for the git for
01:19:04.897 --> 01:19:06.423 pricing by user ID. So on 986.
01:19:07.093 --> 01:19:10.837 You're going to click on the the the definition of get for
01:19:10.837 --> 01:19:11.853 pricing user ID.
01:19:13.933 --> 01:19:16.669 And then you're going to control F-12 so that you go to the
01:19:16.669 --> 01:19:17.353 implementation.
01:19:20.343 --> 01:19:22.814 There we go. OK, now Scroll down a little bit cuz we need to add
01:19:22.814 --> 01:19:25.095 the credit to this property on here cause it's not gonna be
01:19:25.095 --> 01:19:25.703 here by default.
01:19:27.193 --> 01:19:29.810 So in the query they're starting at 122, you see it's got account
01:19:29.810 --> 01:19:32.268 price points, the type ID, the custom keys, Scroll down so we
01:19:32.268 --> 01:19:33.973 can see that whole section of that select.
01:19:34.753 --> 01:19:38.363 OK, add right below type ID X dot credit.
01:19:40.363 --> 01:19:40.663 Comma.
01:19:43.663 --> 01:19:46.673 OK, now on that next select, that starts at 1:38. We need to
01:19:46.673 --> 01:19:47.413 edit there too.
01:19:48.393 --> 01:19:50.183 So credit equal to X dot credit.
01:19:53.443 --> 01:19:56.291 And you could tabs in it will take that whole thing. There we
01:19:56.291 --> 01:19:59.322 go. Perfect. Now Scroll down and just make sure we're not missing
01:19:59.322 --> 01:20:01.573 anything else in the dysfunction. Great. Perfect
01:20:01.573 --> 01:20:01.803 save.
01:20:03.713 --> 01:20:06.567 I think if you Scroll down to that next function this is get
01:20:06.567 --> 01:20:09.421 for pricing by username. It's gonna need that same stuff. So
01:20:09.421 --> 01:20:11.293 we wanna make sure we get in there too.
01:20:12.923 --> 01:20:16.132 So AX dot credit and then credit equal to X dot credit on that
01:20:16.132 --> 01:20:16.693 other part.
01:20:23.953 --> 01:20:26.603 Perfect. OK, Scroll down.
01:20:29.303 --> 01:20:32.977 OK, great. We don't need it for taxes. So save and close that
01:20:32.977 --> 01:20:33.273 file.
01:20:36.723 --> 01:20:39.073 OK, so we're back here. This thing's doing what we want.
01:20:41.003 --> 01:20:44.436 Save this file, but don't close it and then Scroll down inside
01:20:44.436 --> 01:20:45.853 the code lens black again.
01:20:50.063 --> 01:20:51.503 OK. And then?
01:20:52.193 --> 01:20:54.493 So like 1006, double click that one.
01:20:57.743 --> 01:21:00.018 We don't care about that. And then 1011 is the one that was
01:21:00.018 --> 01:21:02.179 right there. That's we don't care about that. So you can
01:21:02.179 --> 01:21:03.013 collapse that one now.
01:21:03.923 --> 01:21:06.694 And then we don't care about the two testing or the three testing
01:21:06.694 --> 01:21:08.163 ones that just collapse those two.
01:21:10.023 --> 01:21:12.373 OK, so we added the things that we need to add for this side.
01:21:13.443 --> 01:21:16.513 And now we need to go to the search form.
01:21:17.433 --> 01:21:19.971 As it gets brought in by the server and make sure that it
01:21:19.971 --> 01:21:22.640 passes that variable value from the pricing context onto the
01:21:22.640 --> 01:21:22.903 thing.
01:21:24.293 --> 01:21:25.903 Try to think of the best place to do that.
01:21:27.663 --> 01:21:30.381 And what we probably want to do is go to the service thing. So
01:21:30.381 --> 01:21:32.798 on your solution Explorer, collapse the base and config
01:21:32.798 --> 01:21:33.143 folders.
01:21:36.203 --> 01:21:39.457 And on the product one go to elestic searching service dot
01:21:39.457 --> 01:21:39.623 CS.
01:21:42.743 --> 01:21:44.513 Uh, do you control him? Control O.
01:21:48.103 --> 01:21:50.153 Gay Scroll down to where the handlers are.
01:21:53.533 --> 01:21:54.763 So we want the.
01:21:55.673 --> 01:21:58.622 Uh search product catalog with provider online one-on-one. So
01:21:58.622 --> 01:21:59.383 expand that one.
01:22:03.963 --> 01:22:07.567 OK, it builds up producing factory context for us. And then
01:22:07.567 --> 01:22:11.172 what we're gonna do is between 119 and 1:20, we're gonna go
01:22:11.172 --> 01:22:11.893 request dot.
01:22:13.273 --> 01:22:18.083 Credit limit or equal to pricing factory context dot credit.
01:22:21.103 --> 01:22:23.403 And that's how we pass it from that thing over to this.
01:22:28.933 --> 01:22:32.015 Yes, stat. So now we've passed it in there. And so when the
01:22:32.015 --> 01:22:34.993 product search gets run, it's going to have that limit in
01:22:34.993 --> 01:22:36.483 there and bring that part up.
01:22:38.093 --> 01:22:40.740 So I believe we've done everything we need to do for the
01:22:40.740 --> 01:22:43.665 back end and all of this stuff in order to make sure this runs
01:22:43.665 --> 01:22:46.265 what you would do is turn your app pools off, build the
01:22:46.265 --> 01:22:46.683 solution.
01:22:47.863 --> 01:22:48.673 And then.
01:22:51.073 --> 01:22:51.553 Uh.
01:22:54.153 --> 01:22:57.429 Turn it back on and then run an index through the scheduler or
01:22:57.429 --> 01:23:00.550 wait 15 minutes. It will do it automatically and then go to
01:23:00.550 --> 01:23:03.670 your store front and then run it and then anything that any
01:23:03.670 --> 01:23:06.738 product that had a that I starting price above your credit
01:23:06.738 --> 01:23:09.911 limit for your account that you're logged in as we should no
01:23:09.911 --> 01:23:12.823 longer show up for you because it will get blocked out.
01:23:13.663 --> 01:23:16.894 Umm, but that's it for time. If you wanna play with that, let me
01:23:16.894 --> 01:23:19.827 know if it worked or not. Go ahead, get a PR out for these
01:23:19.827 --> 01:23:23.008 changes and then we'll you might do a couple more tweaks to it.
01:23:23.008 --> 01:23:26.239 And now that we could do that in the browser, I might do that in
01:23:26.239 --> 01:23:29.073 the browser and play with it. But that's pretty much it.
01:23:30.533 --> 01:23:33.568 Yeah, real quick. I'm sorry. Can you give me those steps one by
01:23:33.568 --> 01:23:35.323 one? Again, I wanna write them down.
01:23:38.213 --> 01:23:40.777 Turn your app pools off that are pointing at your developed
01:23:40.777 --> 01:23:42.913 folder here where this, this instance of Seth is.
01:23:43.953 --> 01:23:45.133 Yeah, got that.
01:23:44.233 --> 01:23:45.523 For for IS.
01:23:46.653 --> 01:23:49.984 And build the solution so that it could take the updated value
01:23:49.984 --> 01:23:51.253 into the plugins folder.
01:23:51.893 --> 01:23:53.133 Turn your apples back on.
01:23:53.873 --> 01:23:54.933 Go to the scheduler.
01:23:55.983 --> 01:23:57.073 Run an index.
01:23:58.863 --> 01:24:01.084 If you don't want to do that yourself, you can wait 15
01:24:01.084 --> 01:24:03.467 minutes because that's the default time cycle for it to do
01:24:03.467 --> 01:24:04.033 it on its own.
01:24:05.443 --> 01:24:08.233 OK, I'm not actually sure how to run an index.
01:24:05.943 --> 01:24:06.553 And.
01:24:09.903 --> 01:24:12.286 It's one of the jobs that's available in the index or you
01:24:12.286 --> 01:24:14.833 can go to the admin and you can press the button in the admin
01:24:14.833 --> 01:24:17.256 under the product section to says index products and do it
01:24:17.256 --> 01:24:17.503 there.
01:24:18.603 --> 01:24:18.993 OK.
01:24:22.793 --> 01:24:23.373 10.
01:24:24.183 --> 01:24:28.232 Uh, you would go to the store front and if your account has a
01:24:28.232 --> 01:24:29.473 credit limit on it.
01:24:30.413 --> 01:24:32.947 Then anything that was above that credit limit for starting
01:24:32.947 --> 01:24:34.383 price would then be filtered out.
01:24:36.503 --> 01:24:40.050 You test that more specifically, you probably have to manipulate
01:24:40.050 --> 01:24:43.214 data on either account record and the starting price on a
01:24:43.214 --> 01:24:46.488 particular products, or or whether it's lot so that you can
01:24:46.488 --> 01:24:49.653 for sure make sure that it gets commented or blocked out.
01:24:50.963 --> 01:24:51.383 OK.
01:24:51.083 --> 01:24:53.568 And that kind of testing, I mean I would get with bread and Lyon
01:24:53.568 --> 01:24:55.823 on that so that he can walk you through that testing that.
01:24:57.543 --> 01:25:00.070 And then make your PR off of the branch, whatever you think it's
01:25:00.070 --> 01:25:00.303 ready.
01:25:01.463 --> 01:25:01.753 OK.
01:25:04.543 --> 01:25:06.245 And right now you're in developed. So obviously we
01:25:06.245 --> 01:25:08.348 change your branch first before you committing it, because you
01:25:08.348 --> 01:25:09.483 can't commit to develop directly.
01:25:11.493 --> 01:25:13.813 OK, got it. Thank you.
01:25:13.583 --> 01:25:14.383 OK, so that's everything.
01:25:17.173 --> 01:25:17.463 Cool.
01:25:18.353 --> 01:25:20.294 I guess I should have gone so long winded on some of those
01:25:20.294 --> 01:25:22.038 other explanations so we wouldn't have to go over on
01:25:22.038 --> 01:25:22.203 time.
01:25:24.493 --> 01:25:24.783 OK.
01:25:24.663 --> 01:25:25.533 Yeah, I.
01:25:26.533 --> 01:25:30.252 It was a little bit hard to follow the logic and everything
01:25:30.252 --> 01:25:34.094 cause as we were going through the code we were moving pretty
01:25:34.094 --> 01:25:37.999 fast and I definitely did not catch all of the terminology and
01:25:37.999 --> 01:25:38.743 process for.
01:25:38.143 --> 01:25:40.743 OK. Well the, the this was recorded. So you'll be able to
01:25:40.743 --> 01:25:43.388 come back and review it. And there's I, I don't think they
01:25:43.388 --> 01:25:44.643 did a transcript on it, but.
01:25:49.223 --> 01:25:51.908 Yeah, it looks like they didn't do the transcript, but they did
01:25:49.553 --> 01:25:50.123 Yeah, and.
01:25:51.908 --> 01:25:54.467 do a recording. So you'll be able to come back and do it and
01:25:54.467 --> 01:25:55.013 see it again.
01:25:55.473 --> 01:25:58.674 Yeah, and that recording just gets saved in the chat. The
01:25:58.674 --> 01:26:01.323 teams chat for whatever this meeting is called.
01:26:00.463 --> 01:26:00.713 Yeah.
01:26:02.963 --> 01:26:03.423 Yes.
01:26:03.243 --> 01:26:03.683 OK.
01:26:08.983 --> 01:26:12.649 So weekly Dev training, so this chat is persistent like every
01:26:12.649 --> 01:26:16.434 Friday, right? When we jump into this meeting every Friday, you
01:26:16.434 --> 01:26:17.853 can view this same chat.
01:26:18.613 --> 01:26:20.063 Or you can see it from your chats.
01:26:21.673 --> 01:26:25.306 OK. Could I like scroll backwards two months and see
01:26:24.573 --> 01:26:25.033 Yeah.
01:26:25.306 --> 01:26:26.403 training videos?
01:26:25.473 --> 01:26:28.145 Yes, you can scroll back grids and all that stuff in teams to
01:26:28.145 --> 01:26:29.093 to find older history.
01:26:29.723 --> 01:26:30.073 Cool.
01:26:29.943 --> 01:26:30.133 Yep.
01:26:38.343 --> 01:26:42.153 James, are we good to stop this recording?
01:26:42.793 --> 01:26:44.143 Yes, we are good to stop.
01:26:45.253 --> 01:26:47.896 So I'm stopping the recording and then I am going to balance
01:26:47.896 --> 01:26:50.626 because I have other calls I'm trying to do to go to go stuff.
01:26:50.626 --> 01:26:53.183 I gotta do my time logs with Caroline and then I work with
01:26:53.183 --> 01:26:55.263 Tim and I gotta get some food cause I'm starve.