| Topic | Presenter | Summary | Duration | Tags | Quiz | Captions |
| --------------------------------- | ----------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------- | -------- |
| ASP.Net Core 3 and Angular 9 Book | Chris Black | This discussion finishes chapter 7 of the ASP.Net Core 3 and Angular 9 book, and begins chapter 8, which pertains to debugging. Also, this video contains the link for downloading the app which is discussed in the book and trainings. | 22:25 | #DevTrainings, #FridayTrainings, #ASP.NetCore3, #Angular9, #DevTrainingBook | ASP.Net Book CH 7/8 | |00:00:02.220 --> 00:00:05.575 - I do is have everybody download the application that we've all 00:00:05.575 --> 00:00:08.320 - been building and kind of showing throughout this training 00:00:08.320 --> 00:00:12.285 - process so far and you guys can don't have to use your own 00:00:12.285 --> 00:00:16.555 - database. You can hook up to the database on SQL be. I think it's 00:00:16.555 --> 00:00:19.910 - called World cities or something like that. So you just say 00:00:19.910 --> 00:00:23.440 - hello, hello. And. 00:00:24.010 --> 00:00:27.790 - After you get that set up, you can kind of play with it and 00:00:27.790 --> 00:00:31.030 - like you know, see how the angular is talking to itself and 00:00:31.030 --> 00:00:34.540 - then kind of see how like the back end API calls are working 00:00:34.540 --> 00:00:38.320 - as well and so you'll have like all the forms and stuff that we 00:00:38.320 --> 00:00:41.290 - kind of covered and how all that validation is working with 00:00:41.290 --> 00:00:44.260 - angular. And then how all that validation is happening on the 00:00:44.260 --> 00:00:47.770 - back end. Just basically to kind of like, you know, dig into and 00:00:47.770 --> 00:00:50.740 - really tear apart on your and will probably use that for 00:00:50.740 --> 00:00:53.980 - future trainings as well. So let me find that link really quick. 00:00:54.080 --> 00:00:58.280 - And I'll post it in the chat, and if you feel will just start 00:00:58.280 --> 00:01:00.080 - downloading that to like a local 00:01:00.080 --> 00:01:05.370 - environment. And then what will do after that is James will 00:01:05.370 --> 00:01:10.133 - start the continuation of last week's training and then for the 00:01:10.133 --> 00:01:11.432 - last little bit. 00:01:11.450 --> 00:01:15.103 - CR and I will kind of go through the chapter seven of the. 00:01:15.640 --> 00:01:17.689 - The debugging chapter. 00:01:19.040 --> 00:01:21.840 - Remind me to get my. 00:01:22.490 --> 00:01:25.319 - Solution open here. 00:01:27.450 --> 00:01:29.520 - Did everybody now should have? 00:01:30.960 --> 00:01:36.378 - See, now you know all my secrets. 00:01:38.050 --> 00:01:41.370 - Top secrets. Topsy kretts 00:01:41.370 --> 00:01:49.010 - exactly right. And I'm not suggest my screen so. 00:01:49.010 --> 00:01:53.546 - So basically what we're going to do today is back at back end and 00:01:53.546 --> 00:01:57.304 - front end debugging. And it's just pretty basic stuff. I think 00:01:57.304 --> 00:02:01.828 - most most devs on the team are pretty familiar with it. So what 00:02:01.828 --> 00:02:06.700 - we're going to do is we're going through a break point on a back 00:02:06.700 --> 00:02:11.224 - end API, and then we're going to throw a breakpoint on that front 00:02:11.224 --> 00:02:15.748 - end API as well. So I'm going to go ahead and start my 00:02:15.748 --> 00:02:19.228 - application. That should roll everything up for me and then 00:02:19.228 --> 00:02:20.968 - start a Google Chrome. Yeah, 00:02:20.968 --> 00:02:26.480 - here. Through that over here and then, while this is loading, we 00:02:26.480 --> 00:02:30.170 - can kind of just walk through that as well. 00:02:31.390 --> 00:02:32.320 - Alright. 00:02:33.950 --> 00:02:39.952 - So. What we should do and we can go ahead and pull this up. I'm 00:02:39.952 --> 00:02:44.272 - not running this in IIS, it's kind of it on its own port, so I 00:02:44.272 --> 00:02:48.304 - think we should still be able to find a W3 WP process. So what 00:02:48.304 --> 00:02:50.608 - I'm going to do is open my task 00:02:50.608 --> 00:02:54.983 - manager here. On my Windows Machine, which is where this is 00:02:54.983 --> 00:02:57.822 - running. An I'm going to try to 00:02:57.822 --> 00:03:01.250 - find. My W3 WP process. 00:03:02.160 --> 00:03:05.950 - Hopefully I bet it's this. 00:03:08.350 --> 00:03:11.049 - This looks. This looks good. 00:03:12.770 --> 00:03:13.300 - Baby. 00:03:14.500 --> 00:03:18.812 - Anybody with more back and experience so 52? I think that's 00:03:18.812 --> 00:03:23.908 - it. Let's check on that on that Port 'cause I think we hard 00:03:23.908 --> 00:03:25.868 - coded it in our application. 00:03:27.410 --> 00:03:30.190 - It's with this typically my 00:03:30.190 --> 00:03:34.477 - startups. He would know Brendan, you or Eric. 00:03:36.750 --> 00:03:39.198 - OK, I'm watching now. 00:03:39.850 --> 00:03:43.140 - What's the question for CR? 00:03:43.140 --> 00:03:46.608 - I'm thinking that this is the port that my backends running on 00:03:46.608 --> 00:03:50.654 - here is that fit 520, four, 97. Where would I find that to make 00:03:50.654 --> 00:03:54.411 - sure that that's the correct one to the center back in? I don't 00:03:54.411 --> 00:03:58.457 - think so. You can see it in the little IS there should be a 00:03:58.457 --> 00:03:59.902 - little IES when you're running 00:03:59.902 --> 00:04:03.457 - it. Um, there should. Yeah, I guess that. 00:04:04.900 --> 00:04:08.128 - Like in your task. 00:04:08.130 --> 00:04:11.923 - Check properties. Start 00:04:11.923 --> 00:04:15.450 - up project. Yeah, that's yeah 00:04:15.450 --> 00:04:22.166 - good point. OK, I'm there. Right click on 00:04:22.166 --> 00:04:24.820 - project. World cities at the top. 00:04:26.070 --> 00:04:27.660 - I'm sorry you're breaking up a 00:04:27.660 --> 00:04:30.740 - little bit. Very sad. 00:04:32.230 --> 00:04:34.766 - I'm sorry there's a lot going on, let's. 00:04:36.950 --> 00:04:38.775 - World cities at some buzzing 00:04:38.775 --> 00:04:43.322 - project. OK, Alright World cities right click and say 00:04:43.322 --> 00:04:43.726 - properties. 00:04:45.000 --> 00:04:48.140 - Properties, nice thank you. 00:04:49.210 --> 00:04:55.216 - Cool. And it's gonna be in maybe. 00:04:57.850 --> 00:05:03.000 - No debug resources debug OK. 00:05:05.120 --> 00:05:07.760 - There you go. 65112 00:05:08.990 --> 00:05:15.799 - Nice cool. So what I'm gonna do is through. 00:05:16.670 --> 00:05:19.010 - Probably have to reopen this. 00:05:20.830 --> 00:05:23.670 - What supporters were not already do. Oh no, it's already. 00:05:24.180 --> 00:05:26.754 - I think it's already deep in debug mode, so I should 00:05:26.754 --> 00:05:29.328 - be able to just throw a breakpoint on it now, huh? 00:05:31.460 --> 00:05:33.068 - Yes, or something. 00:05:33.690 --> 00:05:35.478 - Where do you work? 00:05:35.980 --> 00:05:43.770 - Alright. So let's see my throw break point on. 00:05:45.200 --> 00:05:47.636 - Oh, there we go? OK, you work. 00:05:48.850 --> 00:05:51.930 - Summer through breakpoint, an get cities and it looks like 00:05:51.930 --> 00:05:55.010 - something weird is happening here, so I'm going to just 00:05:55.010 --> 00:05:56.858 - refresh this and see if that 00:05:56.858 --> 00:06:01.320 - works. I think Heather. Did you have something similar to this? 00:06:01.320 --> 00:06:05.675 - Just a minute ago and it just went away? Yeah, it did just 00:06:05.675 --> 00:06:07.015 - refresh it timed out. 00:06:07.860 --> 00:06:09.700 - OK. 00:06:10.800 --> 00:06:17.888 - Oh it gave me 0 seconds to start 00:06:17.888 --> 00:06:21.700 - listening. So it's very impatient. 00:06:23.690 --> 00:06:29.740 - Cool. 00:06:32.320 --> 00:06:37.116 - So basically typically what you do is you could find your 00:06:37.116 --> 00:06:42.348 - process ID in your task manager, and that's where I was digging 00:06:42.348 --> 00:06:47.144 - there to try to find that process ID and then typically 00:06:47.144 --> 00:06:51.068 - you would open your Visual Studio instance as an 00:06:51.068 --> 00:06:55.428 - administrator, so you could attach to that process and then 00:06:55.428 --> 00:07:01.096 - you can go to your debug here and then basically attach to the 00:07:01.096 --> 00:07:02.840 - W 3 WP process. 00:07:02.870 --> 00:07:06.050 - And then be able to hit breakpoints and stuff. So 00:07:06.050 --> 00:07:08.912 - this is pretty similar, but since it's already running 00:07:08.912 --> 00:07:12.410 - in debug mode, I can just throw a breakpoint on the 00:07:12.410 --> 00:07:15.590 - side there. So after this loads, whenever we get our 00:07:15.590 --> 00:07:19.088 - cities by hitting the route on the front end, it should 00:07:19.088 --> 00:07:22.904 - hit this back in end point and then we can simply walk 00:07:22.904 --> 00:07:25.766 - through our back end debugger here and see if 00:07:25.766 --> 00:07:28.628 - there's some funky stuff going on with our code. 00:07:29.660 --> 00:07:35.428 - And then can Conversely, on the front end what we can do is this 00:07:35.428 --> 00:07:39.960 - is really large. We can take a look at our sources. 00:07:41.750 --> 00:07:43.605 - And then we should have our nice 00:07:43.605 --> 00:07:45.230 - little. Um? 00:07:46.830 --> 00:07:50.574 - You know Maine dot JS or some kind of large JavaScript file 00:07:50.574 --> 00:07:54.318 - that all of our TypeScript is going to compile too and get 00:07:54.318 --> 00:07:58.374 - sent over the wire so we can put a breakpoint on that API 00:07:58.374 --> 00:08:01.806 - endpoint on the front end as well, and then you'll notice 00:08:01.806 --> 00:08:06.174 - that I have a few extensions and see if I can show those really 00:08:06.174 --> 00:08:09.606 - quick. So I think they're actually down here. This is just 00:08:09.606 --> 00:08:11.166 - really crazy looking, so my 00:08:11.166 --> 00:08:13.838 - extensions are. Remove you, Heather. 00:08:15.660 --> 00:08:17.760 - What? 00:08:19.810 --> 00:08:23.554 - Will be under elements similar should have in here. OK so that 00:08:23.554 --> 00:08:27.922 - I have scope. Scope is 1 for angular JS an in state is for 00:08:27.922 --> 00:08:31.354 - the new angular so will have that nice little guy that'll 00:08:31.354 --> 00:08:35.410 - give me some stuff there. I don't know why I might have to 00:08:35.410 --> 00:08:39.154 - restart my application to see if that's exactly what I'm going to 00:08:39.154 --> 00:08:41.026 - do. I'm going to take this 00:08:41.026 --> 00:08:45.656 - breakpoint off. Stop this and restart it here. 00:08:47.050 --> 00:08:48.730 - See if I can get this sucker working. 00:08:50.340 --> 00:08:54.438 - Where'd you go? 00:08:55.630 --> 00:09:01.366 - Is your connection string set to your DVD or an SQL be? 00:09:02.310 --> 00:09:05.847 - It is set to mine. Could call out though. 00:09:06.970 --> 00:09:09.670 - It's not that. 00:09:10.200 --> 00:09:16.080 - Man, I have my own little user I put in here is world cities. 00:09:16.080 --> 00:09:18.600 - That's mapped to the database as 00:09:18.600 --> 00:09:22.578 - well. There we go, we did it. Sometimes you just have to turn 00:09:22.578 --> 00:09:25.372 - it off and turn it back on again. That's the secret. 00:09:27.060 --> 00:09:32.910 - Cool, so we're going to go back to our controller, which is not 00:09:32.910 --> 00:09:36.800 - open. Never gonna go to versus controller here. I'm going to 00:09:36.800 --> 00:09:40.583 - throw a breakpoint. Let's see in my throat right here. I think is 00:09:40.583 --> 00:09:44.948 - let me hit it right here, so I should be able to go to cities 00:09:44.948 --> 00:09:49.022 - and then get cities. Will hit on the break point so you can see 00:09:49.022 --> 00:09:53.096 - that this is hit and then I can simply walk through this by my 00:09:53.096 --> 00:09:56.297 - little tools appear. There are some hotkeys. I think it's like 00:09:56.297 --> 00:10:00.080 - F5 to step over. Sorry F-10 step over and we can step into 00:10:00.080 --> 00:10:03.863 - functions or step out of them. So here I'm just going to step 00:10:03.863 --> 00:10:08.728 - over them. So it should be just in this little bit here so you 00:10:08.728 --> 00:10:11.914 - can see that I'm actually hitting the returned await 00:10:11.914 --> 00:10:13.330 - method and I can. 00:10:13.860 --> 00:10:18.072 - Step over that and then it should step over that and then 00:10:18.072 --> 00:10:19.476 - continue the process there. 00:10:20.960 --> 00:10:23.090 - Shakespeare 00:10:23.090 --> 00:10:26.830 - play. Come on, baby. 00:10:27.400 --> 00:10:33.665 - It looks like it's still pending here. 00:10:35.060 --> 00:10:36.629 - My stuck somewhere. 00:10:38.490 --> 00:10:42.468 - Don't know why. 00:10:43.280 --> 00:10:45.600 - Seems like. 00:10:47.140 --> 00:10:50.548 - Get the API call is failing and retrying. 00:10:52.330 --> 00:10:54.542 - So let me go ahead and see if I can remove my break point 00:10:54.542 --> 00:10:55.648 - and see if that'll fix her up. 00:10:57.240 --> 00:11:03.664 - You can just hit continue inside of Visual Studio. That's that's 00:11:03.664 --> 00:11:07.168 - what I was about to say. 00:11:07.690 --> 00:11:11.878 - It's the green I was looking forward to that green guy. OK, 00:11:11.878 --> 00:11:15.717 - that's what it is Haha. I thought that's what this button 00:11:15.717 --> 00:11:20.603 - was. Nose like water that little guy and I was like what is what 00:11:20.603 --> 00:11:24.791 - is this? I'm sorry man. I'm letting you roast over there and 00:11:24.791 --> 00:11:25.838 - not saying anything. 00:11:25.850 --> 00:11:29.256 - I'm just fumbling trying to be a back end developer in front of 00:11:29.256 --> 00:11:32.138 - everybody. I mean my feelings are hurt or anything or plan 00:11:32.138 --> 00:11:35.020 - totally familiar. Name starts with C so you can see sharply. 00:11:35.850 --> 00:11:40.602 - So yeah, so our API endpoint comes back just fine there on 00:11:40.602 --> 00:11:46.542 - the front end and then let's try to find it on the front end and 00:11:46.542 --> 00:11:52.086 - see if we can stop it. So this is our cities component. We know 00:11:52.086 --> 00:11:56.046 - it's happening here, so whenever we're making that call it's 00:11:56.046 --> 00:11:58.026 - probably on this load data. 00:11:58.720 --> 00:12:03.050 - And we're calling get data and then passing in that. 00:12:03.600 --> 00:12:07.851 - Let's see here. I think we just want this. The is this the 00:12:07.851 --> 00:12:12.765 - individual city. So let's see this that load data load data 00:12:12.765 --> 00:12:16.715 - brings into querystring. Is null page meant? Is that index 00:12:16.715 --> 00:12:20.270 - default page with query looks like the red thing. 00:12:21.140 --> 00:12:23.360 - Yeah, should be this guy here, 00:12:23.360 --> 00:12:26.696 - OK? And then that's going to call or get data. 00:12:27.760 --> 00:12:30.256 - That's going to be our cool. 00:12:32.590 --> 00:12:34.330 - It should be building out. 00:12:35.970 --> 00:12:39.830 - Are Cool. Alright. 00:12:40.550 --> 00:12:42.328 - See if I can find this character. 00:12:44.010 --> 00:12:46.986 - There should be API cities, so let me just look for get 00:12:46.986 --> 00:12:49.218 - data. So I'm going to go to my sources. 00:12:52.780 --> 00:12:53.968 - I click on my. 00:12:54.900 --> 00:12:58.475 - Nice little, this is my main JS and I believe they actually have 00:12:58.475 --> 00:13:02.600 - it all broken up here so I'm going to just do a control F and 00:13:02.600 --> 00:13:06.725 - I'll try to bring this over so I can see it a little bit better 00:13:06.725 --> 00:13:08.375 - because this is a little bit 00:13:08.375 --> 00:13:15.164 - wild. Very big and I'm going to see if I can get it. Was called 00:13:15.164 --> 00:13:17.770 - get cities. And our component. 00:13:20.880 --> 00:13:22.400 - What city at it? 00:13:23.360 --> 00:13:26.510 - I'm pretty sure your trusted Price after paspor specs. 00:13:27.390 --> 00:13:30.090 - You're not 00:13:30.090 --> 00:13:33.896 - wrong. Get good 00:13:33.896 --> 00:13:36.850 - data. Get data. 00:13:38.760 --> 00:13:42.540 - And there might be one of those for countries in. 00:13:44.090 --> 00:13:49.298 - Clean your radio. Honest is it the city service? 'cause I think 00:13:49.298 --> 00:13:53.204 - that was the service directly. That's the service directly. 00:13:53.960 --> 00:13:56.914 - This is what we want, isn't it? 00:13:58.510 --> 00:14:02.965 - Make sure this is the correct class here. Now that's the 00:14:02.965 --> 00:14:07.420 - countries you alright so that that person is the countries and 00:14:07.420 --> 00:14:09.445 - then this one should be. 00:14:10.770 --> 00:14:12.090 - Our cities. 00:14:14.100 --> 00:14:17.230 - Cities. We did it. 00:14:17.840 --> 00:14:21.578 - Tell me to put a breakpoint here and I'm gonna reload my page and 00:14:21.578 --> 00:14:25.049 - as soon as I reload. Since this is happening on load, it should 00:14:25.049 --> 00:14:27.986 - hit my breakpoint and we can kind of walk through that. 00:14:28.670 --> 00:14:35.209 - So same thing here. We have our little over and then into and 00:14:35.209 --> 00:14:41.245 - out of function and our play button. If we just want to 00:14:41.245 --> 00:14:43.760 - resume it. Another cool feature 00:14:43.760 --> 00:14:48.166 - an. In Chrome, is that if you and I think this is an edge to 00:14:48.166 --> 00:14:50.794 - with their new chromium motor was kind of playing with it the 00:14:50.794 --> 00:14:53.203 - other day whenever it came out with the Windows Update, but 00:14:53.203 --> 00:14:56.050 - you can turn on and turn off your break point. So if you 00:14:56.050 --> 00:14:58.021 - want to deactivate your breakpoints and like leave this 00:14:58.021 --> 00:15:00.868 - open. Say you made like some kind of fixed to your front end 00:15:00.868 --> 00:15:03.277 - code and you don't want to keep hitting the same breakpoint 00:15:03.277 --> 00:15:05.467 - instead of just like taking your break point often losing 00:15:05.467 --> 00:15:08.095 - your place, you can just hit this and Deactivate it. So what 00:15:08.095 --> 00:15:10.942 - kind of do that here in a second just to see how that 00:15:10.942 --> 00:15:13.351 - works. But basically we can step over should be able to 00:15:13.351 --> 00:15:15.541 - right click the break point and do that as well. 00:15:16.770 --> 00:15:19.820 - I think you're right. Disable continue remove 00:15:19.820 --> 00:15:21.560 - disabled. Yeah Boo. 00:15:23.850 --> 00:15:27.568 - And then yeah, this little guy up here or this little guy over 00:15:27.568 --> 00:15:31.572 - here so we can kind of see this. And then as these are going 00:15:31.572 --> 00:15:35.004 - through it, you can see what they are and then you'll have 00:15:35.004 --> 00:15:38.722 - your nice little local tab here so you can see what like this 00:15:38.722 --> 00:15:42.154 - should have like you know all the local variables to this and 00:15:42.154 --> 00:15:45.872 - then it should have like even what this is. So yeah, so we 00:15:45.872 --> 00:15:48.732 - know that this in this particular area of the code 00:15:48.732 --> 00:15:51.592 - still refers to the cities component. So if you have 00:15:51.592 --> 00:15:54.166 - anything like this dot sort direction this keyword still. 00:15:54.200 --> 00:15:57.668 - You know, is pointed at the component itself, so you get to 00:15:57.668 --> 00:16:01.425 - see all your nice little stuff as they kind of come along. And 00:16:01.425 --> 00:16:05.471 - this guy in your little scope box and then as well as like you 00:16:05.471 --> 00:16:09.228 - can just hover over them here so we know that's null. And then 00:16:09.228 --> 00:16:12.696 - this is going to be undefined until we actually do stuff with 00:16:12.696 --> 00:16:15.875 - it. And then we can just step into this next one. 00:16:17.080 --> 00:16:21.422 - And then it'll actually go to the bit here and build out our 00:16:21.422 --> 00:16:25.764 - nice little base URL and set all the params like we did last 00:16:25.764 --> 00:16:31.072 - time. Step over all this stuff and then it will actually hit 00:16:31.072 --> 00:16:32.680 - our API endpoint here. 00:16:34.640 --> 00:16:37.511 - And again, you can see what you know, what your filter 00:16:37.511 --> 00:16:40.904 - query is. It does not look like we have one and see what 00:16:40.904 --> 00:16:44.036 - our params are and those are all the programs that we kind 00:16:44.036 --> 00:16:45.341 - of built out while ago. 00:16:48.470 --> 00:16:52.253 - And then we can just play and then I'll roll through it and 00:16:52.253 --> 00:16:53.708 - then since we deactivated our 00:16:53.708 --> 00:16:56.830 - break point. If we go ahead and. 00:16:57.460 --> 00:17:01.060 - Refresh the page. It'll just kind of ignore it, but if we 00:17:01.060 --> 00:17:02.260 - turn it back on. 00:17:03.820 --> 00:17:06.180 - Nearest refresh the page it should just take us right 00:17:06.180 --> 00:17:07.360 - back to where we were. 00:17:14.080 --> 00:17:16.300 - Or did it actually remove it, 00:17:16.300 --> 00:17:17.040 - removed it? 00:17:17.860 --> 00:17:20.410 - No. 00:17:20.980 --> 00:17:23.760 - Right now. Round one. 00:17:24.490 --> 00:17:26.954 - I might have removed it on us, 00:17:26.954 --> 00:17:30.470 - but. Typically I you can just deactivate and that's and then 00:17:30.470 --> 00:17:33.530 - you can reactivate it and you owe. It looks like it's actually 00:17:33.530 --> 00:17:37.355 - saved it for us here, so let me just turn that bad boy back on. 00:17:43.000 --> 00:17:47.791 - Boom Read it again and there's another thing called resource 00:17:47.791 --> 00:17:51.740 - Maps with JavaScript that you can set so it's something that 00:17:51.740 --> 00:17:56.407 - we do as well that you can basically kick out a bunch of 00:17:56.407 --> 00:18:00.715 - your. You know if you minify files and kind of like uglify 00:18:00.715 --> 00:18:05.382 - them basically and you like golf them. So if you like use webpack 00:18:05.382 --> 00:18:10.049 - or any other like module loader, you can send them as like little 00:18:10.049 --> 00:18:13.998 - bitty minified packets over the wire. You kind of do what's 00:18:13.998 --> 00:18:15.075 - called lazy loading. 00:18:15.110 --> 00:18:19.010 - But whenever they get sent over the wire, there really ugly and 00:18:19.010 --> 00:18:22.585 - just minified, engulfed, and by Gulf time mean. Like you know, 00:18:22.585 --> 00:18:26.160 - the variables can be turned into like you know, literally letters 00:18:26.160 --> 00:18:29.410 - and stuff like that, so it's kind of undiscernable. What 00:18:29.410 --> 00:18:33.310 - actually is going on in the browser? If you were to put 00:18:33.310 --> 00:18:36.885 - breakpoints on something. But if you send Maps over the wires, 00:18:36.885 --> 00:18:41.110 - will it kind of let your browser like take those apart and you 00:18:41.110 --> 00:18:44.685 - can UN minify files in the browser with Google Chrome and 00:18:44.685 --> 00:18:49.208 - other like. Up to speed dev tools you can't really do it in 00:18:49.208 --> 00:18:53.384 - IE9 or anything like that or IE 1011, but with edges new 00:18:53.384 --> 00:18:56.516 - chromium engine and then with you know. Obviously Google 00:18:56.516 --> 00:19:00.344 - Chrome and Mozilla and stuff like that. You can roll through 00:19:00.344 --> 00:19:04.868 - that fairly easily. Can you all hear me? I think my air pods 00:19:04.868 --> 00:19:06.970 - just died. Yeah. 00:19:07.960 --> 00:19:13.693 - Oh man, OK. Only one of my airpods is working right now so. 00:19:13.850 --> 00:19:17.270 - And that's basically it. I think most of us, you know we're 00:19:17.270 --> 00:19:20.690 - pretty used to, you know, doing some stuff. Maybe some of us 00:19:20.690 --> 00:19:23.540 - learn some stuff, but that's essentially it on our training. 00:19:23.540 --> 00:19:27.815 - And then as far as like all the code goes here, if you guys just 00:19:27.815 --> 00:19:32.090 - want to kind of like tear into this on on your own and see what 00:19:32.090 --> 00:19:35.795 - you can kind of make changes and see how this changes kind of 00:19:35.795 --> 00:19:39.500 - apply. And then we're going to bake that into, you know, one of 00:19:39.500 --> 00:19:43.490 - our next trainings as well and see if we can come up with their 00:19:43.490 --> 00:19:47.586 - own features. Or something along those lines. Does anybody have 00:19:47.586 --> 00:19:52.410 - any questions for the? Yeah, I just wanted to chime in first 00:19:52.410 --> 00:19:56.832 - thanks sebyan. Good job slogging it out. Going through all that. 00:19:57.430 --> 00:20:01.159 - There there might be some other debugging areas that you might 00:20:01.159 --> 00:20:05.227 - have questions on, so feel free to share those here or later 00:20:05.227 --> 00:20:09.634 - during the week next week so we can cover them in next week's 00:20:09.634 --> 00:20:14.041 - training. I think a lot of times the ability to debug is probably 00:20:14.041 --> 00:20:17.770 - one of the most critical tasks, and if you're really efficient 00:20:17.770 --> 00:20:21.499 - with it, you can get a solution very quickly and efficiently. 00:20:21.499 --> 00:20:26.245 - And if you're not, you can beat your head against the wall for a 00:20:26.245 --> 00:20:30.313 - long time, so I really encourage you to think about this one. 00:20:30.320 --> 00:20:34.198 - The other thing is I would like to kind of go around the room 00:20:34.198 --> 00:20:35.583 - and the next week's training. 00:20:36.180 --> 00:20:40.525 - And just see if anyone has issues with getting their local 00:20:40.525 --> 00:20:45.265 - spun out for this and just encourage you to get a local 00:20:45.265 --> 00:20:46.845 - working before next week's 00:20:46.845 --> 00:20:51.900 - training. So we can interact with you guys around this. Alot 00:20:51.900 --> 00:20:56.421 - of what this book covers and the topics that this application 00:20:56.421 --> 00:21:00.531 - kind of shows in example form are really, really fundamental. 00:21:00.531 --> 00:21:03.819 - They're pretty simple, but they're not necessarily all 00:21:03.819 --> 00:21:09.573 - easy. I think for some of the folks on the line, they might be 00:21:09.573 --> 00:21:14.094 - easy, but for a lot of folks these are really fundamental 00:21:14.094 --> 00:21:19.026 - things that you can take apart and put back together and really 00:21:19.026 --> 00:21:21.903 - kind of help yourself crystallize that information. 00:21:21.940 --> 00:21:26.178 - And the book will give you something to kind of use as a 00:21:26.178 --> 00:21:29.764 - map or a guidebook as you kind of formulate your crystallized 00:21:29.764 --> 00:21:33.024 - thoughts. It's just a great little simple project that kind 00:21:33.024 --> 00:21:36.936 - of is fundamental in nature, but very powerful. To give you a 00:21:36.936 --> 00:21:40.196 - solid foundation if you don't already have one in these 00:21:40.196 --> 00:21:43.782 - different topic areas. So if you're going to spend some time 00:21:43.782 --> 00:21:48.020 - and you're like you know you tell Chris or Eric or myself or 00:21:48.020 --> 00:21:51.932 - others that you know you learn by doing, this is a great. 00:21:51.990 --> 00:21:56.100 - Thing to do and you have to do it, though you have to take the 00:21:56.100 --> 00:21:59.662 - time and spend some time digging into this. If you want to, you 00:21:59.662 --> 00:22:02.128 - know, crystallize those thoughts, but this is, you know, 00:22:02.128 --> 00:22:05.964 - a new stack of some of the newer stack of technology and you get 00:22:05.964 --> 00:22:09.800 - to be very hands on and kind of play with this and we're trying 00:22:09.800 --> 00:22:13.636 - to help walk you through an it really does cover a lot of the 00:22:13.636 --> 00:22:17.198 - basic things that you would expect to need to know how to do 00:22:17.198 --> 00:22:19.116 - on the front end and back end. 00:22:19.650 --> 00:22:22.430 - So anyway, with that, let's turn it over for questions. 00:22:24.150 --> 00:22:25.010 - Or comments?