Video from Paired Programming Session on 6/1/21 covering how to Run T4s for Schema Changes.
00:00:06.140 --> 00:00:08.499 OK, so real quick so go ahead
00:00:08.499 --> 00:00:10.826 and open up user lab results
00:00:10.826 --> 00:00:13.292 status on the right side and
00:00:13.292 --> 00:00:15.840 keep user lab results on left.
00:00:15.840 --> 00:00:18.160 So we're adding schema for
00:00:18.160 --> 00:00:20.480 lab results so each user.
00:00:20.480 --> 00:00:23.049 Can have lab results for a specific.
00:00:25.910 --> 00:00:29.318 Test and the test needs to have the
00:00:29.318 --> 00:00:32.259 lab results need to have a status.
00:00:32.260 --> 00:00:34.640 So for example, processing denied
00:00:34.640 --> 00:00:37.020 or rejected or whatever approved
00:00:37.099 --> 00:00:39.374 or processed or complete whatever
00:00:39.374 --> 00:00:41.649 terminology they want to use.
00:00:41.650 --> 00:00:43.906 They need to store the actual
00:00:43.906 --> 00:00:46.241 result of the status and the
00:00:46.241 --> 00:00:48.497 user whose lab results they are.
00:00:48.500 --> 00:00:50.748 Thinking that they may also need to store.
00:00:50.750 --> 00:00:52.430 Now that I'm thinking about it,
00:00:52.430 --> 00:00:54.432 they may also need to store some
00:00:54.432 --> 00:00:55.530 identifying information about the.
00:00:58.080 --> 00:01:01.909 The test, but I'm not totally sure.
00:01:01.910 --> 00:01:04.310 So we can revisit that, but anyway,
00:01:04.310 --> 00:01:07.334 so on the left side you can see the
00:01:07.334 --> 00:01:10.008 actual schema that we built for that.
00:01:10.010 --> 00:01:12.008 So he created the interface at
00:01:12.008 --> 00:01:14.508 the top I user lab results and
00:01:14.508 --> 00:01:17.049 it derives from my base which is.
00:01:17.050 --> 00:01:19.353 I base provides all the default out
00:01:19.353 --> 00:01:22.173 of the box stuff for every entity and
00:01:22.173 --> 00:01:24.790 stuff which is like ID custom key,
00:01:24.790 --> 00:01:26.555 Jason attributes created and updated
00:01:26.555 --> 00:01:28.660 dates and then also drives from.
00:01:28.660 --> 00:01:32.332 I have a status base which will help with.
00:01:32.340 --> 00:01:34.195 Any boilerplate code involving an
00:01:34.195 --> 00:01:36.580 entity that also has a status,
00:01:36.580 --> 00:01:39.452 and then the bottom we have the actual
00:01:39.452 --> 00:01:41.199 implementation of that interface,
00:01:41.200 --> 00:01:43.125 which again derives from base
00:01:43.125 --> 00:01:45.497 to populate all the the default
00:01:45.497 --> 00:01:47.735 schema for IDs and all that,
00:01:47.740 --> 00:01:51.676 and then we derive from the interface above.
00:01:51.680 --> 00:01:53.750 We have our status in there.
00:01:53.750 --> 00:01:56.774 The lab results and the user
00:01:56.774 --> 00:01:59.310 for whom the results are.
00:01:59.310 --> 00:02:00.192 And that's it.
00:02:00.192 --> 00:02:00.780 It's pretty.
00:02:00.780 --> 00:02:02.526 This is a pretty straightforward schema,
00:02:02.530 --> 00:02:04.448 but it is kind of interesting 'cause
00:02:04.448 --> 00:02:06.638 we have a couple of cool things.
00:02:06.640 --> 00:02:08.100 It's not just storing data,
00:02:08.100 --> 00:02:09.912 we also have a relationship to
00:02:09.912 --> 00:02:12.200 a user as well as to a status.
00:02:12.200 --> 00:02:14.576 So it's a little bit of a little
00:02:14.576 --> 00:02:16.010 bit of a fun one.
00:02:16.010 --> 00:02:16.355 Also,
00:02:16.355 --> 00:02:18.425 I will cover one really quick
00:02:18.425 --> 00:02:20.970 thing that I did not cover with
00:02:20.970 --> 00:02:23.124 with Josh that I just realized.
00:02:23.130 --> 00:02:25.314 Obviously all that I have a
00:02:25.314 --> 00:02:27.662 status base is doing is declaring
00:02:27.662 --> 00:02:30.104 2 fields status and status ID.
00:02:30.110 --> 00:02:32.438 So on paper you could just
00:02:32.438 --> 00:02:33.602 manually make those.
00:02:33.610 --> 00:02:36.312 The reason you would never do that
00:02:36.312 --> 00:02:39.001 is because I have a status base
00:02:39.001 --> 00:02:41.750 is actually used by the T fours,
00:02:41.750 --> 00:02:44.263 which will be the next thing we're
00:02:44.263 --> 00:02:45.881 running to generate additional
00:02:45.881 --> 00:02:47.769 boilerplate code around filtering
00:02:47.769 --> 00:02:50.880 by status is searching for them and
00:02:50.880 --> 00:02:53.260 then as well as across endpoints for.
00:02:53.260 --> 00:02:55.828 Statuses and things like that so.
00:02:55.830 --> 00:02:57.380 As much as you can,
00:02:57.380 --> 00:02:58.920 if you're adding like types,
00:02:58.920 --> 00:03:00.470 states, statuses, stuff like that,
00:03:00.470 --> 00:03:01.674 there's there's existing interfaces
00:03:01.674 --> 00:03:03.860 that will make your life much easier.
00:03:03.860 --> 00:03:05.672 So just if you're ever going
00:03:05.672 --> 00:03:07.260 to do something like that,
00:03:07.260 --> 00:03:09.346 you can check and make sure those
00:03:09.346 --> 00:03:11.219 exist in the place you'll find
00:03:11.219 --> 00:03:13.347 those is in the 01 data model
00:03:13.418 --> 00:03:15.595 project and it will be under models
00:03:15.595 --> 00:03:17.148 and then the shared folder,
00:03:17.148 --> 00:03:19.002 and you'll see a folder that's
00:03:19.002 --> 00:03:20.548 two folders in there called.
00:03:20.550 --> 00:03:23.254 I am and I have and those will
00:03:23.254 --> 00:03:25.870 define some of that out of the box.
00:03:25.870 --> 00:03:27.418 Basic functionality like I
00:03:27.418 --> 00:03:28.966 am a relationship table.
00:03:28.970 --> 00:03:31.609 I have a status things like that
00:03:31.609 --> 00:03:33.724 that will help generate some
00:03:33.724 --> 00:03:35.969 boilerplate code that you won't
00:03:35.969 --> 00:03:38.609 have to do yourself later.
00:03:38.610 --> 00:03:39.120 So.
00:03:39.120 --> 00:03:41.160 Where we left off,
00:03:41.160 --> 00:03:43.204 we had already run the T fours
00:03:43.204 --> 00:03:45.399 in the 01 data model layer,
00:03:45.400 --> 00:03:48.660 so we're going to move up to the 02 layer,
00:03:48.660 --> 00:03:50.616 which I think we already did.
00:03:50.620 --> 00:03:53.880 So let's go ahead and look at the diff again.
00:03:53.880 --> 00:03:55.896 Josh is to make sure that they
00:03:55.896 --> 00:03:58.265 result of running those was what we
00:03:58.265 --> 00:04:00.065 expected because sometimes it's not,
00:04:00.070 --> 00:04:01.674 and that is unfortunate.
00:04:01.674 --> 00:04:04.080 So then we're going to ignore
00:04:04.163 --> 00:04:06.257 all the skins files down there
00:04:06.257 --> 00:04:08.329 for now and just look at.
00:04:08.330 --> 00:04:10.352 OK, so obviously we didn't modify
00:04:10.352 --> 00:04:12.036 user product type sales, group,
00:04:12.036 --> 00:04:14.724 sales group, and store on the top part.
00:04:14.730 --> 00:04:17.089 So let's see what those changes are.
00:04:19.570 --> 00:04:22.342 OK, that's commented out so we don't
00:04:22.342 --> 00:04:24.678 care about that. But the next one.
00:04:29.480 --> 00:04:31.628 I just rearranged those,
00:04:31.628 --> 00:04:34.230 so that's fine. Next one.
00:04:37.640 --> 00:04:41.150 OK, that's interesting. Why did it do that?
00:04:48.320 --> 00:04:49.440 Remove that.
00:04:51.920 --> 00:04:55.346 Ha. Well, I don't think
00:04:55.346 --> 00:04:57.416 we wanted that to happen.
00:04:59.470 --> 00:05:00.210 Oh
00:05:03.060 --> 00:05:05.589 I wonder if that is now inside of IAM
00:05:05.589 --> 00:05:07.849 filter will buy account search model.
00:05:12.590 --> 00:05:14.565 Sometimes this happens and that's
00:05:14.565 --> 00:05:17.829 why I said anytime you run a T for
00:05:17.829 --> 00:05:20.060 the very first thing you should do
00:05:20.060 --> 00:05:22.405 after running it is check the diff.
00:05:22.410 --> 00:05:25.600 Because God knows what silly
00:05:25.600 --> 00:05:27.514 things have transpired.
00:05:27.520 --> 00:05:29.445 So real quick before we dig into
00:05:29.445 --> 00:05:31.189 this look at this last one,
00:05:31.190 --> 00:05:32.876 the search model storage dot store.
00:05:35.250 --> 00:05:37.930 OK, just added a blank line that's removed.
00:05:37.930 --> 00:05:39.274 A blank line actually.
00:05:39.274 --> 00:05:40.946 OK, that's fine. Who cares?
00:05:40.946 --> 00:05:41.948 That is acceptable.
00:05:41.950 --> 00:05:43.625 Let's look at the three
00:05:43.625 --> 00:05:44.965 new files that generated.
00:05:44.970 --> 00:05:47.308 It looks like it generated ATXT file,
00:05:47.310 --> 00:05:48.315 which is confusing.
00:05:48.315 --> 00:05:50.662 It's gonna be here, not version files.
00:05:50.662 --> 00:05:51.998 The third one down.
00:05:52.000 --> 00:05:54.010 Let's look at that text file.
00:05:56.220 --> 00:06:03.148 OK, that's like. Using lab results status
00:06:03.148 --> 00:06:06.950 gift already processed, that's interesting.
00:06:06.950 --> 00:06:09.344 What if I said I don't agree with that?
00:06:17.690 --> 00:06:19.216 Let's look at the user lab results
00:06:19.216 --> 00:06:20.521 status real quick. Make sure that
00:06:20.521 --> 00:06:21.823 we didn't do something in there.
00:06:26.270 --> 00:06:28.560 In in the Visual Studio, sorry.
00:06:28.560 --> 00:06:31.200 On the right side.
00:06:31.200 --> 00:06:32.504 Place my usual status.
00:06:32.504 --> 00:06:33.808 You everything looks contacts.
00:06:33.810 --> 00:06:36.736 Yeah OK. I don't know why it's.
00:06:36.740 --> 00:06:39.140 Maybe? And whatever, anyway,
00:06:39.140 --> 00:06:42.608 it's probably fine, and if it's not,
00:06:42.608 --> 00:06:44.693 we will figure that out.
00:06:44.700 --> 00:06:47.740 Probably the hard way.
00:06:47.740 --> 00:06:50.566 Let's dig into that sales Group 1 real quick,
00:06:50.570 --> 00:06:52.628 so let's find that I search models
00:06:52.628 --> 00:06:54.650 that sales dot sales group class.
00:06:54.650 --> 00:06:57.038 So if you go into Visual
00:06:57.038 --> 00:06:58.880 Studio and type control T.
00:06:58.880 --> 00:07:00.448 While you're looking at
00:07:00.448 --> 00:07:02.800 any any of the hour here.
00:07:02.800 --> 00:07:05.617 And then type that sales or whatever it was.
00:07:05.620 --> 00:07:06.868 I can't remember exactly
00:07:06.868 --> 00:07:08.116 that file was called,
00:07:08.120 --> 00:07:09.998 but you'll just type that filename.
00:07:10.000 --> 00:07:11.565 I search models dot sales
00:07:11.565 --> 00:07:13.130 dot sales group I think.
00:07:19.050 --> 00:07:21.017 Yep, there it is and you said
00:07:21.017 --> 00:07:23.270 enter and it will open that file.
00:07:23.270 --> 00:07:24.310 Yeah, there's no errors.
00:07:24.310 --> 00:07:25.870 F 12 into iron filter by
00:07:25.925 --> 00:07:27.038 account search model.
00:07:30.810 --> 00:07:33.000 It doesn't have that thing that
00:07:33.000 --> 00:07:35.560 was removed. Go ahead and go back.
00:07:40.350 --> 00:07:42.780 If you have a back button on your mouse,
00:07:42.780 --> 00:07:44.607 you can just press that and it'll
00:07:44.607 --> 00:07:46.288 go back where we were before,
00:07:46.290 --> 00:07:50.060 but it's also out left. Also that.
00:07:53.630 --> 00:07:56.535 I'm gonna say. That we open that
00:07:56.535 --> 00:08:00.136 diff up and we just reset this file.
00:08:00.140 --> 00:08:04.235 This specific one because I I have a feeling.
00:08:04.240 --> 00:08:06.557 That that's not supposed to be changed,
00:08:06.560 --> 00:08:09.280 so you can. You can right click the
00:08:09.280 --> 00:08:11.821 file itself in the diff and just do
00:08:11.821 --> 00:08:14.169 revert so you can close this one.
00:08:16.190 --> 00:08:17.130 And then just right click
00:08:17.130 --> 00:08:18.070 that file and hit revert.
00:08:20.460 --> 00:08:24.210 Yes. You ever if you ever run a T4 and get
00:08:24.265 --> 00:08:26.077 something like that where you're like?
00:08:26.080 --> 00:08:28.090 I don't know if that was
00:08:28.090 --> 00:08:29.800 supposed to happen or not.
00:08:29.800 --> 00:08:32.061 Don't hesitate to either make a post
00:08:32.061 --> 00:08:35.251 in the in Stackoverflow or just in the
00:08:35.251 --> 00:08:38.029 development team channel and and say hey,
00:08:38.030 --> 00:08:41.387 I just ran a T4 and this file changed.
00:08:41.390 --> 00:08:44.798 What's the deal and either me or James
00:08:44.798 --> 00:08:47.697 or somebody will see it and either
00:08:47.697 --> 00:08:50.509 tell you that's fine or reset it.
00:08:50.510 --> 00:08:52.918 And I'm not totally sure what the right
00:08:52.918 --> 00:08:55.119 answer is on this one to be honest,
00:08:55.120 --> 00:08:55.882 I'm just I.
00:08:55.882 --> 00:08:57.406 I don't imagine that that change
00:08:57.406 --> 00:08:58.859 is expected or intended,
00:08:58.860 --> 00:09:01.740 so we're just going to go ahead and reset it.
00:09:01.740 --> 00:09:03.130 The others are just changing
00:09:03.130 --> 00:09:04.910 commented out lines or blank spaces,
00:09:04.910 --> 00:09:07.406 so that's not a big deal.
00:09:07.410 --> 00:09:09.610 So we'll leave those.
00:09:09.610 --> 00:09:13.863 OK, so go ahead and rebuild the 02
00:09:13.863 --> 00:09:16.650 interfaces project the models one.
00:09:16.650 --> 00:09:18.393 So you just right click on the
00:09:18.393 --> 00:09:20.029 project there and then do rebuild.
00:09:28.390 --> 00:09:31.726 OK, it succeeded, so that's good.
00:09:31.730 --> 00:09:37.346 Now you can go back and search TT again.
00:09:37.350 --> 00:09:38.730 In the air solution Explorer,
00:09:38.730 --> 00:09:40.380 which by the way I mentioned
00:09:40.380 --> 00:09:41.480 this to Josh earlier,
00:09:41.480 --> 00:09:42.850 but I'll mention it here.
00:09:42.850 --> 00:09:45.001 This is how you can find all of the
00:09:45.001 --> 00:09:47.247 T forms that you'll need to run.
00:09:47.250 --> 00:09:49.450 So now that we've run the search models,
00:09:49.450 --> 00:09:51.100 we can run filter by TT.
00:09:53.140 --> 00:09:56.638 Which is the yeah right there.
00:09:56.640 --> 00:10:00.180 And this one shouldn't break now.
00:10:00.180 --> 00:10:03.998 Probably. OK, and then go
00:10:03.998 --> 00:10:05.383 ahead and rebuild the searching
00:10:05.383 --> 00:10:06.966 project so you don't have to
00:10:06.966 --> 00:10:08.221 clear your search engine yet.
00:10:08.230 --> 00:10:09.718 Do it right there.
00:10:09.718 --> 00:10:11.950 That way we don't have to.
00:10:11.950 --> 00:10:13.870 Come in and out of the search results.
00:10:19.510 --> 00:10:24.208 Yeah. I was I was correct in my belief.
00:10:24.210 --> 00:10:26.346 This project actually references
00:10:26.346 --> 00:10:29.550 02 interfaces and I believe it's
00:10:29.635 --> 00:10:32.425 because it uses the search models.
00:10:32.430 --> 00:10:34.596 OK, we had one that failed.
00:10:34.600 --> 00:10:36.940 Let's look at the error list and see why.
00:10:41.050 --> 00:10:42.218 Double click on that.
00:10:49.720 --> 00:10:50.832 OK, so something changed.
00:10:50.832 --> 00:10:52.510 We ran the T4. That probably
00:10:52.510 --> 00:10:53.910 also wasn't supposed to change,
00:10:53.910 --> 00:10:57.978 so if you go back to your diff again.
00:10:57.980 --> 00:11:00.094 And then refresh or we close it.
00:11:00.100 --> 00:11:03.215 That's also a way to do that.
00:11:03.220 --> 00:11:05.815 But if and then we'll
00:11:05.815 --> 00:11:08.410 look at what changed and.
00:11:08.410 --> 00:11:10.356 There it is, the second one there,
00:11:10.360 --> 00:11:11.750 26 lines added, zero removed,
00:11:11.750 --> 00:11:13.886 so just go ahead and double click on
00:11:13.886 --> 00:11:16.185 this to see what's going on in here.
00:11:18.750 --> 00:11:21.110 OK, added the ones that
00:11:21.110 --> 00:11:22.998 it's saying don't exist.
00:11:23.000 --> 00:11:24.764 And then Scroll down and see
00:11:24.764 --> 00:11:26.888 what the other changes are at the
00:11:26.888 --> 00:11:28.658 bottom bunch of stuff about brands.
00:11:28.660 --> 00:11:31.720 We can probably leave that one.
00:11:31.720 --> 00:11:35.968 This is weird. Gotta scroll up real quick.
00:11:35.970 --> 00:11:40.183 And then reset. Honestly, screw it.
00:11:40.183 --> 00:11:41.538 Just reset this whole file.
00:11:41.540 --> 00:11:43.388 Close this and revert the file and
00:11:43.388 --> 00:11:45.060 we're just going to keep rolling.
00:11:47.160 --> 00:11:48.630 And one of these days we're
00:11:48.630 --> 00:11:50.510 going to have to fix that stuff.
00:11:50.510 --> 00:11:52.454 Go back in there real quick and I want
00:11:52.454 --> 00:11:54.655 to just go through the other changes and
00:11:54.655 --> 00:11:56.958 make sure that everything else is is fine.
00:11:56.960 --> 00:11:58.508 Isn't that basically the same as
00:11:58.508 --> 00:12:00.409 editing those ****** by hand though?
00:12:00.409 --> 00:12:02.647 If we're also going to keep
00:12:02.647 --> 00:12:04.170 other stuff in here.
00:12:04.170 --> 00:12:06.714 It's it we're not editing the TT or
00:12:06.714 --> 00:12:08.919 editing the result of the running.
00:12:08.920 --> 00:12:10.615 Yeah, sorry, editing the results
00:12:10.615 --> 00:12:12.648 of the forms by hand, correct?
00:12:12.648 --> 00:12:15.460 It is exactly that, however.
00:12:15.460 --> 00:12:17.259 We don't have the time on this
00:12:17.259 --> 00:12:19.074 task to dig into why running the
00:12:19.074 --> 00:12:21.613 T4 on an out of the box stuff is
00:12:21.613 --> 00:12:23.293 changing files we didn't touch,
00:12:23.300 --> 00:12:25.260 so we're just going to reset him,
00:12:25.260 --> 00:12:28.110 move on with our lives.
00:12:28.110 --> 00:12:29.937 And I'm going to make a mental
00:12:31.612 --> 00:12:33.530 and just run all the T force,
00:12:33.530 --> 00:12:34.900 because in theory that shouldn't
00:12:34.900 --> 00:12:36.510 change anything out of the box.
00:12:36.510 --> 00:12:38.407 But obviously that is not the case,
00:12:38.410 --> 00:12:40.150 so let's see searching CS project
00:12:40.150 --> 00:12:41.848 change that's adding the new classes
00:12:41.848 --> 00:12:43.556 based on the new schema we made,
00:12:43.560 --> 00:12:44.340 so that's expected.
00:12:44.340 --> 00:12:46.764 Next one is also expected to add some stuff
00:12:46.764 --> 00:12:48.703 'cause we changed it user product type.
00:12:48.710 --> 00:12:50.566 Let's look at that one to make sure
00:12:50.566 --> 00:12:52.228 that that didn't break anything.
00:12:52.230 --> 00:12:54.669 I think it's just going to be comment change.
00:12:54.670 --> 00:12:54.940 Yep,
00:12:54.940 --> 00:12:55.480 that's fine.
00:12:57.950 --> 00:13:01.502 About that one that's only with that.
00:13:01.502 --> 00:13:03.320 It's just rearranging and in the
00:13:03.382 --> 00:13:05.370 next one we already checked as well,
00:13:05.370 --> 00:13:07.538 so alright and then we can look at
00:13:07.538 --> 00:13:09.858 the ones that are generated as well,
00:13:09.860 --> 00:13:11.946 which is going to be this device,
00:13:11.950 --> 00:13:14.840 which is perfectly fine. OK, so.
00:13:14.840 --> 00:13:17.206 I'm going to say let's go ahead
00:13:17.206 --> 00:13:19.379 and commit what we have so far.
00:13:19.380 --> 00:13:21.048 However, you prefer to do that,
00:13:21.050 --> 00:13:23.282 but we just want to make sure that
00:13:23.282 --> 00:13:25.767 we don't take all of the files I want
00:13:25.767 --> 00:13:28.025 to leave the skin out for now and
00:13:28.025 --> 00:13:31.260 just get the T4's that were running.
00:13:31.260 --> 00:13:34.548 Because just for separation of things.
00:13:52.800 --> 00:13:54.144 Right now you'll do.
00:13:54.144 --> 00:13:56.650 They get add instead of committing to git.
00:13:56.650 --> 00:13:59.220 Add and you'll do a.
00:13:59.220 --> 00:14:02.829 01 and then tab and you make a tab
00:14:02.829 --> 00:14:05.817 several times to get to filter by.
00:14:05.820 --> 00:14:07.218 Alright, yeah, searching that was it?
00:14:09.420 --> 00:14:12.066 Yep, and then so hit enter.
00:14:12.070 --> 00:14:15.710 And then get add 02.
00:14:15.710 --> 00:14:18.506 And then tab and then enter.
00:14:18.510 --> 00:14:20.064 And then do a quick get status
00:14:20.064 --> 00:14:21.392 and make sure that there's
00:14:21.392 --> 00:14:22.907 nothing else outside of that.
00:14:22.910 --> 00:14:24.470 Oh, wait, skins that we yeah?
00:14:24.470 --> 00:14:28.190 OK good so you can commit this one and say.
00:14:28.190 --> 00:14:29.738 Run additional T force.
00:14:31.990 --> 00:14:34.342 And for those that were not there
00:14:34.342 --> 00:14:36.999 for when we started this process,
00:14:37.000 --> 00:14:40.760 I'll very briefly cover why.
00:14:40.760 --> 00:14:42.782 I always recommend if you're running
00:14:42.782 --> 00:14:46.003 a lot of T fours like biking do when
00:14:46.003 --> 00:14:48.557 you make a schema change after you
00:14:48.557 --> 00:14:50.958 have run a T4 and audited things.
00:14:50.960 --> 00:14:53.312 Make a commit in case the
00:14:53.312 --> 00:14:55.200 next T4 blows something up,
00:14:55.200 --> 00:14:57.984 you can just revert the commit or just
00:14:57.984 --> 00:15:00.424 revert your locally changed files and
00:15:00.424 --> 00:15:03.280 pretend it never happened and call 911.
00:15:05.390 --> 00:15:07.294 That way, if most of your T4's
00:15:07.294 --> 00:15:08.860 work and then one breaks,
00:15:08.860 --> 00:15:10.995 you don't have to manually pick out
00:15:10.995 --> 00:15:13.265 all the files that were good versus
00:15:13.265 --> 00:15:15.203 the ones that aren't and then.
00:15:15.210 --> 00:15:16.835 You know next things take
00:15:16.835 --> 00:15:18.135 10 times longer self.
00:15:18.140 --> 00:15:19.436 OK, so real quick.
00:15:19.436 --> 00:15:22.235 I didn't think to go ahead and rebuild
00:15:22.235 --> 00:15:25.347 stuff in Visual Studio because I'm a fool.
00:15:25.350 --> 00:15:27.462 So let's go ahead and rebuild
00:15:27.462 --> 00:15:28.870 the searching project again.
00:15:31.310 --> 00:15:33.686 It should successfully build this time.
00:15:56.290 --> 00:16:01.870 Yep. Excellent, OK so. Moving on,
00:16:01.870 --> 00:16:04.606 we're going to go ahead and run the
00:16:04.606 --> 00:16:07.529 T fours under interfaces workflows.
00:16:07.530 --> 00:16:10.568 So I association workflow and I workflows.
00:16:19.480 --> 00:16:22.917 And now that I'm thinking about it.
00:16:22.920 --> 00:16:24.816 I do want to check one quick thing.
00:16:24.820 --> 00:16:26.724 Go ahead and run that one as well.
00:16:29.070 --> 00:16:33.308 And that was very fast. Did it run?
00:16:33.308 --> 00:16:35.380 Run it again just to be sure.
00:16:35.380 --> 00:16:38.364 'cause I feel like that was really fast.
00:16:38.370 --> 00:16:40.608 I guess that's just a fast one, alright?
00:16:40.608 --> 00:16:43.872 OK, so go back into go ahead and
00:16:43.872 --> 00:16:46.977 close the search results real quick.
00:16:46.980 --> 00:16:48.842 And then go into the scroll up
00:16:48.842 --> 00:16:50.816 into the 02 interfaces model so
00:16:50.816 --> 00:16:53.024 it's gonna be right there where
00:16:53.024 --> 00:16:55.236 you're at and then expand contacts.
00:16:55.240 --> 00:16:57.920 And find our user.
00:16:57.920 --> 00:16:59.120 Something, something well,
00:16:59.120 --> 00:17:00.445 actually it's going to be
00:17:00.445 --> 00:17:01.659 under eye models that TT.
00:17:03.850 --> 00:17:08.068 Expandi models dot TT right there.
00:17:08.070 --> 00:17:12.734 Yep and. Oh, it's called
00:17:12.734 --> 00:17:14.246 you downloaded that great,
00:17:14.250 --> 00:17:16.742 so we're going to find I models
00:17:16.742 --> 00:17:18.779 dot context user lab results.
00:17:22.430 --> 00:17:24.206 There it is. Then we're going
00:17:24.206 --> 00:17:26.071 to see what it auto generated
00:17:26.071 --> 00:17:28.495 in here so I can open that up.
00:17:28.500 --> 00:17:32.156 Absolutely nothing, but I did get the status,
00:17:32.160 --> 00:17:36.017 but it didn't get the related object.
00:17:36.020 --> 00:17:37.228 Or the other thing,
00:17:37.228 --> 00:17:39.470 so we're going to manually add those.
00:17:39.470 --> 00:17:41.040 So like I said earlier,
00:17:41.040 --> 00:17:42.954 that the force will generate 95
00:17:42.954 --> 00:17:45.130 ish percent of the code for you.
00:17:45.130 --> 00:17:47.634 This one we will have to do ourselves.
00:17:47.640 --> 00:17:50.120 Also, it's super weird that it added that
00:17:50.120 --> 00:17:52.350 user image type type ship is skipped,
00:17:52.350 --> 00:17:55.430 already processed at the top of this file.
00:17:55.430 --> 00:17:57.838 Some substance, something funky in that T4.
00:17:57.840 --> 00:17:58.791 Anywho, we won't.
00:17:58.791 --> 00:18:01.620 You won't want to change this file manually,
00:18:01.620 --> 00:18:04.028 since this one is the T4 generated,
00:18:04.030 --> 00:18:06.438 even though I've already violated that rule.
00:18:06.440 --> 00:18:07.772 As Jonathan pointed out.
00:18:07.772 --> 00:18:10.220 So in order to manually add these,
00:18:10.220 --> 00:18:11.940 you'll notice that it's declared
00:18:11.940 --> 00:18:13.316 as a partial interface,
00:18:13.320 --> 00:18:15.824 and So what that means is we can
00:18:15.824 --> 00:18:18.367 create a separate file and add the
00:18:18.367 --> 00:18:20.890 rest of the stuff that we need.
00:18:20.890 --> 00:18:22.948 So if you go Scroll down,
00:18:22.950 --> 00:18:25.008 or actually probably easier to collapse,
00:18:25.010 --> 00:18:27.710 I models first.
00:18:27.710 --> 00:18:31.958 Yeah, and then open up the contacts folder.
00:18:31.960 --> 00:18:35.056 We're going to add a new file in here
00:18:35.056 --> 00:18:37.450 that's I. Use your lab results model.
00:18:48.920 --> 00:18:51.320 Alright, and then we're going to
00:18:51.320 --> 00:18:53.448 change the namespace to clarity
00:18:53.448 --> 00:18:55.698 dot E commerce dot interface
00:18:55.698 --> 00:18:57.919 interfaces dot models list removed
00:18:57.919 --> 00:19:00.320 context off the end and then make
00:19:00.320 --> 00:19:02.420 this a public partial interface.
00:19:02.420 --> 00:19:04.300 Instead of a class.
00:19:13.240 --> 00:19:15.300 Yeah, perfect and then
00:19:15.300 --> 00:19:17.360 fix the copyright stuff.
00:19:27.060 --> 00:19:29.195 So now if your traffic to cooperate,
00:19:29.200 --> 00:19:31.030 I think you can also use.
00:19:31.030 --> 00:19:33.396 I'd have that little green under re-enter
00:19:33.396 --> 00:19:36.226 line back up there before you changed it.
00:19:36.230 --> 00:19:38.310 You should also be able to just go
00:19:38.310 --> 00:19:40.797 to the adult enter and it should say
00:19:40.797 --> 00:19:42.830 like add file header from right.
00:19:42.830 --> 00:19:44.426 That's part of the.
00:19:44.426 --> 00:19:46.421 How make all those things
00:19:46.421 --> 00:19:48.818 at the stylecop analyzers?
00:19:48.820 --> 00:19:50.300 You've already fixed it,
00:19:50.300 --> 00:19:52.520 so it should be good now,
00:19:52.520 --> 00:19:54.740 though I did not know that.
00:19:54.740 --> 00:19:56.932 OK, so the what we need to add
00:19:56.932 --> 00:19:59.181 on to this interface is anything
00:19:59.181 --> 00:20:02.133 that we declared on the on the
00:20:02.133 --> 00:20:04.358 entity that's not present here,
00:20:04.360 --> 00:20:06.210 so that's going to be,
00:20:06.210 --> 00:20:06.950 for example,
00:20:06.950 --> 00:20:09.910 the user itself and the lab results string,
00:20:09.910 --> 00:20:12.500 so I don't remember the exact syntax.
00:20:12.500 --> 00:20:14.350 So to help us out,
00:20:14.350 --> 00:20:16.856 let's go ahead and open up I
00:20:16.856 --> 00:20:18.790 user model on the left.
00:20:21.400 --> 00:20:24.208 In the solution explorer.
00:20:24.210 --> 00:20:28.575 Anne will look at how it does the things.
00:20:28.580 --> 00:20:29.995 Docket on the right and
00:20:29.995 --> 00:20:31.410 open up the related objects.
00:20:31.410 --> 00:20:35.314 'cause we'll get that user set up first.
00:20:35.320 --> 00:20:38.029 And that's all kinds out of water.
00:20:38.030 --> 00:20:39.730 That's fine I guess.
00:20:39.730 --> 00:20:42.850 So go back into the left side.
00:20:42.850 --> 00:20:46.948 And add the related objects region.
00:20:46.950 --> 00:20:48.720 Even if there's only one,
00:20:48.720 --> 00:20:51.550 we keep them in regions.
00:20:51.550 --> 00:20:53.380 Makefile is easier to read.
00:20:55.690 --> 00:20:57.601 And then inside that region we're going
00:20:57.601 --> 00:21:00.009 to add the nullable int called user ID.
00:21:15.080 --> 00:21:19.424 Neither at this pace before get as well.
00:21:19.430 --> 00:21:22.688 And then next line down at
00:21:22.688 --> 00:21:26.509 and I user model called user.
00:21:30.040 --> 00:21:32.136 And then saying get set on that one.
00:21:34.600 --> 00:21:37.328 Perfect and you can also for the docs
00:21:37.328 --> 00:21:40.371 on these you can just copy the XML docs
00:21:40.371 --> 00:21:43.358 from the user lab results entity itself.
00:21:45.430 --> 00:21:47.248 Which it looks like you've opened
00:21:47.248 --> 00:21:49.267 on the left side. Not those ones,
00:21:49.267 --> 00:21:51.514 but on the on the actual lab results
00:21:51.514 --> 00:21:53.914 so that it all matches just copy the
00:21:53.914 --> 00:21:56.045 user ID and user ones right there.
00:22:01.400 --> 00:22:02.680 Do the same for.
00:22:04.960 --> 00:22:06.060 Perfect.
00:22:08.070 --> 00:22:09.780 Saving some time.
00:22:12.900 --> 00:22:16.908 Alright, and then next, under the.
00:22:16.910 --> 00:22:18.590 Underneath the actually above related
00:22:18.590 --> 00:22:22.800 objects, we're going to add another region.
00:22:22.800 --> 00:22:26.856 Called a user lab results properties.
00:22:34.270 --> 00:22:36.484 And then in there we're going
00:22:36.484 --> 00:22:38.990 to add the string lab results.
00:22:47.410 --> 00:22:48.915 Alright, and then copy the
00:22:48.915 --> 00:22:50.750 documentation for that one as well.
00:23:01.690 --> 00:23:03.790 Perfect. OK, so that should
00:23:03.790 --> 00:23:05.890 get all that figured out.
00:23:05.890 --> 00:23:08.186 If you go back to the the second
00:23:08.186 --> 00:23:10.277 tab you have open AI models,
00:23:10.280 --> 00:23:11.850 contacts that user lab results.
00:23:11.850 --> 00:23:14.178 I have a status based model that should
00:23:14.178 --> 00:23:16.560 get the other two things we'll need,
00:23:16.560 --> 00:23:18.130 which is status idea status.
00:23:18.130 --> 00:23:20.410 So if you fall into that we need
00:23:20.410 --> 00:23:22.836 to make sure that that does that,
00:23:22.840 --> 00:23:24.730 which I'm 99% sure it does.
00:23:26.760 --> 00:23:28.204 Yeah, it sure does.
00:23:28.204 --> 00:23:30.810 Excellent so we can close this file,
00:23:30.810 --> 00:23:33.074 just making sure that that does the things.
00:23:33.080 --> 00:23:35.222 Yeah, and I'm starting to think that
00:23:35.222 --> 00:23:37.643 we may have actually had an easier way
00:23:37.643 --> 00:23:40.354 to do a little bit of this if we go
00:23:40.354 --> 00:23:43.076 back into the 01 data model real quick.
00:23:43.076 --> 00:23:45.586 Their own data access layer.
00:23:45.590 --> 00:23:49.310 And then open up the models.
00:23:49.310 --> 00:23:50.630 And then shared.
00:23:54.690 --> 00:23:58.110 I have a is there and I have a.
00:23:58.110 --> 00:24:01.910 I have a contact is not. I have a user.
00:24:08.660 --> 00:24:10.088 I was trying to find if
00:24:10.088 --> 00:24:11.720 there was and I have like.
00:24:11.720 --> 00:24:15.325 I have a related object or something.
00:24:15.330 --> 00:24:18.108 I don't think there is though.
00:24:18.110 --> 00:24:20.470 Which is fine, that's fine.
00:24:23.210 --> 00:24:25.415 That means we get to have more fun later,
00:24:25.420 --> 00:24:28.092 not in a bad way per say. It's just a.
00:24:28.092 --> 00:24:30.290 If there was a thing like that,
00:24:30.290 --> 00:24:31.505 it would have generate some
00:24:31.505 --> 00:24:32.477 of the filter endpoints,
00:24:32.480 --> 00:24:33.938 but some of the filter methods,
00:24:33.940 --> 00:24:35.386 but like to do this ourselves,
00:24:35.390 --> 00:24:36.119 but that's fine.
00:24:36.119 --> 00:24:37.334 We don't need that yet,
00:24:37.340 --> 00:24:39.956 and it's not going to prevent us from.
00:24:39.960 --> 00:24:43.590 Moving along so.
00:24:43.590 --> 00:24:45.155 So we've added the properties
00:24:45.155 --> 00:24:46.407 that we needed to.
00:24:46.410 --> 00:24:48.288 I use your lab results model,
00:24:48.290 --> 00:24:50.912 so let's go ahead and rebuild
00:24:50.912 --> 00:24:51.786 filtering again.
00:24:51.790 --> 00:24:53.918 And the only reason I say to rebuild
00:24:53.918 --> 00:24:56.270 the air searching sorry L1 searching.
00:24:56.270 --> 00:24:58.366 The reason I say to rebuild that one
00:24:58.366 --> 00:25:00.050 instead of interfaces is because
00:25:00.050 --> 00:25:01.522 searching relies on interfaces
00:25:01.522 --> 00:25:03.630 and they will rebuild that one.
00:25:03.630 --> 00:25:05.779 And searching in case the changes we
00:25:05.779 --> 00:25:07.469 made break anything in searching.
00:25:11.960 --> 00:25:15.800 Which they shouldn't probably.
00:25:15.800 --> 00:25:19.144 Who's the really famous last words are there?
00:25:19.150 --> 00:25:22.335 Yeah, that's why I ended with probably.
00:25:25.650 --> 00:25:28.198 Or rather, that's why you do your
00:25:28.198 --> 00:25:30.208 git commits before you run HD4.
00:25:30.210 --> 00:25:32.695 Alright, so I think we Speaking of
00:25:32.695 --> 00:25:35.439 we're probably in a good spot to run
00:25:35.439 --> 00:25:37.478 another or do another commit and
00:25:37.478 --> 00:25:39.650 just say adding additional fields to
00:25:39.650 --> 00:25:41.799 user or user lab results interface.
00:25:54.400 --> 00:25:56.848 Be a backslash. QA backslash set.
00:26:03.830 --> 00:26:05.720 And then do they get add?
00:26:05.720 --> 00:26:09.815 And then I think you need a one searching.
00:26:09.820 --> 00:26:11.827 I don't know if we change anything or not,
00:26:11.830 --> 00:26:14.120 but let's do it anyway.
00:26:14.120 --> 00:26:17.480 And then get add 02 interfaces
00:26:17.480 --> 00:26:20.460 so two and then yeah.
00:26:20.460 --> 00:26:22.926 And then do a get status just to make
00:26:22.926 --> 00:26:25.489 sure we're not leaving anything behind.
00:26:25.490 --> 00:26:27.470 One of those I can't read.
00:26:27.470 --> 00:26:29.450 The Red Texas is only rambunctious.
00:26:29.450 --> 00:26:30.440 That's right dude.
00:26:30.440 --> 00:26:32.750 Get at O2 and then tap twice.
00:26:32.750 --> 00:26:35.262 Yeah and then like get status to make
00:26:35.262 --> 00:26:37.696 sure that we got everything we want.
00:26:39.950 --> 00:26:42.270 Perfect, OK and then do a git commit.
00:26:44.650 --> 00:26:46.600 Actually, before we do anything
00:26:46.600 --> 00:26:49.407 else and I'm not going to make
00:26:49.407 --> 00:26:51.700 this mistake again, rebuild the
00:26:51.700 --> 00:26:53.940 O2 interfaces workflows project.
00:26:53.940 --> 00:26:54.712 We ran that before.
00:26:54.712 --> 00:26:56.040 I don't think we ever built it.
00:26:56.040 --> 00:26:58.338 I don't remember.
00:26:58.340 --> 00:27:00.348 So let's go ahead and rebuild that one.
00:27:27.770 --> 00:27:29.842 OK, so that works. So go ahead and
00:27:29.842 --> 00:27:31.868 run that commit and just call it.
00:27:34.730 --> 00:27:38.510 Ran workflow or ran more T fours.
00:27:38.510 --> 00:27:41.066 I think it's the other one
00:27:41.066 --> 00:27:42.344 actually doesn't matter.
00:27:42.350 --> 00:27:45.550 Right committed neither one.
00:27:45.550 --> 00:27:48.558 Let me just make sure you get it.
00:27:52.860 --> 00:27:54.500 And then the message.
00:27:54.500 --> 00:27:57.450 I just ran more T4's and. Look at.
00:28:02.730 --> 00:28:05.466 Alright, moving on so we ran
00:28:05.466 --> 00:28:07.830 our interfaces and all that.
00:28:07.830 --> 00:28:11.045 We ran searching random model
00:28:11.045 --> 00:28:14.260 so we're going to models.
00:28:14.260 --> 00:28:16.255 And now that I'm thinking about it,
00:28:16.260 --> 00:28:17.636 before we do that,
00:28:17.636 --> 00:28:20.550 let's look at user lab results real quick.
00:28:20.550 --> 00:28:25.830 Just a Yep that one there. So.
00:28:25.830 --> 00:28:27.648 I briefly mentioned some of this,
00:28:27.650 --> 00:28:28.822 I think on Friday,
00:28:28.822 --> 00:28:31.000 but I'll very quickly cover it again.
00:28:31.000 --> 00:28:32.818 There's there's a lot to cover,
00:28:32.820 --> 00:28:34.644 so I'm not going to go
00:28:34.644 --> 00:28:35.860 through the whole spiel,
00:28:35.860 --> 00:28:38.920 but I am going to quickly.
00:28:38.920 --> 00:28:42.568 Cover the attributes that control mapping.
00:28:42.570 --> 00:28:45.405 So obviously the entity in the database
00:28:45.405 --> 00:28:47.956 always has everything on it all the time.
00:28:47.960 --> 00:28:50.846 It's the entity in the database.
00:28:50.850 --> 00:28:52.975 However, for certain workflows you
00:28:52.975 --> 00:28:55.869 may not always want everything out of
00:28:55.869 --> 00:28:57.975 the database for any given entities.
00:28:57.980 --> 00:28:59.108 So for example,
00:28:59.108 --> 00:29:01.740 especially in the case of of storing
00:29:01.819 --> 00:29:03.919 a user's medical lab results,
00:29:03.920 --> 00:29:06.245 we probably don't really want
00:29:06.245 --> 00:29:08.105 to map anything out.
00:29:08.110 --> 00:29:08.958 And so,
00:29:08.958 --> 00:29:11.078 unless it's explicitly requested so,
00:29:11.080 --> 00:29:14.587 we basically want all the default CRUD
00:29:14.587 --> 00:29:18.689 endpoints to do very little with this data.
00:29:18.690 --> 00:29:19.024 So.
00:29:19.024 --> 00:29:21.362 What we're going to do to that
00:29:21.362 --> 00:29:23.917 end is specifically on the lab
00:29:23.917 --> 00:29:26.611 results on the user lab results
00:29:26.696 --> 00:29:28.328 class at the bottom.
00:29:30.640 --> 00:29:34.153 So I think line 50 so the line 50 on this
00:29:34.153 --> 00:29:37.205 file we're going to add an attribute.
00:29:39.920 --> 00:29:43.946 So we after the documentation there.
00:29:43.950 --> 00:29:47.219 It'll be between the inherit Doc and
00:29:47.219 --> 00:29:50.618 lab results being attribute on that one.
00:29:50.620 --> 00:29:52.908 And that attribute is going to be called.
00:29:52.910 --> 00:29:58.933 Don't map out, ever. So. That's a map
00:29:58.933 --> 00:30:00.930 in you change into out and get it.
00:30:03.920 --> 00:30:08.869 Sweet, so basically what this does is.
00:30:08.870 --> 00:30:13.580 In a very quick nutshell.
00:30:13.580 --> 00:30:17.148 Seps mapping project is where all of the
00:30:17.148 --> 00:30:19.435 conversions from an entity tool model
00:30:19.435 --> 00:30:22.900 an from a model to an entity or handled.
00:30:22.900 --> 00:30:25.728 So Seth has three layers of mapping,
00:30:25.730 --> 00:30:28.226 so a full mapping obviously takes
00:30:28.226 --> 00:30:30.998 everything from the entity into the model.
00:30:31.000 --> 00:30:33.670 Full mapping is extremely slow.
00:30:33.670 --> 00:30:36.898 And generally. Not what you need.
00:30:36.900 --> 00:30:38.040 Most of the time,
00:30:38.040 --> 00:30:40.403 and then there's a light mapping which takes
00:30:40.403 --> 00:30:42.771 a little bit less than the full mapping.
00:30:42.780 --> 00:30:45.124 Actually is a lot less than the flapping,
00:30:45.130 --> 00:30:46.870 and is generally probably the one
00:30:46.870 --> 00:30:48.950 you're going to need for most things.
00:30:48.950 --> 00:30:51.008 I would say, and then they'll like.
00:30:51.010 --> 00:30:52.828 The smallest mapping is the list
00:30:52.828 --> 00:30:54.829 mapping and that will be for where.
00:30:54.830 --> 00:30:56.618 Basically you just need like the
00:30:56.618 --> 00:30:58.431 name of something to display it
00:30:58.431 --> 00:31:00.117 in a list of several entries,
00:31:00.120 --> 00:31:01.590 and so obviously the full
00:31:01.590 --> 00:31:02.766 mapping is the slowest.
00:31:02.770 --> 00:31:04.528 The light mapping is fairly fast,
00:31:04.530 --> 00:31:06.408 but the list mapping is still.
00:31:06.410 --> 00:31:08.818 The fastest mapping these attributes let you
00:31:08.818 --> 00:31:10.838 control how different things get mapped.
00:31:10.840 --> 00:31:12.148 So in this case,
00:31:12.148 --> 00:31:14.110 because I imagine we want to
00:31:14.191 --> 00:31:16.301 have very explicit control over
00:31:16.301 --> 00:31:18.780 where these lab results go for.
00:31:18.780 --> 00:31:20.196 Compliance and user privacy,
00:31:20.196 --> 00:31:23.614 or just not going to map this out with
00:31:23.614 --> 00:31:25.659 any default workflow anywhere ever,
00:31:25.660 --> 00:31:28.060 and that will come in later when we
00:31:28.060 --> 00:31:30.620 when we want to actually expose these
00:31:30.620 --> 00:31:33.486 lab results will do that from endpoints
00:31:33.486 --> 00:31:35.756 that are specifically designed to
00:31:35.756 --> 00:31:38.648 expose these lab results and do various
00:31:38.648 --> 00:31:41.320 checks for permissions and things like that.
00:31:41.320 --> 00:31:43.462 But this attribute says that says
00:31:43.462 --> 00:31:45.789 don't map out ever basically says
00:31:45.789 --> 00:31:47.849 if somebody uses the workflows
00:31:47.849 --> 00:31:50.328 or the mapping layer to request.
00:31:50.330 --> 00:31:52.322 This entity never map out this
00:31:52.322 --> 00:31:52.986 specific field.
00:31:52.990 --> 00:31:53.920 The lab results.
00:31:53.920 --> 00:31:56.640 They can have the user in the status,
00:31:56.640 --> 00:31:58.884 but they cannot ever have the
00:31:58.884 --> 00:32:01.654 lab results and then will have to
00:32:01.654 --> 00:32:04.048 manually get the lab results later.
00:32:04.050 --> 00:32:05.326 But there are also.
00:32:05.326 --> 00:32:08.085 If you go in and look at some
00:32:08.085 --> 00:32:09.980 of those other don't maps,
00:32:09.980 --> 00:32:11.535 there's also things like don't
00:32:11.535 --> 00:32:12.779 map out with light.
00:32:12.780 --> 00:32:14.658 Don't map out with listing things
00:32:14.658 --> 00:32:17.197 like that where you can sort of fine
00:32:17.197 --> 00:32:18.732 tune exactly which attributes on
00:32:18.732 --> 00:32:21.205 an entity will be mapped out or in
00:32:21.205 --> 00:32:22.884 on different levels of the mapping.
00:32:22.884 --> 00:32:25.087 Then you can use that to fine tune
00:32:25.087 --> 00:32:26.419 performance for different layers
00:32:26.419 --> 00:32:28.949 and just as a really quick example,
00:32:28.950 --> 00:32:30.742 a full mapping is will be used
00:32:30.742 --> 00:32:32.531 for example on like the product
00:32:32.531 --> 00:32:34.445 details page where you're going to
00:32:34.445 --> 00:32:36.478 show everything about the product.
00:32:36.480 --> 00:32:37.990 All it's images related products,
00:32:37.990 --> 00:32:38.896 pricing, descriptions, attributes,
00:32:38.896 --> 00:32:40.406 everything you can think about.
00:32:40.410 --> 00:32:42.454 The product is going to be on
00:32:42.454 --> 00:32:44.618 the details page and so it makes
00:32:44.618 --> 00:32:46.138 sense that you're going to.
00:32:46.140 --> 00:32:47.775 You're going to pull everything
00:32:47.775 --> 00:32:49.756 about the product and it's fine
00:32:49.756 --> 00:32:51.730 that that's not going to be the
00:32:51.730 --> 00:32:53.090 fastest thing in the world.
00:32:53.090 --> 00:32:55.506 But you would use a list mapping for,
00:32:55.510 --> 00:32:57.200 like the catalog results because
00:32:57.200 --> 00:32:59.422 the only thing you want to see
00:32:59.422 --> 00:33:01.302 for that is like the name of the
00:33:01.367 --> 00:33:02.854 product. Maybe it's short description.
00:33:02.854 --> 00:33:05.225 A little bit of maybe some other information
00:33:05.225 --> 00:33:06.865 that's that's relatively lightweight.
00:33:06.870 --> 00:33:08.130 And because you're going
00:33:08.130 --> 00:33:09.390 to be mapping potentially,
00:33:09.390 --> 00:33:12.225 I think up to 27 products at a time.
00:33:12.230 --> 00:33:13.454 Doing it. That way,
00:33:13.454 --> 00:33:16.318 you're going to want that to be much faster,
00:33:16.320 --> 00:33:18.824 so that's kind of an example of where
00:33:18.824 --> 00:33:21.048 those different layers of mapping come in.
00:33:21.050 --> 00:33:23.297 So anyway, all that to say that
00:33:23.297 --> 00:33:24.830 attribute will help us here.
00:33:24.830 --> 00:33:26.618 Thankfully, we don't have to run
00:33:26.618 --> 00:33:29.238 any of the T4 as we've already run,
00:33:29.240 --> 00:33:31.760 but if you do change any of these,
00:33:31.760 --> 00:33:33.716 don't map or or mapping related
00:33:33.716 --> 00:33:35.427 attributes in the data model
00:33:35.427 --> 00:33:37.137 layer on an existing schema.
00:33:37.140 --> 00:33:39.756 You will need to rerun the mapping T4,
00:33:39.760 --> 00:33:42.334 which is what we're about to do so you
00:33:42.334 --> 00:33:45.307 can go ahead and save that file and then
00:33:45.307 --> 00:33:47.600 rebuild the one data model project.
00:33:50.210 --> 00:33:52.973 He added a blank line there on line 38.
00:33:55.040 --> 00:33:56.870 Who had pulled that out there,
00:33:56.870 --> 00:33:58.700 yeah, and then rebuild that project.
00:34:08.150 --> 00:34:09.450 Almost done.
00:34:14.080 --> 00:34:18.380 Perfect OK so we can go ahead and you can
00:34:18.490 --> 00:34:22.474 type TT TT back into the search there.
00:34:22.480 --> 00:34:24.106 And you can collapse 01 data
00:34:24.106 --> 00:34:25.870 access layer and 02 interfaces.
00:34:25.870 --> 00:34:28.966 Since we're done with the T4 and those.
00:34:28.970 --> 00:34:32.314 And we're going to go ahead and run.
00:34:32.320 --> 00:34:35.104 I models TT and then search models TT
00:34:35.104 --> 00:34:37.768 and also models registry actually.
00:34:37.770 --> 00:34:40.374 So those 3T four is at the
00:34:40.374 --> 00:34:43.220 top of the first three, yeah?
00:34:47.750 --> 00:34:49.158 These ones are. Obviously
00:34:49.158 --> 00:34:50.566 a little bit slower.
00:34:54.400 --> 00:34:56.507 Alright, and then on the next one.
00:35:03.890 --> 00:35:07.310 And then run models registry.
00:35:07.310 --> 00:35:09.518 No. I think you moved that
00:35:09.518 --> 00:35:11.900 one on accident or something.
00:35:11.900 --> 00:35:13.265 Something happened there.
00:35:13.265 --> 00:35:15.540 I'm not sure what happened.
00:35:15.540 --> 00:35:19.840 I just did. Control Z.
00:35:19.840 --> 00:35:24.616 Yeah, control Z didn't do anything.
00:35:24.620 --> 00:35:25.808 Something happened there.
00:35:28.050 --> 00:35:29.620 I think oh models registry.
00:35:29.620 --> 00:35:31.804 You moved it into the T4 folder.
00:35:31.810 --> 00:35:34.306 I think it wasn't in the T4 folder
00:35:34.306 --> 00:35:36.190 previously. Lube it up to there.
00:35:39.910 --> 00:35:40.650 K.
00:35:42.700 --> 00:35:44.940 Because the check yet to see what?
00:35:44.940 --> 00:35:47.131 Yeah, it'll lock change from A plus
00:35:47.131 --> 00:35:49.740 back to a lock so we're good now.
00:35:49.740 --> 00:35:51.340 That's where it was before.
00:35:51.340 --> 00:35:55.188 OK run that again just to make sure.
00:35:55.190 --> 00:35:57.308 Find custom tool.
00:35:57.308 --> 00:36:02.250 OK and then rebuild the models project.
00:36:02.250 --> 00:36:04.126 And I think it's going to fail.
00:36:06.170 --> 00:36:10.154 And the reason for that is we added.
00:36:10.160 --> 00:36:14.366 The things we needed to the.
00:36:14.370 --> 00:36:16.662 I yeah to the AI user
00:36:16.662 --> 00:36:19.000 interface or user lab results.
00:36:19.000 --> 00:36:20.883 Model, but we did not make the
00:36:20.883 --> 00:36:22.729 same addition to user lab results.
00:36:22.730 --> 00:36:25.466 So if you go to your error list
00:36:25.466 --> 00:36:27.870 will see whatever it is and.
00:36:27.870 --> 00:36:29.028 You can go and fix it.
00:36:32.880 --> 00:36:34.904 Yep, so double click on that one and
00:36:34.904 --> 00:36:36.998 so this is the T4, so we're not going
00:36:36.998 --> 00:36:38.740 to make the change in this file.
00:36:38.740 --> 00:36:40.350 We're going to do something very similar
00:36:40.350 --> 00:36:42.400 to what we did before in the interfaces,
00:36:42.400 --> 00:36:44.320 so you can go ahead and
00:36:44.320 --> 00:36:45.600 close the search results.
00:36:45.600 --> 00:36:48.726 On the on the solution explorer
00:36:48.726 --> 00:36:51.939 and then under your 03 models,
00:36:51.940 --> 00:36:53.518 expand that project.
00:36:56.470 --> 00:37:02.168 Right now right there and then contacts.
00:37:02.170 --> 00:37:07.156 And then add a new class to that folder.
00:37:07.160 --> 00:37:08.720 And that was going to be
00:37:08.720 --> 00:37:09.760 user lab results model.
00:37:21.510 --> 00:37:24.645 Perfect. And then again, we're going
00:37:24.645 --> 00:37:26.411 to change the namespace on this to
00:37:26.411 --> 00:37:27.875 just clarity E commerce dot models.
00:37:40.350 --> 00:37:42.483 And this is going to be a public partial
00:37:42.483 --> 00:37:44.136 class. Here the class name is correct.
00:37:44.140 --> 00:37:46.273 It will just make it a public partial class.
00:37:54.780 --> 00:37:57.060 Yeah, and now.
00:37:59.440 --> 00:38:00.368 Yeah, you got it.
00:38:06.190 --> 00:38:07.210 They have changed interface
00:38:07.210 --> 00:38:08.740 to class on that as well.
00:38:12.410 --> 00:38:14.120 Perfect, OK now inside of
00:38:14.120 --> 00:38:16.250 there we're going to get this.
00:38:16.250 --> 00:38:18.680 Basically the same stuff we had
00:38:18.680 --> 00:38:21.650 to I user lab results model.
00:38:21.650 --> 00:38:24.044 That being said, there are a
00:38:24.044 --> 00:38:25.640 couple of interesting gotchas,
00:38:25.640 --> 00:38:27.576 particularly with related models,
00:38:27.576 --> 00:38:31.024 so if you go to open up
00:38:31.024 --> 00:38:32.816 user model real quick.
00:38:32.820 --> 00:38:33.760 On the left side.
00:38:36.570 --> 00:38:38.796 Right there, yeah, you got it.
00:38:38.800 --> 00:38:41.509 And then look at its related objects.
00:38:41.510 --> 00:38:43.726 You're going to see something kind of wacky,
00:38:43.730 --> 00:38:46.680 so if you look at, for example.
00:38:46.680 --> 00:38:50.348 Account ID account key account name count
00:38:50.348 --> 00:38:55.430 and then I account model so it's weird. But
00:38:58.230 --> 00:38:59.418 that's basically the same
00:38:59.418 --> 00:39:01.200 thing that we have to do,
00:39:01.200 --> 00:39:03.034 so we're going to go ahead and
00:39:03.034 --> 00:39:05.360 add to the user lab results model.
00:39:05.360 --> 00:39:07.862 Go ahead and add the public
00:39:07.862 --> 00:39:09.860 nullable int. User ID.
00:39:20.850 --> 00:39:22.494 Alright, and then you can add
00:39:22.494 --> 00:39:24.400 the inherit doc on this as well.
00:39:34.680 --> 00:39:38.784 OK, and then go ahead and
00:39:38.784 --> 00:39:41.520 add public user model.
00:39:46.170 --> 00:39:48.080 That's a lot of words.
00:39:48.080 --> 00:39:50.747 User model and then user gets set.
00:39:55.060 --> 00:39:56.746 And then the next part weird.
00:39:56.750 --> 00:40:00.550 So this next one is not going to be public.
00:40:00.550 --> 00:40:03.140 It's going to be just no access
00:40:03.140 --> 00:40:05.360 specifier, just put I user model.
00:40:07.650 --> 00:40:11.458 And then. I use your lab results model.
00:40:16.470 --> 00:40:23.380 Dot. User. Yeah, and then do the. Get.
00:40:26.050 --> 00:40:27.522 Then yeah, you got.
00:40:27.522 --> 00:40:29.730 And it's going to return user.
00:40:32.490 --> 00:40:37.640 And then the set. Is going to set user too
00:40:37.640 --> 00:40:40.818 and then cast the interface to concrete.
00:40:45.140 --> 00:40:46.939 The user model. Yeah, we got it.
00:40:53.310 --> 00:40:56.174 And semi colon? And what is it help?
00:40:56.180 --> 00:40:58.700 We need the using for the interface,
00:40:58.700 --> 00:41:01.094 so you're going to add using interfaces
00:41:01.094 --> 00:41:03.718 dot models right before the partial class.
00:41:12.530 --> 00:41:15.962 And then you'll shorten that to
00:41:15.962 --> 00:41:18.678 just interfaces dot models. Perfect.
00:41:18.678 --> 00:41:21.246 And then on the inherit Doc,
00:41:21.250 --> 00:41:23.110 you put just a regular inherit
00:41:23.110 --> 00:41:25.375 doc on the second one on the I
00:41:25.375 --> 00:41:27.408 user Model 1 and then on the next
00:41:27.408 --> 00:41:29.004 one you have to do this.
00:41:29.010 --> 00:41:29.697 See ref part.
00:41:29.697 --> 00:41:31.071 So it knows what to inherit
00:41:31.071 --> 00:41:32.330 the documentation from.
00:41:34.520 --> 00:41:36.860 Please sorry, copy that one down.
00:41:36.860 --> 00:41:40.370 Yep, right there and then if you change that.
00:41:40.370 --> 00:41:43.820 So after inherit Doc do space.
00:41:43.820 --> 00:41:45.608 Sorry, in inside the brackets right
00:41:45.608 --> 00:41:47.519 after the the word inherit Doc.
00:41:47.520 --> 00:41:49.104 Before this life.
00:41:49.104 --> 00:41:52.272 Yeah and then do see ref.
00:41:52.280 --> 00:41:54.664 Equals and then it's going to be I.
00:41:54.670 --> 00:41:56.470 User Lab results model dot user.
00:42:02.200 --> 00:42:03.940 Perfect, and that basically says
00:42:03.940 --> 00:42:05.332 inherit the documentation from
00:42:05.332 --> 00:42:06.967 this member on the interface.
00:42:06.970 --> 00:42:07.993 Just that curiosity,
00:42:07.993 --> 00:42:10.380 can you have 12 on the CRF?
00:42:12.520 --> 00:42:14.116 It will actually go to the thing.
00:42:16.590 --> 00:42:17.826 Which one you wanna go to?
00:42:17.830 --> 00:42:20.350 'cause there's it's a partial bed.
00:42:20.350 --> 00:42:22.566 I was just wondering if it was actually
00:42:22.566 --> 00:42:24.372 even possible to see that since
00:42:24.372 --> 00:42:26.160 otherwise in their attack would require
00:42:26.220 --> 00:42:27.950 you to compile the documentation.
00:42:27.950 --> 00:42:31.749 Yeah. You know that.
00:42:31.750 --> 00:42:35.926 Really cool. OK, I think so.
00:42:35.930 --> 00:42:40.060 That gets the user reference put together.
00:42:40.060 --> 00:42:43.066 And then we need to get user lab results
00:42:43.066 --> 00:42:44.886 properties added above related objects
00:42:44.886 --> 00:42:47.470 and get the lab results in there.
00:42:50.420 --> 00:42:53.966 If you up to line 10 and then go
00:42:53.966 --> 00:42:57.539 new line after that and add the.
00:43:04.060 --> 00:43:07.858 Region. User zones properties. That's it.
00:43:36.920 --> 00:43:40.464 And it's just going to be a region.
00:43:40.470 --> 00:43:45.740 User Lab results properties. Oh
00:43:49.600 --> 00:43:51.427 so I was. I was reading something
00:43:51.427 --> 00:43:52.829 I looked away for today.
00:44:00.450 --> 00:44:03.820 And then proper space after
00:44:03.820 --> 00:44:06.516 results in before properties.
00:44:06.520 --> 00:44:08.340 And then that works alright.
00:44:08.340 --> 00:44:10.956 And then in that region we're just going
00:44:10.956 --> 00:44:13.778 to add the public string lab results.
00:44:16.410 --> 00:44:18.665 It's going to have the
00:44:18.665 --> 00:44:21.939 get set on it and I think.
00:44:21.940 --> 00:44:23.722 That's everything and you can add
00:44:23.722 --> 00:44:25.708 the inherit doc on this as well.
00:44:40.550 --> 00:44:43.042 Alright, and let's go to the error
00:44:43.042 --> 00:44:45.954 list real quick and see if there's
00:44:45.954 --> 00:44:48.169 anything else it's complaining about.
00:44:48.170 --> 00:44:49.470 Wait for it to refresh.
00:44:49.470 --> 00:44:51.600 You might expect to rebuild.
00:44:51.600 --> 00:44:53.770 For it to refresh that.
00:44:53.770 --> 00:44:55.336 Or we just open file there's,
00:44:55.340 --> 00:44:58.028 and I'm not sure.
00:44:58.030 --> 00:44:59.595 And I saw something about
00:44:59.595 --> 00:45:00.847 the sales groups again,
00:45:00.850 --> 00:45:01.975 which is wonderful.
00:45:01.975 --> 00:45:04.600 Yeah, so it looks like we fixed
00:45:04.674 --> 00:45:06.876 all the problems we had there.
00:45:06.880 --> 00:45:08.462 So let's go ahead and open up
00:45:08.462 --> 00:45:09.704 the different quick and see
00:45:09.704 --> 00:45:10.736 what it's complaining about
00:45:10.736 --> 00:45:12.270 with the sales group stuff and
00:45:12.270 --> 00:45:13.626 most likely do what we've done
00:45:13.626 --> 00:45:15.740 with all the others which is.
00:45:15.740 --> 00:45:16.985 Just revert them.
00:45:41.550 --> 00:45:43.608 And let's look at some of the
00:45:43.608 --> 00:45:45.290 modified files for sales group.
00:45:45.290 --> 00:45:46.538 Let's get that search
00:45:46.538 --> 00:45:47.786 models that sales people.
00:45:47.790 --> 00:45:49.350 I think that's one that
00:45:49.350 --> 00:45:50.910 we may have already seen.
00:45:55.020 --> 00:45:55.954 That's weird.
00:45:55.954 --> 00:45:59.223 Why did it change that to string?
00:45:59.230 --> 00:46:00.750 Let's definitely not a string.
00:46:00.750 --> 00:46:03.790 OK, what's the other change?
00:46:03.790 --> 00:46:06.366 Adding another account ID that isn't it.
00:46:06.370 --> 00:46:09.860 OK, scroll up real quick.
00:46:09.860 --> 00:46:14.460 Awesome, the T4 is busted.
00:46:14.460 --> 00:46:16.665 We're just gonna listen over this file.
00:46:16.670 --> 00:46:18.926 We don't have time to troubleshoot
00:46:18.926 --> 00:46:21.450 why the T4 is acting dumb.
00:46:21.450 --> 00:46:25.590 And then look at.
00:46:25.590 --> 00:46:26.700 Everything else should be fine
00:46:26.700 --> 00:46:28.130 as far as we added files,
00:46:28.130 --> 00:46:29.432 we expected it to add when
00:46:29.432 --> 00:46:30.670 we ran those T fours.
00:46:33.230 --> 00:46:38.396 I think. I think we're OK too.
00:46:38.400 --> 00:46:40.152 Try another build real quick and
00:46:40.152 --> 00:46:42.059 make sure that that error is
00:46:42.059 --> 00:46:44.081 complaining about is gone with the
00:46:44.081 --> 00:46:45.888 sales properties should be good now.
00:46:49.500 --> 00:46:53.684 And then there's no way I think it's.
00:46:53.690 --> 00:46:55.760 Succeeding go to output and
00:46:55.760 --> 00:46:58.600 make sure that it did nothing.
00:46:58.600 --> 00:47:00.556 Yeah, everything's good now.
00:47:00.556 --> 00:47:03.490 Perfect so we can go ahead
00:47:03.583 --> 00:47:05.539 and do another commit.
00:47:05.540 --> 00:47:08.012 They only get ad and we
00:47:08.012 --> 00:47:09.660 change something in one,
00:47:09.660 --> 00:47:14.564 so we'll get to one data model again.
00:47:14.570 --> 00:47:17.489 And one searching I think as well.
00:47:22.710 --> 00:47:25.620 Yep, and then 03 models.
00:47:28.120 --> 00:47:30.120 Then do I get status to make sure
00:47:30.120 --> 00:47:32.458 we get everything we want? Yep, ask,
00:47:32.458 --> 00:47:34.770 commit and then we had more T force.
00:47:36.940 --> 00:47:41.088 Louisa could be more useful.
00:47:44.640 --> 00:47:49.360 Commit messages, but. That's it's fine, OK?
00:47:52.060 --> 00:47:55.396 So we have gotten the models T4 and
00:47:55.396 --> 00:47:59.077 let's go ahead and run the mapping T4.
00:47:59.080 --> 00:48:01.951 So let's search by dot TT and collapse 01
00:48:01.951 --> 00:48:05.114 and 02 layers 'cause we're done with those.
00:48:08.620 --> 00:48:10.804 Edward the mapping dot TT you
00:48:10.804 --> 00:48:13.200 don't have to run TT include,
00:48:13.200 --> 00:48:15.110 just just the mapping one.
00:48:22.850 --> 00:48:24.740 This one is a really long one.
00:48:27.360 --> 00:48:29.275 Perfect, alright, let's check the
00:48:29.275 --> 00:48:32.398 diff and see what it broke this time.
00:48:43.150 --> 00:48:44.782 OK, so I changed mapping that
00:48:44.782 --> 00:48:46.512 brand and of course it changed
00:48:46.512 --> 00:48:47.977 the sales Group One again.
00:48:50.650 --> 00:48:52.414 So open up the sales group and
00:48:52.414 --> 00:48:53.908 let's just see what it did.
00:48:53.910 --> 00:48:56.420 I bet I bet that is going to have errors.
00:48:59.090 --> 00:49:01.470 Or maybe it will nose scroll through
00:49:01.470 --> 00:49:04.454 there and see if there's any other than
00:49:04.454 --> 00:49:07.050 just other more changes. The very bottom.
00:49:12.870 --> 00:49:15.954 Those might be OK. You see?
00:49:15.954 --> 00:49:18.068 Go ahead and try to build the
00:49:18.068 --> 00:49:20.347 mapping project and see what happens.
00:49:23.940 --> 00:49:26.525 I will be pleasantly surprised
00:49:26.525 --> 00:49:29.110 if this doesn't have errors.
00:49:54.940 --> 00:49:58.180 Alright. Well, that's nice cool.
00:49:58.180 --> 00:50:00.760 I would do another commit and
00:50:00.760 --> 00:50:03.239 just say Rand mapping T fours.
00:50:03.240 --> 00:50:07.188 I'll do just get add 03 mapping.
00:50:07.190 --> 00:50:09.260 As soon as you get out of three and then
00:50:09.317 --> 00:50:11.340 tap through to get the mapping project.
00:50:11.340 --> 00:50:14.130 Yeah, and then do get status to make sure
00:50:14.130 --> 00:50:16.277 there's nothing else we left behind.
00:50:16.280 --> 00:50:17.999 Yeah, and then.
00:50:22.410 --> 00:50:28.866 Natty force. Perfect. Moving on.
00:50:28.866 --> 00:50:33.680 So that's going to get the majority of the.
00:50:33.680 --> 00:50:36.698 Tedious stuff out of the way.
00:50:36.700 --> 00:50:40.828 We're going to go ahead and run the
00:50:40.828 --> 00:50:44.167 association workflow and workflow Dot TT now.
00:50:44.170 --> 00:50:45.940 As well as workflow registry.
00:50:56.640 --> 00:51:00.175 This was a long ones as well.
00:51:00.180 --> 00:51:04.430 In run workflow dot TT. And the
00:51:04.430 --> 00:51:06.410 last one will be workflow registry.
00:51:30.020 --> 00:51:31.868 Alright, and then rebuild the workflow
00:51:31.868 --> 00:51:34.500 layer and see if it see if it errors out.
00:52:12.390 --> 00:52:14.147 OK, so we did have the workflow
00:52:14.147 --> 00:52:15.654 project failed, so go to the
00:52:15.654 --> 00:52:17.160 error list and see what happened.
00:52:28.570 --> 00:52:30.150 Interesting go and check the
00:52:30.150 --> 00:52:31.738 difference. If it added that.
00:52:35.980 --> 00:52:39.220 Might have a. It's gonna
00:52:39.220 --> 00:52:40.970 be that second one there.
00:52:40.970 --> 00:52:42.994 Six editions I think.
00:52:42.994 --> 00:52:44.050 Yeah, it don't.
00:52:44.050 --> 00:52:45.425 Is it the only change?
00:52:45.430 --> 00:52:47.008 But that's going to be the
00:52:47.008 --> 00:52:48.690 other ones that we added there
00:52:48.690 --> 00:52:50.400 that we expected it to add.
00:52:54.320 --> 00:52:57.830 I think we can probably.
00:53:00.640 --> 00:53:03.448 Revert that change. So you can
00:53:03.448 --> 00:53:06.950 right click on the left grey space.
00:53:06.950 --> 00:53:10.526 And then click use this block.
00:53:10.530 --> 00:53:12.618 Yep, and then save on the right side.
00:53:17.240 --> 00:53:18.560 Are you just clicking into
00:53:18.560 --> 00:53:20.220 control S or click on that?
00:53:20.220 --> 00:53:23.838 Yep, cool so close that one.
00:53:23.840 --> 00:53:25.175 And then there's a couple
00:53:25.175 --> 00:53:26.243 other errors in there,
00:53:26.250 --> 00:53:28.112 and I just realized what those are
00:53:28.112 --> 00:53:29.999 will take care of that real quick.
00:53:30.000 --> 00:53:32.760 Look at the changes made in shopping cart.
00:53:32.760 --> 00:53:35.916 51 change or 51 added lines.
00:53:35.920 --> 00:53:36.970 9 removed.
00:53:55.690 --> 00:53:58.390 Wonder if that's a change based
00:53:58.390 --> 00:54:00.622 on something that actually knew
00:54:00.622 --> 00:54:03.065 was an issue in an old project.
00:54:03.070 --> 00:54:06.086 Is it also possible that the changes we
00:54:06.086 --> 00:54:08.766 ignored earlier sort of bubbling up anyway?
00:54:08.770 --> 00:54:11.290 I think the the account the issues
00:54:11.290 --> 00:54:13.577 were having earlier that we were
00:54:13.577 --> 00:54:15.477 reverting where sales group related
00:54:15.477 --> 00:54:17.847 and that was mostly related to
00:54:17.847 --> 00:54:20.163 filtering by accounts and what we're
00:54:20.170 --> 00:54:23.020 seeing now is cart related completely
00:54:23.020 --> 00:54:25.620 changing the logic which this is.
00:54:25.620 --> 00:54:28.847 Most likely an expected change in this
00:54:28.847 --> 00:54:31.949 T Fortis hasn't been run in awhile,
00:54:31.950 --> 00:54:33.300 which is weird.
00:54:36.990 --> 00:54:40.427 Should be was this RX one or.
00:54:40.430 --> 00:54:41.642 Uh, no, this is.
00:54:41.642 --> 00:54:43.915 This is just fresh out of the
00:54:43.915 --> 00:54:46.207 box as it's been this project
00:54:46.207 --> 00:54:48.440 experiment not been touched since.
00:54:48.440 --> 00:54:51.142 So I just I'm just asking 'cause
00:54:51.142 --> 00:54:53.165 which branch was this cloned
00:54:53.165 --> 00:54:55.523 off of release 2020 dot 4.8.
00:54:57.640 --> 00:55:00.784 Which is not good because there should not.
00:55:00.790 --> 00:55:04.730 If you run, the T4 is on the release branch,
00:55:04.730 --> 00:55:06.700 at least in my opinion,
00:55:06.700 --> 00:55:08.280 absolutely nothing should change.
00:55:08.280 --> 00:55:10.249 They should. Nothing should change
00:55:10.249 --> 00:55:12.214 unless you've changed something yourself.
00:55:12.220 --> 00:55:15.516 So I guess that's also something worth noting
00:55:15.516 --> 00:55:18.919 for the video to just with a new client,
00:55:18.920 --> 00:55:21.278 no matter which version you choose,
00:55:21.280 --> 00:55:24.424 always start off of a fresh release branch.
00:55:24.430 --> 00:55:27.218 Never develop or anything like that, correct?
00:55:27.218 --> 00:55:30.980 Yeah, and then a future
00:55:31.066 --> 00:55:33.810 myself and or James or just someone
00:55:33.810 --> 00:55:37.529 we need to figure out why the T fours
00:55:37.529 --> 00:55:39.952 are breaking stuff in the release
00:55:39.952 --> 00:55:41.907 branch that shouldn't be happening.
00:55:41.910 --> 00:55:45.126 But anyway, I think these these changes I
00:55:45.126 --> 00:55:47.742 think are intentional because actually I
00:55:47.742 --> 00:55:51.530 was aware of a logic bug in this class.
00:55:51.530 --> 00:55:53.690 Better.
00:55:53.690 --> 00:55:54.846 I get the private.
00:55:54.846 --> 00:55:56.580 Looks like James probably solved it.
00:55:56.580 --> 00:55:58.344 Some of that logic is rearranged
00:55:58.344 --> 00:56:00.628 probably to fix that bug should be fine.
00:56:00.630 --> 00:56:02.358 I think this one is fine,
00:56:02.360 --> 00:56:04.088 but we can keep these changes.
00:56:04.090 --> 00:56:06.512 You could close this file or close
00:56:06.512 --> 00:56:08.595 this diff window and then let's
00:56:08.595 --> 00:56:10.210 look at the other ones.
00:56:10.210 --> 00:56:10.522 Uh,
00:56:10.522 --> 00:56:12.706 everything else I think is expected changes.
00:56:12.710 --> 00:56:13.338 Yeah, OK,
00:56:13.338 --> 00:56:14.908 this should all be fine.
00:56:17.770 --> 00:56:20.400 Yeah, uh, so go ahead and go back to Visual
00:56:20.467 --> 00:56:22.597 Studio and then rebuild the workflow
00:56:22.597 --> 00:56:24.879 project again and see what happens.
00:57:21.920 --> 00:57:23.954 OK, I just remembered that we
00:57:23.954 --> 00:57:26.618 actually need to do that as well, so.
00:57:26.618 --> 00:57:29.322 On the I user lab results model and
00:57:29.322 --> 00:57:32.106 the user lab results modeled both,
00:57:32.110 --> 00:57:35.080 we're going to need to add a user key
00:57:35.080 --> 00:57:37.998 and it's just going to be a string.
00:57:38.000 --> 00:57:40.828 So under related objects.
00:57:40.830 --> 00:57:45.430 After user ID add a string user key.
00:57:55.180 --> 00:57:57.385 And then you can for the docs,
00:57:57.390 --> 00:57:59.595 you can just put gets or sets
00:57:59.595 --> 00:58:01.480 the custom key of the user.
00:58:06.940 --> 00:58:09.110 Values custom keep the user.
00:58:16.440 --> 00:58:17.718 And then you'll need a period
00:58:17.718 --> 00:58:19.069 at the end of the yeah.
00:59:14.350 --> 00:59:16.270 And then make that public.
00:59:22.910 --> 00:59:24.310 Perfect, OK and that made
00:59:24.310 --> 00:59:25.710 the thing on the right.
00:59:25.710 --> 00:59:27.432 Stop complaining and I don't see
00:59:27.432 --> 00:59:29.336 any more errors in the error list
00:59:29.336 --> 00:59:31.329 so we should be able to do another
00:59:31.329 --> 00:59:33.548 rebuild and it should work this time.
00:59:33.550 --> 00:59:35.582 Yeah, I forgot about that so that's a
00:59:35.582 --> 00:59:37.691 good 6547f537-1b05-4214-9460-e718b8b0cfba
00:59:37.691 --> 00:59:39.560 will cover real quick whenever you
00:59:39.560 --> 00:59:41.415 have a related object on your entity
00:59:41.415 --> 00:59:43.350 when you create the models for it.
00:59:43.350 --> 00:59:45.030 If the T fours don't auto
00:59:45.030 --> 00:59:46.150 generate the relational stuff.
00:59:46.150 --> 00:59:47.830 Depending on how you do it,
00:59:47.830 --> 00:59:50.230 which most of the time it would probably
00:59:50.230 --> 00:59:52.338 want the way we did it, it doesn't.
00:59:52.338 --> 00:59:53.220 You don't just.
00:59:53.220 --> 00:59:54.978 Add the ID and the user.
00:59:54.980 --> 00:59:57.338 You also have to add the key and the
00:59:57.338 --> 00:59:59.382 reason for that is because it will
00:59:59.382 --> 01:00:01.449 auto generate or an auto generate.
01:00:01.450 --> 01:00:04.474 It will filter by user keys and things like
01:00:04.474 --> 01:00:07.406 that define what it's looking for in the.
01:00:07.410 --> 01:00:09.610 In the workflows, so you have to have
01:00:09.610 --> 01:00:12.308 that in there so it can do the thing cool.
01:00:12.310 --> 01:00:13.936 I think. I think it worked.
01:00:13.940 --> 01:00:16.469 Did it work?
01:00:16.470 --> 01:00:17.820 Yeah, no worries.
01:00:17.820 --> 01:00:18.720 Yeah, alright,
01:00:18.720 --> 01:00:21.324 so we can do another commit here.
01:00:24.650 --> 01:00:27.490 So we think we can just do a git add.
01:00:27.490 --> 01:00:30.220 Oh we need to get at 03.
01:00:30.220 --> 01:00:32.703 Could you change the models, yeah?
01:00:32.703 --> 01:00:34.468 Shouldn't have to touch mapping
01:00:34.468 --> 01:00:36.400 and then just get add 05?
01:00:39.110 --> 01:00:40.856 Dinner should be off, I think.
01:00:43.150 --> 01:00:45.894 One more status to be sure we left
01:00:45.894 --> 01:00:47.609 something behind. What is that?
01:00:50.620 --> 01:00:53.740 Oh yeah, you can see interface.
01:00:53.740 --> 01:00:56.617 I forgot about that alright and then
01:00:56.617 --> 01:00:59.628 you get commit ran workflow D force.
01:01:04.170 --> 01:01:08.618 Already. The light is shining at the
01:01:08.618 --> 01:01:11.487 end of the tunnel for the T force.
01:01:11.490 --> 01:01:12.906 We're getting pretty close,
01:01:12.906 --> 01:01:15.838 so you can go ahead and search our
01:01:15.838 --> 01:01:18.028 collapse 05 were done in there,
01:01:18.030 --> 01:01:21.288 and we're going to run these services dot TT.
01:01:21.290 --> 01:01:23.468 This will generate all the endpoints,
01:01:23.470 --> 01:01:24.559 basic crud stuff.
01:01:28.890 --> 01:01:30.370 Nothing too crazy here.
01:01:30.370 --> 01:01:32.590 Usually this one is the most
01:01:32.664 --> 01:01:34.769 well behaved, but we'll see.
01:01:47.440 --> 01:01:50.344 And as a tip, even if the rebuild
01:01:50.344 --> 01:01:52.127 succeeds after you run a T4,
01:01:52.130 --> 01:01:55.748 it's still a good idea to go back and.
01:01:55.750 --> 01:01:58.445 Check what changes happened, just in case.
01:02:00.630 --> 01:02:02.855 Because. A success doesn't always
01:02:02.855 --> 01:02:04.635 indicate that nothing broke,
01:02:04.640 --> 01:02:06.548 but it looks like this time
01:02:06.548 --> 01:02:08.276 nothing broke it, didn't it?
01:02:08.276 --> 01:02:10.957 All it did was add the files.
01:02:10.960 --> 01:02:12.168 And that was it.
01:02:12.168 --> 01:02:13.376 Didn't change anything else,
01:02:13.380 --> 01:02:15.501 so long as the files are generated
01:02:15.501 --> 01:02:17.019 aren't broken, should be fine.
01:02:21.530 --> 01:02:23.198 And because the services layer is
01:02:23.198 --> 01:02:25.276 at a pretty high level, it basically
01:02:25.276 --> 01:02:27.936 has to rebuild everything, so it's.
01:02:27.936 --> 01:02:30.948 It's gonna rebuild everything.
01:02:30.950 --> 01:02:34.658 And no errors, everything succeeded perfect.
01:02:34.660 --> 01:02:37.190 We love to see it so you can do a git
01:02:37.190 --> 01:02:39.556 add 06 and then commit these services.
01:02:44.400 --> 01:02:46.400 Should be the only thing.
01:02:46.400 --> 01:02:50.390 Yep. And service the force.
01:02:53.480 --> 01:02:58.344 And the. Now we're on the final step,
01:02:58.350 --> 01:03:00.654 and unfortunately this is the one
01:03:00.654 --> 01:03:02.660 that most commonly break stuff.
01:03:02.660 --> 01:03:06.980 So go ahead and run the CV API dot TT first.
01:03:32.760 --> 01:03:35.917 OK, let's go ahead and and see
01:03:35.917 --> 01:03:37.720 what exploded, if anything.
01:03:40.270 --> 01:03:42.718 OK, so see the API dot contacts was an
01:03:42.718 --> 01:03:44.401 expected change because that's where
01:03:44.401 --> 01:03:46.830 all of our endpoints are going to go.
01:03:46.830 --> 01:03:48.492 See the API dot providers or
01:03:48.492 --> 01:03:50.100 lines edit for length removed.
01:03:50.100 --> 01:03:52.186 Let's look at that one real quick.
01:03:55.330 --> 01:03:57.946 OK comment chain you can hit next difference
01:03:57.946 --> 01:04:00.944 at the top to just scroll through the
01:04:00.944 --> 01:04:03.342 actual distance that's going through the
01:04:03.342 --> 01:04:05.796 file comma change comma change comment.
01:04:05.800 --> 01:04:08.766 Just keep oh that's it. OK then that's fine,
01:04:08.766 --> 01:04:11.453 but just change comments and it doesn't
01:04:11.453 --> 01:04:14.246 work with that and check DTO classes.
01:04:14.250 --> 01:04:17.458 OK, this is related to that filtering thing
01:04:17.458 --> 01:04:20.868 that we were having issues with earlier.
01:04:20.870 --> 01:04:23.000 Where it wanted to keep
01:04:23.000 --> 01:04:24.704 adding and removing things.
01:04:24.710 --> 01:04:26.378 I don't know why this happens.
01:04:26.380 --> 01:04:28.492 I would like to know why this happens
01:04:28.492 --> 01:04:30.850 so that we can make it stop happening,
01:04:30.850 --> 01:04:32.812 but I would just right click
01:04:32.812 --> 01:04:34.630 on the left grey space.
01:04:34.630 --> 01:04:36.310 And do users on the left side and
01:04:36.310 --> 01:04:38.119 then use this text block and then
01:04:38.119 --> 01:04:39.650 same with the orange beneath it.
01:04:42.310 --> 01:04:44.240 And go to next difference.
01:04:44.240 --> 01:04:46.550 Do the same on this one.
01:04:49.340 --> 01:04:49.860 Yep.
01:04:52.410 --> 01:04:53.810 Same on the next one.
01:04:55.820 --> 01:04:58.316 Next, and all this is our new stuff,
01:04:58.320 --> 01:05:01.974 so we're going to keep these changes.
01:05:01.980 --> 01:05:05.250 Yeah, everything there is fine.
01:05:05.250 --> 01:05:09.460 OK, cool, then we're fine on that one. Save.
01:05:12.680 --> 01:05:15.200 And refresh real quick.
01:05:19.750 --> 01:05:23.174 OK, I think we're good now so that
01:05:23.174 --> 01:05:26.419 one worked one down like 400 to go.
01:05:26.420 --> 01:05:30.684 Just kidding. So go ahead and run the.
01:05:30.690 --> 01:05:31.704 Cache button widget.
01:05:31.704 --> 01:05:33.394 I don't think that's gonna
01:05:33.394 --> 01:05:35.197 change anything and that one is
01:05:35.197 --> 01:05:36.537 never broken anything for me.
01:05:36.540 --> 01:05:38.388 So I think we're probably located.
01:05:38.390 --> 01:05:40.256 Yeah, that was a super fast
01:05:40.256 --> 01:05:41.780 run run head start TT.
01:05:53.580 --> 01:05:57.442 This one might change things. See.
01:05:57.442 --> 01:06:01.140 But it doesn't. Blow stuff up.
01:06:07.450 --> 01:06:10.522 OK. Go ahead and go to tortoise git
01:06:10.522 --> 01:06:13.671 and will just make sure that the
01:06:13.671 --> 01:06:17.870 changes there are. As expected.
01:06:17.870 --> 01:06:20.468 So it looks like it changed.
01:06:23.310 --> 01:06:25.980 Painful things.
01:06:25.980 --> 01:06:28.500 So the clear cache buttons widget
01:06:28.500 --> 01:06:30.725 and stuff that's fine expecting
01:06:30.725 --> 01:06:33.539 changes 'cause we add new things.
01:06:33.540 --> 01:06:34.902 Menu dot statuses.
01:06:34.902 --> 01:06:38.693 I can't quite read with that says and
01:06:38.693 --> 01:06:42.361 type stuff reference dot TS type search
01:06:42.361 --> 01:06:45.070 controller might stop translations.
01:06:45.070 --> 01:06:47.480 Why did that happen outside?
01:06:47.480 --> 01:06:51.764 Doesn't matter that file was already there.
01:06:51.770 --> 01:06:53.866 Then type set TS.
01:06:53.866 --> 01:06:57.010 I think everything there is fine.
01:06:57.010 --> 01:07:01.132 So just gotta move on to the next one.
01:07:01.140 --> 01:07:03.280 Which is gonna be associators.
01:07:03.280 --> 01:07:04.912 Dot TT again,
01:07:04.912 --> 01:07:10.629 this one I live like right at the very well.
01:07:10.630 --> 01:07:12.618 This one I don't think I've ever
01:07:12.618 --> 01:07:14.899 seen it break anything or act funny.
01:07:14.900 --> 01:07:16.430 Usually doesn't really change anything.
01:07:16.430 --> 01:07:18.260 I think maybe maybe it does.
01:07:18.260 --> 01:07:20.546 I don't remember there's a lot
01:07:20.546 --> 01:07:23.070 of the force in the UI and.
01:07:23.070 --> 01:07:24.438 It all kind of runs together.
01:07:27.230 --> 01:07:28.688 OK, I don't think it's anything.
01:07:28.690 --> 01:07:29.915 I've been refreshing the dishes
01:07:29.915 --> 01:07:31.445 to be sure, but I think.
01:07:31.445 --> 01:07:33.300 There's still a lock next to that
01:07:33.360 --> 01:07:35.320 file instead of a red check marks.
01:07:35.320 --> 01:07:37.760 It probably didn't change anything.
01:07:37.760 --> 01:07:40.250 Yeah, I don't need anything
01:07:40.250 --> 01:07:41.744 that's perfectly fine.
01:07:41.750 --> 01:07:44.158 OK, so now all the other CV APIs
01:07:44.158 --> 01:07:46.300 were going to run those as well,
01:07:46.300 --> 01:07:47.508 so brand admin, store,
01:07:47.508 --> 01:07:49.018 store admin and so on.
01:08:21.270 --> 01:08:22.960 That's expected that it changed
01:08:22.960 --> 01:08:24.651 that one. All the others
01:08:24.651 --> 01:08:25.999 probably didn't change anything.
01:08:28.150 --> 01:08:30.574 OK, it deleted CV API dot
01:08:30.574 --> 01:08:32.920 providers which makes me nervous.
01:08:36.890 --> 01:08:39.575 So let's start with the
01:08:39.575 --> 01:08:41.723 brand admin detail classes.
01:08:41.730 --> 01:08:43.326 Like the 7th one, up down,
01:08:43.330 --> 01:08:45.549 right there beneath it types ones look
01:08:45.549 --> 01:08:47.788 at the change one above that file.
01:08:47.790 --> 01:08:52.358 Yeah. Revert these again so.
01:08:54.500 --> 01:08:57.601 Annoying that we have to. Do that OK.
01:08:57.601 --> 01:08:59.023 I think that's the only change
01:08:59.023 --> 01:09:02.568 in this file, so it's fine.
01:09:02.570 --> 01:09:04.240 See the API DTO classes.
01:09:04.240 --> 01:09:08.176 Most likely the same thing on that one.
01:09:08.180 --> 01:09:09.320 This is the one that we
01:09:09.320 --> 01:09:10.080 actually saw on Friday,
01:09:10.080 --> 01:09:13.050 so go ahead and revert that one as well.
01:09:13.050 --> 01:09:18.410 I'm gonna use the left side and save.
01:09:18.410 --> 01:09:19.680 See what changed in there.
01:09:19.680 --> 01:09:21.186 It says it deleted the file,
01:09:21.190 --> 01:09:23.214 so let's see what endpoint is in here.
01:09:25.240 --> 01:09:27.170 That's fine, well, not really,
01:09:27.170 --> 01:09:29.100 but it's also it's fine.
01:09:29.100 --> 01:09:31.030 I don't think that on
01:09:31.030 --> 01:09:32.960 scared provider is in core,
01:09:32.960 --> 01:09:36.184 so that just tells me that these T-47
01:09:36.184 --> 01:09:39.367 been run since arcs one was merged.
01:09:39.370 --> 01:09:40.360 Which is probably why a
01:09:40.360 --> 01:09:41.350 bunch of stuff is broken.
01:09:46.630 --> 01:09:47.983 So that's fine.
01:09:47.983 --> 01:09:50.689 We don't need that input anyway.
01:09:50.690 --> 01:09:52.724 Check on that one that says
01:09:52.724 --> 01:09:54.898 it removed like 200 lines and
01:09:54.898 --> 01:09:57.118 that makes me a little nervous.
01:09:57.120 --> 01:09:58.630 Yes, so revert that one.
01:10:03.770 --> 01:10:05.879 The next difference?
01:10:09.610 --> 01:10:12.952 That, I think is fine. Sales order
01:10:12.952 --> 01:10:14.757 page results. That seems fine.
01:10:18.460 --> 01:10:21.568 Why was that? Sales order search.
01:10:21.570 --> 01:10:22.814 My didn't remove the
01:10:22.814 --> 01:10:24.058 sales order search model.
01:10:24.060 --> 01:10:25.620 That seems not right actually.
01:10:25.620 --> 01:10:29.155 Wait go to previous difference real quick.
01:10:29.160 --> 01:10:31.365 No, I removed that yeah and that back in.
01:10:31.370 --> 01:10:34.387 I don't know why I did that.
01:10:34.390 --> 01:10:35.524 The next difference,
01:10:35.524 --> 01:10:37.792 and then add that back in.
01:10:37.800 --> 01:10:39.108 And then next.
01:10:43.350 --> 01:10:45.225 Subscription history search.
01:10:45.225 --> 01:10:49.770 Warner's came from. Hey Brandon.
01:10:49.770 --> 01:10:54.607 I actually have the RX ones are.
01:10:54.610 --> 01:10:57.340 Are these subscription history stuff
01:10:57.340 --> 01:11:01.241 or these actually in the like outside
01:11:01.241 --> 01:11:04.463 of the RX1 client override project?
01:11:04.470 --> 01:11:07.250 Or they were? Yeah,
01:11:07.250 --> 01:11:10.725 outside of the override existing?
01:11:10.730 --> 01:11:12.298 I'm not sure why it's removing them.
01:11:16.350 --> 01:11:18.302 Let's just revert this.
01:11:18.302 --> 01:11:21.250 So yeah, use that text block and
01:11:21.250 --> 01:11:23.830 I take the whole thing there.
01:11:23.830 --> 01:11:26.320 We go. Next difference, same thing.
01:11:26.320 --> 01:11:29.930 Use that left text block.
01:11:29.930 --> 01:11:31.746 And that's it, OK?
01:11:31.746 --> 01:11:34.470 So save that one and close.
01:11:34.470 --> 01:11:38.438 No, I'm the next one service class, yes.
01:11:38.438 --> 01:11:40.578 OK, that's expected because the
01:11:40.578 --> 01:11:42.740 providers in point is gone.
01:11:42.740 --> 01:11:44.840 Go to next difference and see
01:11:44.840 --> 01:11:46.940 what that one is. Same thing.
01:11:46.940 --> 01:11:48.690 OK, close that that's acceptable.
01:11:48.690 --> 01:11:50.790 Next one, probably the same change.
01:11:50.790 --> 01:11:52.548 Yeah, that's fine.
01:11:52.548 --> 01:11:55.478 And then the last one.
01:11:55.480 --> 01:11:56.424 Awesome yeah.
01:11:56.424 --> 01:12:00.200 OK, run that very last one vendor admin,
01:12:00.200 --> 01:12:01.452 which is probably not
01:12:01.452 --> 01:12:02.704 going to change anything.
01:12:08.360 --> 01:12:12.434 Yeah, we'll see where this puts us.
01:12:12.440 --> 01:12:14.400 Or it may change selected DTO classes
01:12:14.400 --> 01:12:17.021 like it did on the other and let the
01:12:17.021 --> 01:12:19.250 river those dumb changes. Refresh.
01:12:21.770 --> 01:12:23.858 Yeah, sure did.
01:12:23.860 --> 01:12:27.836 Under admin DTO classes, the very last one.
01:12:27.840 --> 01:12:32.299 Open that up and revert said changes.
01:12:32.300 --> 01:12:36.780 And say. Yeah, not happy there yet,
01:12:36.780 --> 01:12:41.868 but it's fine. OK refresh one more time.
01:12:41.870 --> 01:12:44.042 And go alright, we can probably
01:12:44.042 --> 01:12:46.940 commit on this, but before we do that,
01:12:46.940 --> 01:12:49.856 actually let's do a gulp build on the front
01:12:49.856 --> 01:12:52.727 end and make sure that everything works.
01:12:52.730 --> 01:12:57.122 So we already have a a command prompt open.
01:12:57.130 --> 01:12:59.234 It's actually going to be in that folder,
01:12:59.240 --> 01:13:02.600 so go to your. PowerShell.
01:13:02.600 --> 01:13:05.440 CD and Type CD 08.
01:13:05.440 --> 01:13:09.388 In the Tab tab, again enter.
01:13:09.390 --> 01:13:12.126 But then you should be able to gulp,
01:13:12.130 --> 01:13:13.490 build, gulp, space build.
01:13:18.660 --> 01:13:21.660 I will see if we get any errors.
01:13:21.660 --> 01:13:23.804 Also, I think the text that says how
01:13:23.804 --> 01:13:26.271 long the build took is the same color
01:13:26.271 --> 01:13:28.350 as the background. Just says after.
01:13:30.830 --> 01:13:33.510 No, it's just not there.
01:13:33.510 --> 01:13:36.640 Down my computer too sometimes.
01:13:36.640 --> 01:13:39.466 By the way, you're a you have text selected,
01:13:39.470 --> 01:13:41.348 so it's halting it right click.
01:13:43.880 --> 01:13:45.440 Just real quick on that,
01:13:45.440 --> 01:13:46.688 so whenever you're writing
01:13:46.688 --> 01:13:47.936 something in Windows Terminal,
01:13:47.940 --> 01:13:50.117 make sure you never have something selected.
01:13:50.120 --> 01:13:52.696 She wants the program to keep running
01:13:52.696 --> 01:13:54.199 because essentially counseled outright
01:13:54.199 --> 01:13:56.544 line or any other similar thing is
01:13:56.544 --> 01:13:58.378 actually blocking call and it will block
01:13:58.378 --> 01:14:01.000 for as long as it takes to actually get
01:14:01.000 --> 01:14:03.280 something out to the console buffer.
01:14:03.280 --> 01:14:06.097 So for example, if you have that that window
01:14:06.097 --> 01:14:08.520 open and you have something selected,
01:14:08.520 --> 01:14:10.928 any program which tries to rights or
01:14:10.928 --> 01:14:13.297 just play any console that writes
01:14:13.297 --> 01:14:15.817 method will wait until it's actually
01:14:15.817 --> 01:14:18.375 able to send something out to that.
01:14:18.380 --> 01:14:19.556 Which can be very annoying as
01:14:19.556 --> 01:14:20.900 you'll sit there for five minutes,
01:14:20.900 --> 01:14:22.580 but I realize it that that that work,
01:14:22.580 --> 01:14:23.630 all it takes it out.
01:14:23.630 --> 01:14:25.820 Or does it never actually started.
01:14:25.820 --> 01:14:26.880 He's been sitting there waiting
01:14:26.880 --> 01:14:27.516 for the console.
01:14:30.700 --> 01:14:32.404 It's a bottom line.
01:14:32.404 --> 01:14:35.022 Just as an example, like highlight some
01:14:35.022 --> 01:14:37.150 text in the PowerShell window real quick,
01:14:37.150 --> 01:14:39.166 or just highlight some space if you
01:14:39.166 --> 01:14:41.036 ever have highlighted anything in a
01:14:41.036 --> 01:14:42.616 PowerShell or command prompt window.
01:14:42.620 --> 01:14:44.918 Whatever you're doing is just not
01:14:44.918 --> 01:14:47.690 going to run. So like Jonathan said,
01:14:47.690 --> 01:14:50.929 you can just right Click to clear it.
01:14:50.930 --> 01:14:52.994 But I should say I think I actually
01:14:52.994 --> 01:14:55.710 copies it, not just clearing it.
01:14:55.710 --> 01:14:58.479 So careful about.
01:14:58.480 --> 01:15:00.310 About whatever was in your clipboard,
01:15:00.310 --> 01:15:02.200 but knowing that you also had Windows
01:15:02.200 --> 01:15:04.342 V to see the clipboard history and
01:15:04.342 --> 01:15:06.720 get back to whatever you had before.
01:15:09.800 --> 01:15:11.498 Alright, let's also good to know.
01:15:11.500 --> 01:15:13.362 But yeah, if you ever like running
01:15:13.362 --> 01:15:14.890 something in the command line,
01:15:14.890 --> 01:15:16.218 especially something that takes
01:15:16.218 --> 01:15:18.210 a while and you're sitting there
01:15:18.264 --> 01:15:19.769 wondering why it's not going.
01:15:19.770 --> 01:15:22.500 You can make sure that you didn't
01:15:22.500 --> 01:15:24.470 accidentally text or something.
01:15:24.470 --> 01:15:27.480 OK, so gold filled worked.
01:15:27.480 --> 01:15:30.180 So that should be it.
01:15:30.180 --> 01:15:32.382 You should be able to commit
01:15:32.382 --> 01:15:34.680 this last change and that's it.
01:15:34.680 --> 01:15:37.602 We've now added a new schema
01:15:37.602 --> 01:15:40.459 so you can get add 08.
01:15:40.460 --> 01:15:42.737 And we're just going to get the UI folder,
01:15:42.740 --> 01:15:45.270 so tab one more time and then do get status.
01:15:47.870 --> 01:15:49.900 Yep, an will leave the skin behind
01:15:49.900 --> 01:15:51.654 from this commit and so I can
01:15:51.654 --> 01:15:53.500 do a git commit. Ran UI T force.
01:16:00.010 --> 01:16:02.198 Exciting, so that's it.