| Topic | Presenter | Summary | Duration |
| -------------------------------------- | ------------------ | --------------------------------------------------------------------------------------------------------------------- | -------- |
| Progress Bar for the Progress Importer | Various Developers | This is the second part of a Friday Dev Training where we worked on adding the Progress Bar for the Product Importer. | 1:01:42 |00:00:07.180 --> 00:00:10.326 OK, uh. Was expecting to see
00:00:10.326 --> 00:00:12.680 this but I I I am seeing it.
00:00:12.680 --> 00:00:14.768 You are running into things that
00:00:14.768 --> 00:00:17.120 I warrant Eric and Murphy about.
00:00:19.600 --> 00:00:23.764 Develop. Contains the updated SDK
00:00:23.764 --> 00:00:27.338 style CSS project now. That auto target
00:00:30.020 --> 00:00:30.970 both.net472and.net 5.
00:00:30.970 --> 00:00:32.870 Some of those projects,
00:00:32.870 --> 00:00:35.854 like the service one and the data model,
00:00:35.860 --> 00:00:37.168 only work with 472,
00:00:37.168 --> 00:00:39.130 so they're they're they're more targeted,
00:00:39.130 --> 00:00:41.503 but if you had previously built your
00:00:41.503 --> 00:00:44.235 folder with with code and then pulled
00:00:44.235 --> 00:00:46.295 the updated develop branch afterward,
00:00:46.300 --> 00:00:48.084 it's going to confuse some of that stuff
00:00:48.084 --> 00:00:49.696 from where where some of this stuff
00:00:49.696 --> 00:00:51.170 is supposed to actually be stored.
00:00:51.170 --> 00:00:53.162 Uh, and the only way to really satisfy
00:00:53.162 --> 00:00:55.171 it is to like wipe everything and
00:00:55.171 --> 00:00:57.189 like reset back to back the core,
00:00:57.190 --> 00:00:58.450 or like do a fresh check out
00:00:58.450 --> 00:00:58.990 to another folder.
00:01:03.360 --> 00:01:04.824 So that we just need to remove the
00:01:04.824 --> 00:01:07.160 bin and object folders, right?
00:01:07.160 --> 00:01:09.400 We tried that, did not.
00:01:09.400 --> 00:01:10.420 It does not fix it.
00:01:10.420 --> 00:01:13.120 Greg had this issue and I was able to
00:01:13.120 --> 00:01:15.142 reproduce it on my local and deleting
00:01:15.142 --> 00:01:17.325 the bin and obj folders didn't do
00:01:17.325 --> 00:01:19.698 anything and you delete bin obj dot
00:01:19.700 --> 00:01:22.787 VS like everything that might fix it.
00:01:22.790 --> 00:01:24.176 Did you also shut down Visual
00:01:24.176 --> 00:01:25.649 Studio while you were doing that?
00:01:25.650 --> 00:01:28.090 Yes, just make sure.
00:01:28.090 --> 00:01:31.022 Yeah yeah, maybe maybe deleting like
00:01:31.022 --> 00:01:34.495 VS and every bin and obj folder might
00:01:34.495 --> 00:01:37.134 get it because that should clear
00:01:37.134 --> 00:01:39.440 basically any persistent information
00:01:39.440 --> 00:01:43.610 about the previous build or anything.
00:01:43.610 --> 00:01:45.320 Here.
00:01:45.320 --> 00:01:47.462 Your tortoise git was saying that your
00:01:47.462 --> 00:01:49.575 re sharper cache file with green as
00:01:49.575 --> 00:01:51.780 if it's been committed to source control,
00:01:51.780 --> 00:01:52.803 which is weird.
00:01:52.803 --> 00:01:54.508 That shouldn't be in source.
00:02:18.590 --> 00:02:21.450 And they also set up a dot VS folder was
00:02:21.521 --> 00:02:24.456 green, but I just pulled up the gift.
00:02:24.460 --> 00:02:26.505 I just pull up stuff skit and
00:02:26.505 --> 00:02:28.395 it doesn't seem to have the
00:02:28.395 --> 00:02:30.379 obvious folder in the repository.
00:02:30.380 --> 00:02:32.444 Yes, which is why it's weird that his
00:02:32.444 --> 00:02:34.436 local there is showing that it's there.
00:02:34.440 --> 00:02:36.612 Yeah, can you just right click
00:02:36.612 --> 00:02:39.378 there in this so it is developed?
00:02:39.380 --> 00:02:41.186 But is this a fresh check out
00:02:41.186 --> 00:02:42.260 that you just did?
00:02:42.260 --> 00:02:44.448 Or is this another?
00:02:44.448 --> 00:02:47.730 Check out that you just upgraded.
00:02:51.690 --> 00:02:53.016 And if you're talking, you're muted.
00:02:58.350 --> 00:03:00.775 Yes, I just checked this
00:03:00.775 --> 00:03:04.200 out just now. It's strange.
00:03:09.620 --> 00:03:11.335 Uhm, if we don't resolve this in
00:03:11.335 --> 00:03:13.570 the next couple minutes, uhm, James,
00:03:13.570 --> 00:03:16.737 have you done the 2021.3 soft thing
00:03:16.737 --> 00:03:19.864 yet from from the four or five clients
00:03:19.864 --> 00:03:23.310 that were there? No, I have not.
00:03:23.310 --> 00:03:26.870 But if we just did it on release 2021.1 and
00:03:26.870 --> 00:03:31.488 then we can cherry pick that into develop,
00:03:31.490 --> 00:03:34.634 that's just OK. And Brendan do
00:03:34.634 --> 00:03:37.620 get status double dash ignored.
00:03:37.620 --> 00:03:40.566 That'll give you more than just.
00:03:40.570 --> 00:03:41.860 But I'll tell you everything that
00:03:41.860 --> 00:03:43.169 you could possibly clean if you did,
00:03:43.170 --> 00:03:45.061 I think it was dash. FDX.
00:03:45.061 --> 00:03:50.407 Yeah. So go ahead and start.
00:03:50.410 --> 00:03:53.020 Because let's just try like removing
00:03:53.020 --> 00:03:55.480 everything that could possibly be cached.
00:03:55.480 --> 00:03:57.400 Uhm, close up as Visual Studio
00:03:57.400 --> 00:03:58.040 already closed.
00:03:58.040 --> 00:04:01.136 I can't quite see down in the taskbar there.
00:04:01.140 --> 00:04:02.939 Yeah, it's going to kill that thing
00:04:02.939 --> 00:04:04.841 he likes to hang onto weird stuff
00:04:04.841 --> 00:04:06.890 and act like it's the build system.
00:04:14.590 --> 00:04:17.080 Uhm, was that other one also?
00:04:17.080 --> 00:04:19.184 This this project or is that just another
00:04:19.184 --> 00:04:20.887 project that was a separate project?
00:04:20.890 --> 00:04:24.695 OK, just making sure. OK, so uhm,
00:04:24.695 --> 00:04:29.430 I think those get clean dash F DX.
00:04:29.430 --> 00:04:32.510 It's like the most complete clean I've found.
00:04:38.980 --> 00:04:42.530 Who? That should be everything
00:04:42.530 --> 00:04:43.550 that has been ignored,
00:04:43.550 --> 00:04:45.623 including directories, etc.
00:04:45.623 --> 00:04:49.078 Remember it correctly is this.
00:04:49.080 --> 00:04:50.459 Yeah, I was gonna say that's gonna
00:04:50.459 --> 00:04:51.999 wipe out your solution items to you.
00:04:52.000 --> 00:04:54.580 Just deleted all solution.
00:04:54.580 --> 00:04:58.042 Oh my gosh, great mission values Greg.
00:04:58.042 --> 00:04:58.752 This is why you should
00:04:58.752 --> 00:04:59.698 listen to me when I tell you.
00:04:59.700 --> 00:05:02.549 Just open up a PowerShell for granted.
00:05:02.550 --> 00:05:05.232 The power still make sure it's in admin mode.
00:05:05.240 --> 00:05:06.338 Now I'm going to paste this
00:05:06.338 --> 00:05:07.070 command in the chat.
00:05:07.070 --> 00:05:08.678 What you just paste it there.
00:05:08.680 --> 00:05:10.128 I'll paste this command.
00:05:18.700 --> 00:05:21.444 Don't read the command, don't look at it.
00:05:21.450 --> 00:05:23.418 Close your eyes when you copy
00:05:23.420 --> 00:05:26.740 pin number, that's PTSD inducing.
00:05:32.610 --> 00:05:35.186 Alright, uhm I guess can be really quick.
00:05:35.190 --> 00:05:38.078 Check one of the locations that we would
00:05:38.078 --> 00:05:41.106 find a bin or object folder just to.
00:05:41.110 --> 00:05:45.286 Make sure that it's not there that works.
00:05:45.290 --> 00:05:47.620 Looks good. Yeah, it's fine.
00:05:52.250 --> 00:05:56.430 21 horse and now we're setting up flirty,
00:05:56.430 --> 00:06:00.368 slow Clover again. Yeah you wanna also.
00:06:00.368 --> 00:06:02.714 I guess the rest of US code
00:06:02.714 --> 00:06:04.566 folder wouldn't matter here.
00:06:04.570 --> 00:06:06.425 Uh, just try to look through there
00:06:06.425 --> 00:06:11.040 to see if there is anything else.
00:06:11.040 --> 00:06:13.304 Now it's like if you're going into like
00:06:13.304 --> 00:06:15.024 a business logic, and then the workload
00:06:15.024 --> 00:06:16.750 one and there's no bitter obj there.
00:06:16.750 --> 00:06:18.970 You're probably fine now.
00:06:18.970 --> 00:06:20.265 Yeah, that's what I was gonna say.
00:06:20.270 --> 00:06:24.210 Yeah, you're clear, you're good.
00:06:24.210 --> 00:06:27.346 Yeah, so I guess I'll pop that command
00:06:27.350 --> 00:06:32.026 speed reading about Islam. In the chat.
00:06:32.030 --> 00:06:32.910 You're gonna run that command.
00:06:32.910 --> 00:06:34.890 Just copy solution in his first.
00:06:34.890 --> 00:06:36.525 Yep. Yep, and you're also
00:06:36.525 --> 00:06:38.897 going to need to put your, uh,
00:06:38.897 --> 00:06:40.739 you're also going to put your
00:06:40.739 --> 00:06:42.518 rewrite configs back in your skins.
00:06:44.760 --> 00:06:47.980 Well, this is freshly checked out, uhm?
00:06:47.980 --> 00:06:49.475 Solution so I don't have
00:06:49.475 --> 00:06:51.370 any of that to begin with.
00:06:51.370 --> 00:06:52.486 You should have them in the.
00:06:52.490 --> 00:06:54.810 If it's just a release 2021,
00:06:54.810 --> 00:06:56.910 you should have them in your.
00:06:56.910 --> 00:06:58.278 A clarity skin.
00:07:05.590 --> 00:07:07.192 Like you have to put them back in there.
00:07:09.460 --> 00:07:12.050 Or you'll get a URL rewrite errors.
00:07:14.240 --> 00:07:16.490 There be 07 portal storefront skins.
00:07:19.610 --> 00:07:21.923 Do you mean that they come with the cloud?
00:07:21.930 --> 00:07:24.290 They don't. They have to copy them in.
00:07:24.290 --> 00:07:25.670 So under the clarity skin,
00:07:25.670 --> 00:07:27.532 if you don't have if you copy
00:07:27.532 --> 00:07:29.279 from the set config folder,
00:07:29.280 --> 00:07:31.793 they will get dropped into the correct
00:07:31.793 --> 00:07:33.710 place for queries get correct.
00:07:33.710 --> 00:07:34.586 And yeah, they're not in there,
00:07:34.590 --> 00:07:35.242 so you'll have to.
00:07:35.242 --> 00:07:36.706 I mean, yeah, like James said,
00:07:36.706 --> 00:07:38.845 you can just go copy like 2021.1.
00:07:38.845 --> 00:07:41.455 Uhm from self configs and paste
00:07:41.455 --> 00:07:44.468 it into the the root and it'll.
00:07:44.470 --> 00:07:45.854 It'll put all the stuff back where you
00:07:45.854 --> 00:07:47.597 need it and you just update your app
00:07:47.597 --> 00:07:48.839 settings and connection strings I guess.
00:07:48.840 --> 00:07:51.260 Couldn't we also just run
00:07:51.260 --> 00:07:53.196 the quick install script?
00:07:53.200 --> 00:07:55.240 In that does all the same stuff anyway,
00:07:55.240 --> 00:07:57.304 I think it would be faster to just.
00:07:57.310 --> 00:07:58.516 I mean he's already got all
00:07:58.516 --> 00:07:59.649 the IS and everything set up.
00:07:59.650 --> 00:08:02.004 We just need to pull the package
00:08:02.004 --> 00:08:04.668 the settings back in and fix
00:08:04.668 --> 00:08:06.849 the connection string and stuff.
00:08:06.850 --> 00:08:08.218 You can copy since the the
00:08:08.218 --> 00:08:09.420 folder passed all the same,
00:08:09.420 --> 00:08:12.311 you can just copy the entire sub
00:08:12.311 --> 00:08:14.738 folder and paste it at the UM.
00:08:14.740 --> 00:08:14.932 Yeah,
00:08:14.932 --> 00:08:16.084 like you can copy right there
00:08:16.084 --> 00:08:17.484 and then just paste that at the
00:08:17.484 --> 00:08:18.660 same level as your stuff folder.
00:08:18.660 --> 00:08:20.011 I wouldn't copy Web 9 if your
00:08:20.011 --> 00:08:21.398 web 9 already working that way.
00:08:21.400 --> 00:08:23.228 You don't overwrite good
00:08:23.228 --> 00:08:25.056 connection string over there.
00:08:25.060 --> 00:08:27.314 Oh, you didn't have a web night?
00:08:27.320 --> 00:08:29.456 Yeah, I just checked out stuff.
00:08:29.460 --> 00:08:30.336 Oh OK,
00:08:30.336 --> 00:08:31.650 very first time.
00:08:35.610 --> 00:08:38.020 Never worked on self before.
00:08:38.020 --> 00:08:39.370 Not in your whole life.
00:08:44.380 --> 00:08:49.586 Got my things. OK, so now what is this?
00:08:49.590 --> 00:08:51.453 Uh, I need to open thing in a certain
00:08:51.453 --> 00:08:53.378 way to not have the bad thing happen.
00:08:57.000 --> 00:08:59.002 On release Branch, you're fine, really.
00:08:59.002 --> 00:09:00.214 Yeah, you don't have to worry
00:09:00.214 --> 00:09:01.990 about anything here, so fire away.
00:09:15.220 --> 00:09:16.966 Is that something I can do?
00:09:16.970 --> 00:09:17.850 Can I get my money?
00:09:29.920 --> 00:09:31.228 I know James mentioned it at
00:09:31.228 --> 00:09:32.984 the top of this, but Brendan,
00:09:32.984 --> 00:09:36.078 can you summarize why that just happened?
00:09:36.080 --> 00:09:39.398 Brendan Lion or Flare DNS doesn't matter.
00:09:39.400 --> 00:09:41.140 The reason it happened is because,
00:09:41.140 --> 00:09:44.836 UM, if you check out develop as it
00:09:44.836 --> 00:09:47.810 currently is into a set folder.
00:09:47.810 --> 00:09:52.114 That has already built in the past.
00:09:52.114 --> 00:09:55.282 Visual Studio gets very confused about
00:09:55.282 --> 00:09:58.319 where things are supposed to be.
00:09:58.320 --> 00:10:02.290 Come and uh.
00:10:02.290 --> 00:10:04.200 Yeah, basically because there's a.
00:10:04.200 --> 00:10:05.480 It's because there's a change
00:10:05.480 --> 00:10:06.972 in the output path, right?
00:10:06.972 --> 00:10:08.820 Like, right between either
00:10:08.820 --> 00:10:12.798 going to net 472 or net 5.
00:10:12.800 --> 00:10:15.592 So if you if you've built before and
00:10:15.592 --> 00:10:18.037 you check out develop right now,
00:10:18.040 --> 00:10:21.380 you will you will.
00:10:21.380 --> 00:10:25.580 You'll be very sad. But, uh.
00:10:25.580 --> 00:10:29.630 That's that's that's why that exploded.
00:10:29.630 --> 00:10:30.986 And then just go to jail.
00:10:30.990 --> 00:10:31.569 He's got a.
00:10:31.569 --> 00:10:32.920 He's got a good solution for you.
00:10:35.610 --> 00:10:37.230 Yeah, he'll make your
00:10:37.230 --> 00:10:38.850 computer nice and clean.
00:10:38.850 --> 00:10:42.730 Yeah, and then he'll be like bye bye.
00:10:42.730 --> 00:10:43.582 He'll give you up,
00:10:43.582 --> 00:10:44.860 he'll give you a really cool
00:10:44.908 --> 00:10:46.232 really cool recursive PowerShell
00:10:46.232 --> 00:10:47.887 script that goes through every
00:10:47.887 --> 00:10:49.421 directory on your computer and runs
00:10:49.421 --> 00:10:51.176 that command to just wipe every
00:10:51.176 --> 00:10:54.156 git repository back to default.
00:10:54.160 --> 00:10:55.426 Do not use the PowerShell script
00:10:55.426 --> 00:10:56.710 that I use bash at least.
00:11:00.180 --> 00:11:01.070 I'm glad you didn't deny
00:11:01.070 --> 00:11:02.190 that you would ever do that.
00:11:02.190 --> 00:11:03.945 You're just like I wouldn't
00:11:03.945 --> 00:11:05.349 do that with PowerShell.
00:11:05.350 --> 00:11:11.330 Alright, Greg Dash Dash S Club star.
00:11:11.330 --> 00:11:13.026 It's not his PC, so he doesn't have
00:11:13.026 --> 00:11:14.550 to worry about it, don't forget.
00:11:19.700 --> 00:11:21.860 I'm just teaching people make UPS.
00:11:24.240 --> 00:11:26.018 You don't make it back up, it's your problem.
00:11:28.730 --> 00:11:30.550 Dash final Dash final final
00:11:30.550 --> 00:11:32.930 Dash final final dash V4 Dash 6.
00:11:39.170 --> 00:11:41.818 Restoring you get packages.
00:11:41.820 --> 00:11:44.508 Yeah, try that. See if the visual
00:11:44.508 --> 00:11:45.660 schedules currently restoring.
00:11:45.660 --> 00:11:47.106 So just give it a moment.
00:11:47.110 --> 00:11:49.982 It'll kick back on the menu a few
00:11:49.982 --> 00:11:52.699 times until it becomes a selectable.
00:11:52.700 --> 00:11:54.410 It's yeah, it's restoring already.
00:11:54.410 --> 00:11:55.832 You can see in the bottom left of progress.
00:11:55.840 --> 00:11:56.932 That said, restoring package
00:11:56.932 --> 00:11:58.297 something something a moment ago,
00:11:58.300 --> 00:12:02.500 so it's it's installing ahead of you.
00:12:02.500 --> 00:12:04.980 You could also just build and then that
00:12:04.980 --> 00:12:07.584 would kick out for a store no matter what.
00:12:07.590 --> 00:12:09.298 Haven't you done enough?
00:12:13.170 --> 00:12:15.314 No, I was actually thinking of having a
00:12:15.314 --> 00:12:17.895 pop up with our counselors do that build.
00:12:17.900 --> 00:12:20.000 Don't you dare I, actually?
00:12:20.000 --> 00:12:21.626 Uh, that's how that's how the
00:12:21.626 --> 00:12:22.710 installer triggers the build.
00:12:22.710 --> 00:12:24.742 It it grabs the Ms build path and
00:12:24.742 --> 00:12:26.800 just runs it right off so you know,
00:12:26.800 --> 00:12:28.520 you could open the installer and it would.
00:12:28.520 --> 00:12:32.080 It would get you get you right as rain real
00:12:32.168 --> 00:12:34.663 fast and disgusted by logic as going to
00:12:34.663 --> 00:12:36.829 find that particular instance of Ms build.
00:12:36.830 --> 00:12:38.142 That probably comes from
00:12:38.142 --> 00:12:39.454 the Visual Studio install.
00:12:39.460 --> 00:12:40.483 Yes it does.
00:12:40.483 --> 00:12:41.847 I have discussed it.
00:12:44.820 --> 00:12:47.579 How to build the whole solution I just got?
00:12:47.579 --> 00:12:49.487 This part is that it also, uh,
00:12:49.487 --> 00:12:51.449 exactly the same way as the,
00:12:51.450 --> 00:12:53.230 uh, the quick install script.
00:12:53.230 --> 00:12:55.140 It downloads Nougat locally and
00:12:55.140 --> 00:12:58.366 to a new git folder so that it
00:12:58.366 --> 00:13:00.426 can restore the packages because.
00:13:00.430 --> 00:13:03.020 Visual Studio doesn't expose that at all.
00:13:03.020 --> 00:13:05.138 It's all built in. Yeah, I guess,
00:13:05.138 --> 00:13:07.050 are we at the point where we can
00:13:07.118 --> 00:13:08.987 just say DOT net build in there?
00:13:08.990 --> 00:13:10.187 I mean we are trying to make
00:13:10.187 --> 00:13:11.379 this thing not that five ready,
00:13:11.380 --> 00:13:14.200 So what until at least the
00:13:14.200 --> 00:13:16.080 beginning of next year?
00:13:16.080 --> 00:13:17.627 Thorn 'cause once we can do that,
00:13:17.630 --> 00:13:18.668 we don't have to worry about
00:13:18.668 --> 00:13:19.956 any of that crazy stuff.
00:13:19.956 --> 00:13:22.592 I've got to be able to support.net
00:13:22.592 --> 00:13:24.916 472 until we are fully certain that
00:13:24.916 --> 00:13:27.306 we are available on DOT at 5 or 6.
00:13:30.880 --> 00:13:36.528 You want, UM, a get cash client async.
00:13:42.550 --> 00:13:43.420 Only one man.
00:13:48.080 --> 00:13:48.570 Alright.
00:13:53.410 --> 00:13:55.080 It only exists you liar.
00:13:58.980 --> 00:14:00.855 It's thinking it hasn't even
00:14:00.855 --> 00:14:02.585 loaded system, so 'cause you
00:14:02.585 --> 00:14:04.535 don't have like task or anything.
00:14:04.540 --> 00:14:06.692 I think you need to expand your 06
00:14:06.692 --> 00:14:08.579 services folder and then go over to
00:14:08.579 --> 00:14:10.200 the references and mess with that.
00:14:10.200 --> 00:14:11.670 'cause this dot menu is just
00:14:11.670 --> 00:14:12.910 gonna freak out for now.
00:14:16.810 --> 00:14:18.476 So expand your, uh, your services folder
00:14:18.476 --> 00:14:20.195 and let's get those yellow banks fixed
00:14:20.195 --> 00:14:22.248 over there so that this thing can be happy.
00:14:24.920 --> 00:14:26.368 Add an expand references.
00:14:31.830 --> 00:14:33.072 Yeah, it's freaking out on all
00:14:33.072 --> 00:14:34.240 that stuff for some reason.
00:14:36.560 --> 00:14:38.582 I managed to get packages from
00:14:38.582 --> 00:14:40.435 right there, and let's see if it
00:14:40.435 --> 00:14:41.910 will help refresh them load that.
00:14:50.150 --> 00:14:52.908 Click on the references folder itself again,
00:14:52.910 --> 00:14:54.074 and then click the refresh button
00:14:54.074 --> 00:14:55.696 at the top and see if it shared it.
00:14:58.990 --> 00:14:59.930 There's a refresh button on
00:14:59.930 --> 00:15:00.900 the toolbar up there, yeah?
00:15:03.270 --> 00:15:04.916 There it goes so fast, yeah,
00:15:04.916 --> 00:15:06.296 well it should be better.
00:15:13.500 --> 00:15:16.800 It's not just triggering a build.
00:15:16.800 --> 00:15:18.100 Just like right there, right?
00:15:18.100 --> 00:15:19.648 There is something, yeah.
00:15:21.970 --> 00:15:22.948 I will have to catch up.
00:15:29.270 --> 00:15:31.440 Had such a nice PowerShell command ready.
00:16:27.350 --> 00:16:27.890 Ah.
00:16:33.320 --> 00:16:35.130 What do I pass this?
00:16:44.850 --> 00:16:47.634 We're going to want to build a key.
00:16:47.640 --> 00:16:49.640 That we're going to use the
00:16:49.640 --> 00:16:50.790 prefix part will be fine,
00:16:50.790 --> 00:16:53.207 but we should probably add a.
00:16:53.207 --> 00:16:59.140 As a prefix to the filename, uh, the.
00:16:59.140 --> 00:17:02.432 Is there any user ID and like
00:17:02.432 --> 00:17:04.476 import service or something?
00:17:07.230 --> 00:17:09.730 So the request won't have that, it'll be a.
00:17:12.020 --> 00:17:15.140 I was going to lie and say far he equal to.
00:17:17.660 --> 00:17:20.928 Has opened a string.
00:17:20.930 --> 00:17:23.700 Then say product import colon.
00:17:26.220 --> 00:17:27.768 Are you colon?
00:17:30.930 --> 00:17:35.590 Then we're going to add a opening.
00:17:35.590 --> 00:17:37.486 A brace so that we could
00:17:37.486 --> 00:17:39.710 do in order for his string.
00:17:39.710 --> 00:17:40.880 When I put the dollar sign
00:17:40.880 --> 00:17:42.145 at the front of the strings
00:17:42.145 --> 00:17:43.435 that we get the AAA part.
00:17:47.370 --> 00:17:52.020 Yep, and then from there do you get?
00:17:52.020 --> 00:17:55.644 Just, uh, it might just be current username.
00:17:55.650 --> 00:17:59.142 Current, current user ID or is that the one?
00:17:59.150 --> 00:18:00.462 Oh yeah, that's that's.
00:18:00.462 --> 00:18:02.102 And anything that's an endpoint,
00:18:02.110 --> 00:18:04.840 yeah, just do current user I.
00:18:04.840 --> 00:18:07.780 I think you can do current user
00:18:07.780 --> 00:18:10.188 or throw 401 dot name right?
00:18:10.188 --> 00:18:13.040 I need to get off the front of that yeah.
00:18:18.950 --> 00:18:19.838 You Mr you.
00:18:23.190 --> 00:18:25.029 Yeah, current user.
00:18:27.870 --> 00:18:30.044 Your current user ID or 341 current
00:18:30.044 --> 00:18:31.765 user name right there or 3041?
00:18:31.765 --> 00:18:34.445 Yeah perfect. How to know that was there?
00:18:34.450 --> 00:18:35.815 I didn't know you could get the
00:18:35.815 --> 00:18:37.520 name directly. Convenient colon.
00:18:40.840 --> 00:18:42.960 Quest dot filename inside braces.
00:18:49.330 --> 00:18:51.330 Hey go alright so that will be our
00:18:51.330 --> 00:18:53.675 key that we will look up in reference
00:18:53.675 --> 00:18:55.264 to information for and everything
00:18:55.264 --> 00:18:57.658 is released or we inside this block.
00:18:57.660 --> 00:18:59.988 So that right now you're passing a null.
00:18:59.990 --> 00:19:02.546 The null there is what we would we would
00:19:02.546 --> 00:19:05.236 pass as the object that we're going to do.
00:19:05.240 --> 00:19:07.733 Do a value to pull to keep it simple,
00:19:07.740 --> 00:19:11.230 we could create an object.
00:19:11.230 --> 00:19:12.364 We're going to need to read
00:19:12.364 --> 00:19:13.120 this from another direction,
00:19:13.120 --> 00:19:16.136 so I suggest we use like an actual
00:19:16.140 --> 00:19:18.810 class or or valuable or something
00:19:18.810 --> 00:19:21.290 that that structured and easily
00:19:21.290 --> 00:19:23.750 serializable at the serializable.
00:19:23.750 --> 00:19:25.448 We have to define it outside
00:19:25.448 --> 00:19:27.618 of the scope of this UM method,
00:19:27.620 --> 00:19:28.910 because it needs to be accessed
00:19:28.910 --> 00:19:29.555 from multiple places.
00:19:29.560 --> 00:19:31.729 So do we need to go make a model
00:19:31.729 --> 00:19:33.750 somewhere like up in those three models?
00:19:33.750 --> 00:19:35.493 I wouldn't go that far up because
00:19:35.493 --> 00:19:37.164 it's just gonna be getting bread
00:19:37.164 --> 00:19:38.324 from right here anyway,
00:19:38.330 --> 00:19:40.234 but the other endpoints gonna be right here,
00:19:40.240 --> 00:19:41.980 well, isn't it gonna need to
00:19:41.980 --> 00:19:43.650 be updated in the import?
00:19:43.650 --> 00:19:44.518 The provider as well?
00:19:49.370 --> 00:19:54.840 Good point. Uhm, it's kind of weird.
00:19:54.840 --> 00:19:56.490 Like like if we wanted to be cheap about it.
00:19:56.490 --> 00:19:58.032 I value people would be really
00:19:58.032 --> 00:19:59.641 simple because we could just say
00:19:59.641 --> 00:20:00.966 the same number of parameters.
00:20:00.970 --> 00:20:02.290 They don't have to actually create
00:20:02.290 --> 00:20:04.258 a class or a structure or anything.
00:20:04.260 --> 00:20:05.276 Yeah, let's do that.
00:20:05.276 --> 00:20:07.210 Let's just do the double that sounds.
00:20:07.210 --> 00:20:07.920 Sounds easy.
00:20:07.920 --> 00:20:10.405 It's not like this needs to be.
00:20:10.410 --> 00:20:13.175 A crazy you know heavily structured thing.
00:20:17.810 --> 00:20:20.927 It's a new tuple you just
00:20:20.927 --> 00:20:21.878 said open parentheses.
00:20:25.210 --> 00:20:26.220 Parentheses. Yeah, there you go.
00:20:28.260 --> 00:20:31.675 And then, uh, put in, UM,
00:20:31.675 --> 00:20:33.550 so let's think about this.
00:20:33.550 --> 00:20:35.132 So for now, I think the first
00:20:35.132 --> 00:20:36.319 thing will need in there.
00:20:36.320 --> 00:20:38.576 We want to put in the time that
00:20:38.576 --> 00:20:40.480 the that the event started.
00:20:40.480 --> 00:20:42.195 So you might do like date extensions,
00:20:42.200 --> 00:20:43.648 Gen, Date, time first.
00:20:50.430 --> 00:20:55.500 OK, and then we're gonna need, UM, the.
00:20:55.500 --> 00:20:57.648 Uhm, the name of the file
00:20:57.648 --> 00:20:59.490 so you can do a. Actually.
00:20:59.490 --> 00:21:00.660 No, we don't need the name of the file.
00:21:00.660 --> 00:21:01.320 We don't care about that.
00:21:01.320 --> 00:21:03.434 We already identifying that in the key.
00:21:03.440 --> 00:21:08.580 Uhm? So then I guess we would do 04
00:21:08.580 --> 00:21:12.930 total products, 04 products imported.
00:21:12.930 --> 00:21:17.800 And then a string for status, right so?
00:21:17.800 --> 00:21:20.110 Yes, so I think that's insane,
00:21:20.110 --> 00:21:21.340 but like string dot empty.
00:21:21.340 --> 00:21:22.188 Yeah, yeah.
00:21:22.188 --> 00:21:24.308 In a list of strings.
00:21:26.330 --> 00:21:27.779 That we can do like messages and
00:21:27.779 --> 00:21:28.660 feedback that whatever feedback
00:21:28.660 --> 00:21:29.730 we're going to give back.
00:21:32.330 --> 00:21:32.860 Perfect.
00:21:35.040 --> 00:21:36.622 And then that import product table is
00:21:36.622 --> 00:21:38.386 what you would put into this event now.
00:21:43.200 --> 00:21:45.256 I wonder how that gets serialized into Jason.
00:21:45.260 --> 00:21:47.018 I wonder how that's gonna it
00:21:47.018 --> 00:21:49.138 actually looks at technical it.
00:21:49.138 --> 00:21:51.346 It doesn't parentheses and then a
00:21:51.346 --> 00:21:53.580 comma delimited thing of each variable.
00:21:53.580 --> 00:21:58.340 Oh cool, nice in Jason. Yes.
00:22:00.450 --> 00:22:02.952 Like in a string or 'cause
00:22:02.952 --> 00:22:05.170 parentheses aren't valid in Jason.
00:22:05.170 --> 00:22:05.923 Well, it's it's.
00:22:05.923 --> 00:22:08.064 It's a like if it was at Jason
00:22:08.064 --> 00:22:09.545 property of a thing, yes,
00:22:09.545 --> 00:22:10.775 but we're just doing it straight,
00:22:10.780 --> 00:22:12.580 so it's just a directly
00:22:12.580 --> 00:22:13.660 serialized value table.
00:22:24.510 --> 00:22:28.450 OK, and we look at.
00:22:28.450 --> 00:22:31.590 So that creates our initial.
00:22:31.590 --> 00:22:34.188 Entry into the.
00:22:34.190 --> 00:22:36.385 Into the cache and then
00:22:36.385 --> 00:22:39.690 what we need to do is uhm.
00:22:42.380 --> 00:22:45.600 Yeah, a we need a way to identify the file.
00:22:45.600 --> 00:22:48.522 UM, down the line so spreadsheet
00:22:48.522 --> 00:22:51.469 model so we open a stream.
00:22:51.470 --> 00:22:53.750 Here with the file path
00:22:53.750 --> 00:22:55.346 already and we passed that in.
00:22:55.350 --> 00:22:57.366 So that means I don't think
00:22:57.366 --> 00:22:59.208 we have unless we can read
00:22:59.208 --> 00:23:00.960 the file name off the stream.
00:23:03.210 --> 00:23:04.386 We have the file name here,
00:23:04.390 --> 00:23:07.134 but we we passed the spreadsheet model
00:23:07.134 --> 00:23:09.304 into integrate async and we don't
00:23:09.304 --> 00:23:11.968 pass the model the file path into the
00:23:11.968 --> 00:23:15.810 spreadsheet model that's being added.
00:23:15.810 --> 00:23:17.790 You can just add request filename
00:23:17.790 --> 00:23:19.510 to the spreadsheet import model.
00:23:19.510 --> 00:23:24.460 Impact on. Yep, or we could have the key.
00:23:24.460 --> 00:23:27.240 But yeah, that works too.
00:23:27.240 --> 00:23:27.842 Actually, yeah,
00:23:27.842 --> 00:23:29.648 adding the whole key would be
00:23:29.648 --> 00:23:31.739 better 'cause it 'cause we at once
00:23:31.739 --> 00:23:32.883 we're inside integrated products
00:23:32.883 --> 00:23:34.806 we no longer know who the user is.
00:23:34.810 --> 00:23:38.990 Miller we don't need to pass the whole tuple,
00:23:38.990 --> 00:23:41.195 we just need to pass the the the key
00:23:41.195 --> 00:23:43.375 itself because we can read the rest of
00:23:43.375 --> 00:23:45.320 the contents of the tuple back out.
00:23:50.360 --> 00:23:51.730 Games called like cash key.
00:23:55.030 --> 00:23:57.340 And then we'll also need to go and fix the
00:23:57.403 --> 00:23:59.608 the interface that this is pulling from.
00:24:35.310 --> 00:24:35.710 Sweet.
00:25:08.870 --> 00:25:10.040 This mentations
00:25:12.080 --> 00:25:14.530 it's just Visual Studio being Visual Studio.
00:25:22.860 --> 00:25:25.918 Oh you. Go back to that.
00:25:25.918 --> 00:25:27.370 I don't think you updated the
00:25:27.429 --> 00:25:28.799 yeah you didn't update the
00:25:28.800 --> 00:25:30.408 implementation with the updated,
00:25:30.408 --> 00:25:31.718 uh, like you didn't add
00:25:31.718 --> 00:25:33.080 the string key thing to it.
00:25:38.940 --> 00:25:41.886 You gotta go back to work providerbase.
00:25:41.886 --> 00:25:44.950 Yes, go back down to yeah to the
00:25:45.033 --> 00:25:47.199 method and then just add the
00:25:47.199 --> 00:25:49.849 string cache key to it right there.
00:25:49.850 --> 00:25:50.720 That's all we were forgetting.
00:25:54.880 --> 00:25:55.650 Sweeeet
00:26:43.760 --> 00:26:46.410 where is get headers called.
00:26:49.930 --> 00:26:50.380 North
00:27:02.510 --> 00:27:05.870 OK, so that just means it.
00:27:05.870 --> 00:27:07.544 Alright, so yeah, so load async
00:27:07.544 --> 00:27:09.050 loads the spreadsheet into memory,
00:27:09.050 --> 00:27:11.444 so I think what we want to do is
00:27:11.444 --> 00:27:13.374 parse parses where we actually
00:27:13.374 --> 00:27:15.954 go through the data from the
00:27:15.954 --> 00:27:18.758 spreadsheet and convert it into.
00:27:21.820 --> 00:27:22.910 Useful information.
00:27:32.720 --> 00:27:34.190 Oh nice, it does nothing.
00:27:43.970 --> 00:27:47.190 So hold on, wait. What?
00:27:52.730 --> 00:27:55.080 Yeah, I don't know why
00:27:55.080 --> 00:27:56.960 that's like that either.
00:27:56.960 --> 00:27:57.755 'cause this work?
00:27:57.755 --> 00:27:58.815 I mean this works.
00:27:58.820 --> 00:28:00.410 I've used this on recent projects,
00:28:00.410 --> 00:28:01.988 so how does that is that?
00:28:04.520 --> 00:28:07.076 What in the hell? I mean,
00:28:07.080 --> 00:28:08.676 obviously there's a few different imports.
00:28:08.680 --> 00:28:11.038 Oh, it's because I think it uses the Excel.
00:28:11.040 --> 00:28:13.637 Yeah, this is where it overrides it.
00:28:13.640 --> 00:28:15.642 Yeah yeah, yeah, right you went to
00:28:15.642 --> 00:28:18.171 the you into the base class that has
00:28:18.171 --> 00:28:20.480 the that should probably just be an
00:28:20.480 --> 00:28:22.678 abstract class then. But anyway, I,
00:28:22.678 --> 00:28:25.960 I think because it has to like it.
00:28:25.960 --> 00:28:28.660 Have a Google Sheets I think.
00:28:28.660 --> 00:28:30.172 Uh, is that it was trying to provide
00:28:30.172 --> 00:28:31.351 a Google people application that
00:28:31.351 --> 00:28:33.115 Google Sheets you have to deal with?
00:28:33.120 --> 00:28:36.248 Maybe, but that's not even a thing anymore.
00:28:38.560 --> 00:28:39.976 Yeah, that's basically just become a.
00:28:43.480 --> 00:28:45.400 Abstract implementation rather than.
00:29:19.520 --> 00:29:20.100 Second
00:29:53.000 --> 00:29:53.340 sweet.
00:29:55.660 --> 00:29:58.845 Alright, so Next up we want to
00:29:58.845 --> 00:30:02.130 go to the, uh, Excel provider.
00:30:05.880 --> 00:30:06.765 Which is it's giving you
00:30:06.765 --> 00:30:07.650 an error on the right.
00:30:07.650 --> 00:30:09.800 So yeah, there it is.
00:30:09.800 --> 00:30:12.368 Yeah, kaschke in there.
00:30:12.370 --> 00:30:17.212 And then so now what we want to do?
00:30:17.220 --> 00:30:20.666 Is UM? I wonder if there's a way.
00:30:20.670 --> 00:30:23.540 There's probably a way that you can.
00:30:23.540 --> 00:30:28.200 Uhm? Get the number of rows.
00:30:28.200 --> 00:30:30.990 In this spreadsheet.
00:30:30.990 --> 00:30:32.820 It's doing a an excel like
00:30:32.820 --> 00:30:34.735 awhile read so like it's an
00:30:34.735 --> 00:30:36.607 unknown number and it just give
00:30:36.607 --> 00:30:38.663 you the account up every time
00:30:38.663 --> 00:30:40.440 a bicycle road Portsmouth.
00:30:43.500 --> 00:30:46.396 Yeah, I was just thinking if we could.
00:30:46.400 --> 00:30:48.980 We can't really provide progress then
00:30:48.980 --> 00:30:51.156 it's basically just like it's done.
00:30:51.156 --> 00:30:53.344 When it's done, we don't have a.
00:30:53.344 --> 00:30:55.600 We don't have an end number.
00:30:55.600 --> 00:30:58.348 This one. Go up to wherever
00:30:58.348 --> 00:31:00.630 it read the spreadsheet and.
00:31:00.630 --> 00:31:02.527 Yeah, just passed on the number from
00:31:02.527 --> 00:31:04.589 there all the way through the chain.
00:31:04.590 --> 00:31:06.578 It doesn't know it up there either.
00:31:09.990 --> 00:31:12.578 I mean if it's a data set, we have
00:31:12.578 --> 00:31:15.858 exact cell file, we have field count.
00:31:18.700 --> 00:31:20.035 I mean, obviously something has
00:31:20.035 --> 00:31:21.889 to be able to figure out how
00:31:21.889 --> 00:31:23.275 many rows of data there are.
00:31:23.280 --> 00:31:24.624 Gotta be a way to do that.
00:31:24.630 --> 00:31:26.338 Yeah, that's why it's doing a while
00:31:26.338 --> 00:31:28.082 loop is it's having to read each
00:31:28.082 --> 00:31:30.090 line over and over again as it moves
00:31:30.090 --> 00:31:31.903 through until we can discover how many
00:31:31.903 --> 00:31:33.340 are actually going to get pulled up.
00:31:35.820 --> 00:31:37.014 Part of that is because people
00:31:37.014 --> 00:31:38.742 have had in the past, like uplink
00:31:38.742 --> 00:31:40.728 first column and stuff like that,
00:31:40.730 --> 00:31:42.508 and we have to like iterate through
00:31:42.508 --> 00:31:44.395 multiple layers in order to figure out
00:31:44.395 --> 00:31:46.003 where data starting where data stops.
00:31:56.150 --> 00:31:57.734 Still be passing the
00:31:57.734 --> 00:31:59.318 kaschke through that stuff.
00:31:59.320 --> 00:32:01.705 Why would it go to the parse async if
00:32:01.705 --> 00:32:03.735 there's nothing I can report in here?
00:32:03.740 --> 00:32:05.639 There is data that you can report in there.
00:32:05.640 --> 00:32:07.496 We can report how many we've gone through
00:32:07.496 --> 00:32:09.329 to figure out we won't have a progress,
00:32:09.330 --> 00:32:11.810 but we could say how many rows we've
00:32:11.810 --> 00:32:13.429 iterated through the spreadsheet.
00:32:13.430 --> 00:32:14.138 Oh, that's true.
00:32:30.190 --> 00:32:33.090 Smart. Yes.
00:32:35.170 --> 00:32:38.026 Visual Studio. OK so then yeah,
00:32:38.030 --> 00:32:41.036 so I guess after each row yeah so current
00:32:41.036 --> 00:32:45.408 row gets gets incremented. Uhm and then.
00:33:06.390 --> 00:33:10.610 Forgot the Oh yeah, you got it. OK, uhm.
00:33:12.760 --> 00:33:19.150 So then I guess at the end of of each uh.
00:33:19.150 --> 00:33:22.006 Well, I guess you could do Excel data
00:33:22.006 --> 00:33:25.244 at the start current row at the start
00:33:25.244 --> 00:33:27.930 of while Excel data reader read.
00:33:27.930 --> 00:33:30.266 Because there's some early outs and we want
00:33:30.266 --> 00:33:32.855 to make sure that we actually report this.
00:33:32.860 --> 00:33:35.245 In the case that it you know never makes
00:33:35.245 --> 00:33:38.149 it through, do we want to cash it every
00:33:38.149 --> 00:33:40.997 loop or do you wanna cash it every?
00:33:41.000 --> 00:33:43.776 50 loops or 100.
00:33:43.776 --> 00:33:46.470 Uhm, that is a good question.
00:33:46.470 --> 00:33:48.258 Uh, five and if that means
00:33:48.258 --> 00:33:50.120 number needs to be adjusted,
00:33:50.120 --> 00:33:51.320 we can deal with it later.
00:33:51.320 --> 00:33:53.665 Yeah, so you can do if current
00:33:53.665 --> 00:33:55.059 row percent 5 = 0.
00:34:18.520 --> 00:34:19.580 Alright, so then, well,
00:34:19.580 --> 00:34:23.740 I think we need to read it out first, UM?
00:34:23.740 --> 00:34:26.001 And you could probably read it out
00:34:26.001 --> 00:34:28.379 to start at the very beginning.
00:34:28.380 --> 00:34:31.082 Uhm, that way we don't have to
00:34:31.082 --> 00:34:33.592 read it every time because we want
00:34:33.592 --> 00:34:35.720 to make sure that the start date
00:34:35.788 --> 00:34:37.874 or the start time the first date
00:34:37.874 --> 00:34:39.989 time we passed in stays the same.
00:34:42.020 --> 00:34:45.995 And then, uh. And then you'll have to
00:34:45.995 --> 00:34:48.599 pass it and then type a type parameter,
00:34:48.600 --> 00:34:52.962 UM, on the get async to make sure
00:34:52.962 --> 00:34:55.868 it knows how to deserialize it.
00:34:55.870 --> 00:34:58.103 Which is going to be a tuple
00:34:58.103 --> 00:34:59.910 that is a datetime.
00:34:59.910 --> 00:35:01.520 You can just do parentheses.
00:35:05.260 --> 00:35:09.148 Remember, it's in the daytime comma.
00:35:09.150 --> 00:35:10.862 Uhm, what do we do? Datetime,
00:35:10.862 --> 00:35:14.586 uh, I think we did two ints,
00:35:14.590 --> 00:35:17.040 a string and a list of strings.
00:35:22.220 --> 00:35:23.456 And I think we didn't have
00:35:23.456 --> 00:35:24.600 the first string on there.
00:35:24.600 --> 00:35:25.700 I think it was datetime,
00:35:25.700 --> 00:35:30.070 int into string list in early string.
00:35:30.070 --> 00:35:31.589 We can click over our product import
00:35:31.589 --> 00:35:33.350 service at CS right next to it, and.
00:35:38.480 --> 00:35:40.280 Back up just a tiny bit.
00:35:40.280 --> 00:35:41.711 Yeah, there we go. Nope, down,
00:35:41.711 --> 00:35:44.117 uh, yeah we did date into
00:35:44.117 --> 00:35:46.539 string list of strings cool.
00:35:51.570 --> 00:35:56.828 OK, so then you can do cash to poldat.
00:35:56.830 --> 00:36:02.168 I waited. Yeah, yeah. I didn't notice that.
00:36:04.940 --> 00:36:06.836 Do you still not awaiting it at the
00:36:06.836 --> 00:36:13.860 top up there, yeah. Maybe? I'm dumb.
00:36:13.860 --> 00:36:16.404 So item two, I think is going to
00:36:16.404 --> 00:36:18.826 be the total number read yes,
00:36:18.826 --> 00:36:21.004 then you'll just do current row
00:36:21.004 --> 00:36:23.248 and then Redis cache dot add.
00:36:23.248 --> 00:36:26.126 Or is there like an update we haven't had.
00:36:26.126 --> 00:36:27.960 Is there an update or like a
00:36:27.960 --> 00:36:30.504 set or is it just add or add?
00:36:30.510 --> 00:36:32.790 There's not an ad I guess add I'm
00:36:32.790 --> 00:36:34.370 assuming edges overwrites then.
00:36:39.230 --> 00:36:41.003 Thank you want the key first and then two
00:36:41.003 --> 00:36:42.719 people and then whatever else was in there.
00:36:47.360 --> 00:36:48.398 Yeah, OK, cool.
00:36:50.730 --> 00:36:54.690 Oh, it's cash key on the key. Yeah.
00:36:57.070 --> 00:36:59.214 I will also need to await that one.
00:37:08.810 --> 00:37:09.659 Does that update?
00:37:19.950 --> 00:37:23.076 I don't know. I mean, I would.
00:37:23.076 --> 00:37:24.640 I would be surprised if it didn't,
00:37:24.640 --> 00:37:25.688 I don't, I don't.
00:37:25.688 --> 00:37:27.190 I mean otherwise, how would you over it?
00:37:27.190 --> 00:37:29.717 You have to don't think you can.
00:37:29.720 --> 00:37:32.816 Delete so I think it it has to overwrite.
00:37:32.820 --> 00:37:33.884 It does have a delete but we
00:37:33.884 --> 00:37:34.920 don't need to worry about it.
00:37:34.920 --> 00:37:38.002 Does do over it OK? Alright, UM,
00:37:38.002 --> 00:37:40.990 so that's gonna get us the the whole thing.
00:37:40.990 --> 00:37:42.253 And then, UM,
00:37:42.253 --> 00:37:46.069 we can at the end of this we can.
00:37:46.070 --> 00:37:52.410 Add a UM. Uhm?
00:37:52.410 --> 00:37:54.560 Like after the whole UM
00:37:54.560 --> 00:37:56.710 parse async method is done,
00:37:56.710 --> 00:37:59.284 we can do one more update of the cash
00:37:59.284 --> 00:38:01.927 to reflect the actual total number.
00:38:01.930 --> 00:38:05.588 'cause if it's like if we have 357 products,
00:38:05.588 --> 00:38:06.744 but we're only updating
00:38:06.744 --> 00:38:08.210 the cache key every five,
00:38:08.210 --> 00:38:10.098 that number will incorrectly
00:38:10.098 --> 00:38:12.626 be 355 when it should be 357.
00:38:12.626 --> 00:38:16.798 So at the end of parce sink.
00:38:16.800 --> 00:38:18.141 After the loop.
00:38:18.141 --> 00:38:22.870 Will go in and do one last update to the.
00:38:22.870 --> 00:38:24.610 Do that inside face it,
00:38:24.610 --> 00:38:24.940 yeah?
00:38:27.570 --> 00:38:30.880 I agree. Hey Brendan,
00:38:30.880 --> 00:38:32.647 I have a question, yeah?
00:38:32.647 --> 00:38:35.950 Is there a way to deduct the entire file
00:38:36.035 --> 00:38:39.147 size before you loop through all of it?
00:38:39.150 --> 00:38:40.522 Finally, we're kind of
00:38:40.522 --> 00:38:42.237 talking really like we are.
00:38:42.240 --> 00:38:43.977 Yeah, the file size is not part of the,
00:38:43.980 --> 00:38:47.249 uh, how Excel physically stores the data?
00:38:47.250 --> 00:38:50.220 Yeah, so at least with what we're given now,
00:38:50.220 --> 00:38:52.380 it doesn't look like we have a way to
00:38:52.380 --> 00:38:54.318 deduce the number of rows in advance,
00:38:54.320 --> 00:38:54.615 unfortunately.
00:38:54.615 --> 00:38:56.975 Yeah, 'cause I was thinking if you knew
00:38:56.975 --> 00:38:59.260 the file size and there was a way to like,
00:38:59.260 --> 00:39:01.852 say, like how big a row is on average,
00:39:01.860 --> 00:39:03.978 which you could update every iteration,
00:39:03.980 --> 00:39:07.012 you could maybe guess how long the whole
00:39:07.012 --> 00:39:09.999 thing will take that with an Excel file.
00:39:10.000 --> 00:39:12.938 If it was CSC that would be fine. Yeah,
00:39:12.938 --> 00:39:15.530 Excel is kind of goofy and you can also,
00:39:15.530 --> 00:39:17.210 uh, I always thought it was interesting.
00:39:17.210 --> 00:39:18.645 I don't know if this is the
00:39:18.645 --> 00:39:20.089 same for Excel files like asks,
00:39:20.090 --> 00:39:22.090 but if you open a docx file with
00:39:22.090 --> 00:39:23.907 seven zip or like a ZIP viewer,
00:39:23.910 --> 00:39:26.754 or like I think you've changed
00:39:26.754 --> 00:39:28.650 the extension to zip,
00:39:28.650 --> 00:39:30.282 it will open and you'll actually
00:39:30.282 --> 00:39:32.030 able to see files in it like.
00:39:32.030 --> 00:39:33.906 Then they it's literally just a zip
00:39:33.906 --> 00:39:35.909 file with a different extension.
00:39:35.910 --> 00:39:37.062 That's how they're structured,
00:39:37.062 --> 00:39:38.790 and inside that there were all
00:39:38.844 --> 00:39:40.119 the different XML files that
00:39:40.119 --> 00:39:41.394 store all the data about,
00:39:41.400 --> 00:39:43.269 like what the formatting of each cell
00:39:43.269 --> 00:39:45.440 is that the final value of the cell,
00:39:45.440 --> 00:39:46.236 any formulas,
00:39:46.236 --> 00:39:48.226 all that stuff gets separated
00:39:48.226 --> 00:39:50.155 into separate files inside that
00:39:50.155 --> 00:39:53.008 that main exe file painful then.
00:39:58.320 --> 00:40:01.272 Uhm, so we need to pass the cache
00:40:01.272 --> 00:40:04.350 key and to resolve async I think.
00:40:04.350 --> 00:40:06.202 Yes, I like you.
00:40:06.202 --> 00:40:10.440 Sorry that you are you at first. Uh, no.
00:40:10.440 --> 00:40:13.160 I think that I I was just mumbling
00:40:13.248 --> 00:40:15.112 you're good just like you're asking
00:40:15.112 --> 00:40:16.900 what library are we using for Excel?
00:40:16.900 --> 00:40:18.766 Because I just opened up Argus
00:40:18.766 --> 00:40:20.819 which is a somewhat old project.
00:40:20.820 --> 00:40:23.086 At least it's old enough to be.net
00:40:23.086 --> 00:40:26.014 core 2.1 and like I'm able to get
00:40:26.014 --> 00:40:29.130 the number of rows in the worksheet.
00:40:29.130 --> 00:40:31.803 You can get the number of rows if you
00:40:31.803 --> 00:40:34.156 load the entire document at once.
00:40:34.160 --> 00:40:37.610 It's called Microsoft interacting with.
00:40:42.340 --> 00:40:43.915 So we're just doing something
00:40:43.915 --> 00:40:45.570 sort of special there, I guess.
00:40:52.400 --> 00:40:55.024 We are just just having a thing that
00:40:55.024 --> 00:40:57.679 says that like this many rows have
00:40:57.679 --> 00:41:00.056 been edited is not indicative of
00:41:00.056 --> 00:41:02.318 how many rows they're actually on.
00:41:02.320 --> 00:41:04.322 No, I mean inside the file like
00:41:04.322 --> 00:41:06.192 beyond the last record and type
00:41:06.192 --> 00:41:07.772 something it saved the file
00:41:07.772 --> 00:41:09.690 and then deleted that record.
00:41:09.690 --> 00:41:11.022 Our orderly did that role with
00:41:11.022 --> 00:41:12.756 the file and it thinks there are
00:41:12.756 --> 00:41:14.334 more rows in there actually are.
00:41:49.950 --> 00:41:54.390 Should I pass in the cash or just the key?
00:41:54.390 --> 00:41:59.370 The cat the key. OK.
00:41:59.370 --> 00:42:00.618 I don't know if we actually
00:42:00.618 --> 00:42:01.690 need this here or not.
00:42:01.690 --> 00:42:02.398 Just leave it there.
00:42:23.080 --> 00:42:25.270 That's for the reply, not the.
00:42:27.340 --> 00:42:28.280 Alexa off.
00:42:33.210 --> 00:42:35.038 Sounds like my 93.
00:42:41.270 --> 00:42:44.960 Oh oh, you're right, I got it.
00:43:27.060 --> 00:43:27.530 Fire.
00:43:47.050 --> 00:43:48.890 Alright. And it looks good.
00:44:00.370 --> 00:44:00.880 What?
00:44:20.460 --> 00:44:22.056 But that's that can't change there.
00:44:22.060 --> 00:44:24.566 That's a that's a request on Thursday.
00:44:46.550 --> 00:44:48.554 Yeah, anybody else who who wants
00:44:48.554 --> 00:44:50.988 to drop or you know is ready
00:44:50.988 --> 00:44:53.028 to drop have a great weekend.
00:44:53.030 --> 00:44:57.294 Yep, happy Friday we will be held hostage.
00:44:57.300 --> 00:44:59.622 Yeah, I think we're almost to a point where,
00:44:59.630 --> 00:45:02.880 UM, maybe, if we can get.
00:45:02.880 --> 00:45:06.976 Uh, is this side of it close here?
00:45:06.980 --> 00:45:08.644 Uh, no, that's not.
00:45:08.644 --> 00:45:12.001 Under I mean I'm sorry I meant on
00:45:12.001 --> 00:45:14.935 the just like reporting the reporting
00:45:14.935 --> 00:45:18.420 to the cash for about 1/3 done.
00:45:18.420 --> 00:45:19.620 We're getting fairly close.
00:45:19.620 --> 00:45:21.120 We're passing the kashkin to
00:45:21.120 --> 00:45:22.506 resolve and then and this one.
00:45:22.510 --> 00:45:23.926 It's basically just.
00:45:23.926 --> 00:45:26.758 Items items dot length is going
00:45:26.758 --> 00:45:28.700 to be the first uh.
00:45:28.700 --> 00:45:30.065 Part of it,
00:45:30.065 --> 00:45:32.795 and then we just increment a
00:45:32.800 --> 00:45:35.089 counter in that for each loop and
00:45:35.089 --> 00:45:37.509 store that to the cache and then
00:45:37.509 --> 00:45:39.555 the reporting is done I think.
00:45:39.560 --> 00:45:40.493 You think so?
00:45:40.493 --> 00:45:41.426 I think so.
00:45:41.430 --> 00:45:42.040 I mean,
00:45:42.040 --> 00:45:44.810 that's I mean we're not gonna write the end.
00:45:44.810 --> 00:45:46.336 I think it sounds like we're think
00:45:46.336 --> 00:45:47.869 we're probably not going to write the
00:45:47.869 --> 00:45:49.420 endpoint to actually read it out today.
00:45:49.420 --> 00:45:50.698 Will probably do that next week.
00:45:50.700 --> 00:45:52.278 And, uh, yeah, that sounds good.
00:45:52.280 --> 00:45:54.410 Net is that if we can get to a point
00:45:54.472 --> 00:45:56.250 where we think that the code is
00:45:56.250 --> 00:45:58.232 done from a reporting standpoint,
00:45:58.232 --> 00:46:00.656 then maybe next Friday.
00:46:00.660 --> 00:46:00.958 Brandon,
00:46:00.958 --> 00:46:03.044 if you can just have your local
00:46:03.044 --> 00:46:04.836 ready so that we can import something
00:46:04.836 --> 00:46:06.234 and just look at the cache,
00:46:06.240 --> 00:46:07.758 see if the key is there,
00:46:07.760 --> 00:46:10.028 then we can build the the endpoint.
00:46:10.030 --> 00:46:11.798 Next week to actually read it out and
00:46:11.798 --> 00:46:13.375 then look at the front end on it.
00:46:20.130 --> 00:46:24.783 And then from a this is going into core
00:46:24.783 --> 00:46:27.046 perspective on the front end side, we'll
00:46:27.046 --> 00:46:29.390 have we'll do like a nice mock up for it.
00:46:31.540 --> 00:46:33.675 Do just kind of base to get
00:46:33.675 --> 00:46:35.040 to get functionality there,
00:46:35.040 --> 00:46:36.918 but then we'll just have somebody
00:46:36.918 --> 00:46:40.679 style it, they stuff mockups.
00:46:40.680 --> 00:46:42.311 What's wrong just so ready is aware
00:46:42.311 --> 00:46:43.849 of the process there looks like.
00:46:46.210 --> 00:46:48.586 Cool sounds good. Say we'll get this to a
00:46:48.586 --> 00:46:50.530 stopping point here and then we'll, uh.
00:46:52.930 --> 00:46:53.950 Hold the rest for next week.
00:46:56.000 --> 00:46:57.185 Awesome, thanks guys.
00:46:57.185 --> 00:46:59.160 I'm gonna drop as well.
00:46:59.160 --> 00:47:01.068 Have a good weekend. Thanks bye.
00:47:32.590 --> 00:47:33.862 Item three, I think, is the
00:47:33.862 --> 00:47:35.320 one we're going to set on this.
00:47:43.480 --> 00:47:45.010 Item two is longer updating
00:47:45.010 --> 00:47:46.234 with the total amount,
00:47:46.240 --> 00:47:49.070 so I think item 3 is going to be the
00:47:49.153 --> 00:47:52.698 in progress amount we can get there.
00:47:52.700 --> 00:47:54.725 We have to rely on working.
00:47:54.725 --> 00:47:56.450 Yeah, we could do that.
00:47:58.850 --> 00:48:02.280 On the cash on the line 87.
00:48:02.280 --> 00:48:04.271 Like you can do datetime, start
00:48:04.271 --> 00:48:09.810 comma in total comma int a. Yeah.
00:48:12.250 --> 00:48:14.122 And completed or for the next
00:48:14.122 --> 00:48:16.419 one up and then string status.
00:48:22.080 --> 00:48:22.600 Messages.
00:48:28.070 --> 00:48:30.912 Is that is that how you would
00:48:30.912 --> 00:48:32.898 break that? Uh, yeah, that's fine.
00:48:38.480 --> 00:48:41.441 And then you can rename item three
00:48:41.441 --> 00:48:44.386 to be completed. Cash tupled
00:48:44.386 --> 00:48:47.870 completed equals count. On 1/14
00:48:50.600 --> 00:48:55.688 and then, uh. Redis cache dot.
00:48:55.690 --> 00:48:58.518 Add async await Redis cache I guess.
00:49:06.480 --> 00:49:07.705 You need the key first
00:49:07.705 --> 00:49:08.930 and then the the value.
00:49:14.510 --> 00:49:17.625 And then configure, wait and then that
00:49:17.625 --> 00:49:20.979 should be just about it for reporting.
00:49:20.980 --> 00:49:22.054 That's this function.
00:49:22.054 --> 00:49:24.202 The result function builds the models.
00:49:24.210 --> 00:49:26.578 It is not actually pushing the database yet.
00:49:26.580 --> 00:49:28.890 Leading another section that does that OK.
00:49:31.540 --> 00:49:34.048 I guess we should add another
00:49:34.048 --> 00:49:36.830 a catch 2 pole value then.
00:49:36.830 --> 00:49:42.158 Yeah, so on the beginning here.
00:49:42.160 --> 00:49:44.365 What we can do is before the
00:49:44.365 --> 00:49:47.090 for each loop do cast tubal dot
00:49:47.090 --> 00:49:49.215 status equal to resolving models.
00:49:58.540 --> 00:50:00.094 One thing to keep in mind is
00:50:00.094 --> 00:50:01.449 that that's a value tuple.
00:50:03.580 --> 00:50:06.603 Yeah, but. I'm just looking.
00:50:06.603 --> 00:50:08.774 Oh, never mind, I was.
00:50:08.774 --> 00:50:10.946 I was outside during that permit.
00:50:10.950 --> 00:50:12.246 I was thinking that that was
00:50:12.246 --> 00:50:13.430 something we were passing across,
00:50:13.430 --> 00:50:16.006 helping us read this is it lets you
00:50:16.006 --> 00:50:17.659 retrieve things from elsewhere.
00:50:20.900 --> 00:50:22.328 Yeah, we're it's. Yeah it's they
00:50:22.328 --> 00:50:24.044 are value but we're always at the
00:50:24.044 --> 00:50:25.478 start of every place we're using.
00:50:25.480 --> 00:50:26.584 It were reading it out of
00:50:26.584 --> 00:50:27.605 Rita's were not passing it
00:50:27.605 --> 00:50:28.569 around between anything else,
00:50:28.570 --> 00:50:29.430 so that should be fine.
00:50:32.420 --> 00:50:34.598 Yeah, so we're currently in the
00:50:34.598 --> 00:50:36.740 resolve which goes and builds the
00:50:36.740 --> 00:50:39.212 models to be read and then the next
00:50:39.286 --> 00:50:41.438 step that it does is it goes in.
00:50:41.440 --> 00:50:43.204 Actually push the malls in the database
00:50:43.204 --> 00:50:45.260 as it can do the workflows so.
00:50:45.260 --> 00:50:47.972 Using this one as an example where we
00:50:47.972 --> 00:50:50.394 just had the reading at the beginning,
00:50:50.400 --> 00:50:52.122 giving it a status of saying like
00:50:52.122 --> 00:50:53.379 what's what section are we in?
00:50:53.380 --> 00:50:54.966 And then in the loop, you know,
00:50:54.966 --> 00:50:56.331 updating the agreed count and
00:50:56.331 --> 00:50:57.510 pushing it in there.
00:50:57.510 --> 00:50:59.430 We need to do the same thing in the for
00:50:59.479 --> 00:51:01.367 each loop that was in the thing that
00:51:01.367 --> 00:51:03.268 just called this react resolve function.
00:51:08.530 --> 00:51:10.078 Now we go to the reference
00:51:10.078 --> 00:51:11.110 for this resolve async.
00:51:16.320 --> 00:51:19.866 Let's see one that says 65.
00:51:19.870 --> 00:51:22.860 Not now, but the. The other one.
00:51:27.640 --> 00:51:29.719 65 There yeah. So now there's a.
00:51:29.720 --> 00:51:31.920 For each loop there that starts on 75.
00:51:31.920 --> 00:51:33.459 We need to do a count in there and
00:51:33.459 --> 00:51:34.909 look at everything there as well.
00:51:37.210 --> 00:51:37.660 Cool.
00:51:42.130 --> 00:51:42.460 No.
00:51:58.100 --> 00:51:59.668 Copy the code that you had on
00:51:59.668 --> 00:52:01.180 the other one over real fast.
00:52:01.180 --> 00:52:03.160 Yeah, that's what I should do.
00:52:03.160 --> 00:52:05.728 I copied it, but then copy that part.
00:52:16.990 --> 00:52:18.886 Where? Pull it down lower you
00:52:18.886 --> 00:52:21.566 got an error on, it's just a red
00:52:21.566 --> 00:52:23.530 line on your right side. Yep.
00:52:26.840 --> 00:52:31.280 It's a. That time of the day.
00:52:31.280 --> 00:52:33.629 I feel that it's that time of the week.
00:52:33.630 --> 00:52:36.375 Uh, and then you can copy the the receipt
00:52:36.375 --> 00:52:39.080 cash part from the uh from there as well.
00:52:42.330 --> 00:52:43.975 Yep, I can copy. Yep that too.
00:52:46.540 --> 00:52:48.412 We're all in there. You should
00:52:48.412 --> 00:52:51.788 put it, uh? Right there, yeah.
00:52:56.770 --> 00:52:58.930 You might indent the next line to to show
00:52:58.930 --> 00:53:01.100 that it's part of the previous statement.
00:53:01.100 --> 00:53:03.858 Yeah, and then you could say right
00:53:03.858 --> 00:53:06.304 after that line you could do
00:53:06.304 --> 00:53:08.668 cash two poldat status equal to.
00:53:08.670 --> 00:53:10.596 Saving models to database or something.
00:53:16.600 --> 00:53:20.036 Cool. That should get that and
00:53:20.036 --> 00:53:22.528 for all of the reporting I think,
00:53:22.530 --> 00:53:24.240 right, uh, I wanted to.
00:53:24.240 --> 00:53:25.760 We want to make sure we get a
00:53:25.760 --> 00:53:27.098 status message for the parsing part.
00:53:27.100 --> 00:53:28.930 I think that initially I
00:53:28.930 --> 00:53:30.690 agree with those words, yes.
00:53:37.830 --> 00:53:40.750 We're at the end there. He did.
00:53:40.750 --> 00:53:43.130 You could also set the status to
00:53:43.130 --> 00:53:45.682 just done on that because I think
00:53:45.682 --> 00:53:49.450 at this stage like we're finished.
00:53:49.450 --> 00:53:53.356 Things like import complete or something.
00:53:53.360 --> 00:53:55.478 That works too.
00:53:55.480 --> 00:53:56.626 I like what you said there.
00:54:00.470 --> 00:54:02.129 Sweet, UM, so.
00:54:02.129 --> 00:54:05.870 Another thing we can do is, uh.
00:54:05.870 --> 00:54:08.390 See how it's adding a message
00:54:08.390 --> 00:54:11.418 on 224 to this errors list.
00:54:11.420 --> 00:54:13.436 Let's make it add to the cash to pull
00:54:13.436 --> 00:54:15.404 as well so that when it saves it,
00:54:15.410 --> 00:54:17.154 it's saving those messages in there as well.
00:54:17.160 --> 00:54:19.476 Yeah, so cashed up old messages.
00:54:19.480 --> 00:54:22.368 You may have to do cash people that
00:54:22.368 --> 00:54:23.675 messages question question equals
00:54:23.675 --> 00:54:25.880 new list just in case for whatever
00:54:25.935 --> 00:54:27.427 reason it's not initialized.
00:54:32.220 --> 00:54:34.117 Do you wanna do you wanna do?
00:54:36.830 --> 00:54:38.742 You can do it. You can shorten that
00:54:38.742 --> 00:54:40.618 and just do question Mark question
00:54:40.618 --> 00:54:42.301 mark equals that's what it's
00:54:42.301 --> 00:54:43.986 suggesting already you can remove.
00:54:43.990 --> 00:54:47.260 I know you put the new list part back on.
00:54:47.260 --> 00:54:49.240 Uhm and then remove cache.
00:54:49.240 --> 00:54:51.226 People that messages in the middle
00:54:51.226 --> 00:54:53.449 and then also the first equals.
00:54:53.450 --> 00:54:54.458 Yep, like that.
00:54:57.470 --> 00:54:59.270 Now you can open close
00:54:59.270 --> 00:55:00.350 parentheses and semicolon.
00:55:03.100 --> 00:55:05.249 New line cashable dot messages dot at.
00:55:11.490 --> 00:55:13.638 Then MSG yeah cool.
00:55:16.330 --> 00:55:20.026 Nice, that'll get those thrown in there.
00:55:20.030 --> 00:55:22.406 OK, so I think that handles the scenario
00:55:22.406 --> 00:55:24.517 there where it's having to put a
00:55:24.517 --> 00:55:26.380 message in from that exception catch.
00:55:26.380 --> 00:55:27.732 I would do a quick scroll up and
00:55:27.732 --> 00:55:28.978 just see if there's any other
00:55:28.978 --> 00:55:30.268 messages that try to get added.
00:55:33.110 --> 00:55:34.930 Yeah, it's a right there.
00:55:34.930 --> 00:55:36.316 Well then, I guess it's throwing
00:55:36.316 --> 00:55:37.392 an exception because, well,
00:55:37.392 --> 00:55:38.538 there's another Manchester.
00:55:38.538 --> 00:55:40.448 Other exception 'cause I think
00:55:40.448 --> 00:55:42.219 there's a couple of informational
00:55:42.219 --> 00:55:43.547 ones in there somewhere.
00:55:43.550 --> 00:55:44.720 I just don't know where they
00:55:44.720 --> 00:55:46.290 are without this going on isn't
00:55:46.290 --> 00:55:48.378 throwing so we need to add it here.
00:55:58.110 --> 00:55:59.280 Two question marks.
00:55:59.280 --> 00:56:02.313 One equal sign yeah and the.
00:56:02.313 --> 00:56:04.176 The target type.
00:56:04.180 --> 00:56:05.450 You should also be functional,
00:56:05.450 --> 00:56:07.214 so you could literally just type
00:56:07.214 --> 00:56:09.530 new and open and close parentheses.
00:56:09.530 --> 00:56:12.519 Yep. Well, that's free.
00:56:22.810 --> 00:56:24.959 Cool, that makes that knew that that
00:56:24.959 --> 00:56:27.029 Noel check and assign supershirt.
00:56:27.030 --> 00:56:28.200 We do all those things combined.
00:56:40.070 --> 00:56:41.930 Looks like that for the catches.
00:56:41.930 --> 00:56:44.774 Yeah, cool so that's gonna get
00:56:44.774 --> 00:56:46.670 the messages coming through.
00:56:46.670 --> 00:56:48.609 Come check over to the partial plate.
00:56:50.740 --> 00:56:53.134 Yeah, we want to get that
00:56:53.134 --> 00:56:55.540 status in for parsing. So, uh,
00:56:55.540 --> 00:56:58.884 we want to go to that call, right there?
00:56:58.884 --> 00:57:00.396 Go to the one that's override.
00:57:02.640 --> 00:57:04.000 You're in the right spot. F 12.
00:57:04.000 --> 00:57:05.325 On that got override task.
00:57:05.330 --> 00:57:06.716 Yep, and then the first thing we
00:57:06.716 --> 00:57:08.326 want to do in here is cashed up.
00:57:08.330 --> 00:57:11.115 Hold status equals parsing spreadsheet
00:57:11.115 --> 00:57:13.274 or something after after after
00:57:13.274 --> 00:57:15.710 we read the cash to pull out.
00:57:15.710 --> 00:57:17.159 So the next line after that one.
00:57:22.080 --> 00:57:24.366 And we have to add it to the message
00:57:24.366 --> 00:57:26.136 we're going to set the status.
00:57:26.140 --> 00:57:26.990 Status equals,
00:57:26.990 --> 00:57:29.540 which in this case we don't.
00:57:29.540 --> 00:57:30.458 We have to add the names
00:57:30.458 --> 00:57:31.510 like we did to the other.
00:57:34.120 --> 00:57:35.180 If we want that, yeah.
00:57:39.730 --> 00:57:42.390 Yeah, total and then and complete it.
00:57:44.490 --> 00:57:46.176 And the last one is messages.
00:57:56.750 --> 00:57:58.500 You still are parsing spreadsheet, yeah?
00:58:12.600 --> 00:58:14.336 And then it's just giving you a couple
00:58:14.336 --> 00:58:15.784 of warnings 'cause you got like item
00:58:15.784 --> 00:58:17.985 two on 82 there that could just be the
00:58:17.985 --> 00:58:22.100 actual name saying put dot total, yeah?
00:58:22.100 --> 00:58:25.220 Online at 82. Do you want total
00:58:25.220 --> 00:58:26.510 or do we want complete there?
00:58:28.810 --> 00:58:32.395 Uh, uhm. I guess that
00:58:32.395 --> 00:58:33.095 would be completely right.
00:58:36.980 --> 00:58:38.597 And then you say, going to Scroll
00:58:38.597 --> 00:58:40.128 down a little bit further too.
00:58:40.130 --> 00:58:43.574 And do the same little bit further.
00:58:43.580 --> 00:58:45.370 Right there on line 158,
00:58:45.370 --> 00:58:46.610 did the same completed.
00:58:49.670 --> 00:58:52.400 Alright, that should be good.
00:58:52.400 --> 00:58:55.550 Yeah. No errors.
00:58:58.000 --> 00:59:00.317 God Dang, right, cool so then yeah.
00:59:00.320 --> 00:59:03.978 So next Friday we can, uh, we can.
00:59:03.980 --> 00:59:05.590 Bring a nice big import sheet that
00:59:05.590 --> 00:59:07.606 will take a little bit and then
00:59:07.606 --> 00:59:09.904 make sure that we're actually seeing
00:59:09.904 --> 00:59:12.376 values update in Redis and that
00:59:12.376 --> 00:59:14.421 everything you know nothing throws
00:59:14.421 --> 00:59:16.328 exceptions or breaks or anything.
00:59:16.330 --> 00:59:17.842 If we could build our endpoint
00:59:17.842 --> 00:59:19.350 that reads that data back out,
00:59:19.350 --> 00:59:20.340 sends it to the front end,
00:59:20.340 --> 00:59:21.582 and then we'll do the front
00:59:21.582 --> 00:59:22.960 end part so it should be.
00:59:31.150 --> 00:59:34.861 So after. It won't let you do a slash
00:59:34.861 --> 00:59:36.278 with that. You have to put a dash.
00:59:38.880 --> 00:59:39.250 Yeah.
00:59:41.300 --> 00:59:44.448 Import progress or something.
00:59:44.450 --> 00:59:48.349 That would be support slash release slash
00:59:48.349 --> 00:59:53.478 feature Slash 01.1 dash import progress.
00:59:58.260 --> 00:59:59.760 Like that? Yeah.
01:00:11.950 --> 01:00:14.169 Approve of this use of PowerShell commands.
01:00:19.730 --> 01:00:20.760 With the, uh, the wizard,
01:00:20.760 --> 01:00:22.055 the branch name and everything
01:00:22.055 --> 01:00:23.769 on top of the width of the,
01:00:23.770 --> 01:00:25.720 uh, the the folder name.
01:00:25.720 --> 01:00:26.805 It kind of makes it really squished.
01:00:26.810 --> 01:00:28.266 You never know like make this stupid.
01:00:28.270 --> 01:00:32.670 Oh really, why? Yeah.
01:00:32.670 --> 01:00:36.630 Sweet alright, well that was fun.
01:00:36.630 --> 01:00:38.828 So those of you that stuck around,
01:00:38.830 --> 01:00:40.560 that's all for anyone that
01:00:40.560 --> 01:00:43.186 wants to look at it more, yeah?
01:00:43.186 --> 01:00:45.366 Cool, I'm gonna actually put
01:00:45.366 --> 01:00:47.919 that branch name in the chat.
01:00:47.920 --> 01:00:52.088 For anyone that wants.
01:00:52.090 --> 01:00:53.344 Take care closer.
01:00:53.344 --> 01:00:55.434 Look what you did today.
01:00:58.810 --> 01:01:01.660 What release?
01:01:01.660 --> 01:01:07.138 A feature 2021.1 dash import progress
01:01:07.140 --> 01:01:10.068 what's the clear command in PowerShell?
01:01:10.070 --> 01:01:13.430 A clear just clear yeah right?
01:01:13.430 --> 01:01:15.330 Uh, CMD doesn't allow that.
01:01:15.330 --> 01:01:17.610 Uhm, I'll take lower case C,
01:01:17.610 --> 01:01:19.836 But CMD doesn't take all that
01:01:19.836 --> 01:01:22.309 and back in CMD it was CLS,
01:01:22.310 --> 01:01:25.478 but PowerShell allows a lot of
01:01:25.478 --> 01:01:28.020 standard POSIX utilities now. Nice.