CEF Client Project Review
00:00:04.960 --> 00:00:06.100
So here we go.
00:00:06.780 --> 00:00:12.800
So the first thing you should do
is just open your like most time
00:00:12.800 --> 00:00:16.225
and stuff. Do you go
to your stuff folder?
00:00:27.080 --> 00:00:30.110
You know, but it's not.
00:00:30.110 --> 00:00:37.196
Test. Alright cool
alright so whenever you go to
00:00:37.196 --> 00:00:41.860
Steph. Obviously there's going
to be this nice little file down
00:00:41.860 --> 00:00:46.215
here for the code UI workspace,
and you can open that bit an
00:00:46.215 --> 00:00:49.230
code. I think that almost
everybody knows it's already
00:00:49.230 --> 00:00:51.240
fixed. Then I like that now.
00:00:51.260 --> 00:00:54.510
OK, what was the deal?
00:00:54.510 --> 00:00:58.140
Weird cache issue with Skype.
00:00:58.140 --> 00:01:03.468
Thanks Ben R refresh. Thank you.
Computer is allergic to add a
00:01:03.468 --> 00:01:09.685
cash.
I
00:01:09.685 --> 00:01:15.420
guess.
00:01:15.420 --> 00:01:21.690
Fungus fungus.
In memory challenge.
00:01:22.400 --> 00:01:26.276
Yeah, when you move like this
00:01:26.276 --> 00:01:32.024
vehicles there. Alright, so in
the code UI workspace and then
00:01:32.024 --> 00:01:38.114
what we can do to kind of hit an
endpoint if you'll need to open
00:01:38.114 --> 00:01:41.768
Visual Studio as an
administrator to be able to
00:01:41.768 --> 00:01:43.798
debug and attached to it.
00:01:44.460 --> 00:01:50.088
So we'll just open this guy up.
Cashew grows in the bottom of a
00:01:50.088 --> 00:01:51.294
cashew Apple. Yeah.
00:01:51.930 --> 00:01:57.294
You're hijacking training. I
don't wanna learn about not
00:01:57.294 --> 00:02:01.170
stand. Cashews. There
00:02:01.170 --> 00:02:07.483
is bruising. Cash and see yeah
it grows on the bottom of the
00:02:07.483 --> 00:02:14.161
Cashew Apple. It's inside the
Elemental. Yeah. As as as fun
00:02:14.161 --> 00:02:20.451
as that is. I mean, you're
disrespecting training for real.
00:02:22.060 --> 00:02:26.032
So now that we have this opened
as administrator, what you can
00:02:26.032 --> 00:02:30.335
do is go to your IIS and you
basically want to figure out
00:02:30.335 --> 00:02:34.638
which one is your like which
worker process your API is so we
00:02:34.638 --> 00:02:39.603
can connect to it. Easiest way
to do that is just to go to your
00:02:39.603 --> 00:02:42.913
server and click on this guy
under IIS called worker
00:02:42.913 --> 00:02:48.900
processes. And then you can see
which process ID it is. So in
00:02:48.900 --> 00:02:54.710
this case is 3364 for our API.
So then we go up to debug.
00:02:55.350 --> 00:02:58.950
And then with your solution
of an obviously and then
00:02:58.950 --> 00:03:00.030
attach to process.
00:03:01.700 --> 00:03:05.352
And you can filter through all
these processes just by typing
00:03:05.352 --> 00:03:10.000
in W 3 to get everything I, S,
and then we're going to 3364.
00:03:11.290 --> 00:03:17.010
And then successfully attached
to it. So basically what I want
00:03:17.010 --> 00:03:20.872
to do? Is this thing that
00:03:20.872 --> 00:03:25.816
I'm debugging? You're not gonna
know for sure that you're
00:03:25.816 --> 00:03:29.886
successfully attached unless you
see a filled in breakpoint on
00:03:29.886 --> 00:03:35.991
the side of your of a CSV file.
So go ahead and put it break
00:03:35.991 --> 00:03:37.212
point on line.
00:03:46.060 --> 00:03:49.486
China don't know why it's not.
00:03:49.490 --> 00:03:52.244
Cool math, yeah, we just
actually go to you.
00:03:52.850 --> 00:03:58.506
Alright cool and you'll see that
it is a filled in red dot as
00:03:58.506 --> 00:04:03.354
opposed to a unfelt in dot,
which means that it is actually
00:04:03.354 --> 00:04:08.606
attached to the symbols that CSS
file is creating. If it isn't a
00:04:08.606 --> 00:04:13.050
filled in dot, that means it's
attached to the process, but
00:04:13.050 --> 00:04:15.878
you're not going to be able to
00:04:15.878 --> 00:04:19.172
debug properly. How so say like
assemblies haven't been loaded
00:04:19.172 --> 00:04:22.571
or something like this project
or the DLL is currently bill
00:04:22.571 --> 00:04:25.661
isn't reflected in the code that
you're looking at. Something
00:04:25.661 --> 00:04:29.369
changed since that deal was
built, so it's not going to be
00:04:29.369 --> 00:04:30.605
able to step through.
00:04:31.370 --> 00:04:34.502
Cool, sorry, I know you are
good. Thanks, Brendan.
00:04:35.120 --> 00:04:40.772
And then So what we're going to
do is look for endpoint
00:04:40.772 --> 00:04:43.127
basically on what we're wanting
00:04:43.127 --> 00:04:48.570
to hit. So I think
on this one.
00:04:50.260 --> 00:04:53.770
I want to see what let's
00:04:53.770 --> 00:04:58.630
see here. You could do it as
well as the attributes anything
00:04:58.630 --> 00:05:03.796
is. Yeah, get all this thing as
tabs listing, so I think it said
00:05:03.796 --> 00:05:08.593
get attributes of tab listing so
you can see that I'm hooked up
00:05:08.593 --> 00:05:12.283
to this service getting
attributes so I can just click
00:05:12.283 --> 00:05:14.866
on this and hit up 12 or
00:05:14.866 --> 00:05:17.324
controller function. Or not on
00:05:17.324 --> 00:05:22.070
my laptop. So this is basically
where the routes are with this
00:05:22.070 --> 00:05:26.041
is auto generated from the C
Sharp routes in TypeScript. That
00:05:26.041 --> 00:05:30.373
kind of list out your methods
and API calls and kind of
00:05:30.373 --> 00:05:34.344
concatenates them with the root
URL for you and whatever params
00:05:34.344 --> 00:05:39.759
you pass in as your data and you
can see that this is a post
00:05:39.759 --> 00:05:43.369
method and then this is
obviously in our query E
00:05:43.369 --> 00:05:47.701
Commerce dot attributes TS. So
then we can go to the endpoint
00:05:47.701 --> 00:05:51.640
attributes. Slash attribute tabs
listing and that will be
00:05:51.640 --> 00:05:56.580
essentially what we want to get.
So let's go to our solution and
00:05:56.580 --> 00:05:59.240
it's going to be an 06 services.
00:05:59.750 --> 00:06:07.347
And then. Most everything is
going to be an 06 and it was
00:06:07.347 --> 00:06:10.695
in attributes. Go
00:06:10.695 --> 00:06:14.218
back. Tributes attribute
tabs listing.
00:06:17.440 --> 00:06:18.765
Where is attributes going to
00:06:18.765 --> 00:06:20.830
Brandon? The product.
00:06:21.620 --> 00:06:23.060
It probably is.
00:06:25.430 --> 00:06:31.225
Probably not.
Basically everything has
00:06:31.225 --> 00:06:37.275
attributes, not just products. I
would search for attribute slash
00:06:37.275 --> 00:06:41.466
attributes. Just a solution wide
search, because every API
00:06:41.466 --> 00:06:45.489
endpoint has the route and the
comments above it.
00:06:46.280 --> 00:06:48.365
Attributes
00:06:48.365 --> 00:06:51.898
tab Just like in that.
00:06:52.630 --> 00:06:57.180
Comment at the top of that.
Yeah, because the path.
00:06:58.010 --> 00:06:58.390
What?
00:07:00.280 --> 00:07:04.474
Search not supported in this
project and autos window.
00:07:04.760 --> 00:07:06.030
Where's my search window, yeah.
00:07:06.740 --> 00:07:09.440
Condition.
00:07:11.260 --> 00:07:12.430
Boom
00:07:23.880 --> 00:07:28.980
And the endpoint should be the
only place that has it actually
00:07:28.980 --> 00:07:31.105
spelled out with the path.
00:07:58.770 --> 00:08:01.538
This should be it.
00:08:01.540 --> 00:08:07.098
Oh God, first try. I was like I
should've hit by find all so
00:08:07.098 --> 00:08:11.862
here is going to be our route
and it's an attribute dot
00:08:11.862 --> 00:08:13.053
attribute tab service.
00:08:13.070 --> 00:08:16.394
Is basically just declaring what
it is and declaring it, but if
00:08:16.394 --> 00:08:20.272
you put a breakpoint on this, I
mean I think you can put a
00:08:20.272 --> 00:08:23.319
breakpoint on it, but you're not
going to actually like see
00:08:23.319 --> 00:08:24.704
anything happen here, you can't.
00:08:24.740 --> 00:08:31.796
Definition, but if you go to
where that DTO is used and
00:08:31.796 --> 00:08:36.314
the. API method then you can put
a breakpoint there. So I copied
00:08:36.314 --> 00:08:39.690
the call. Go ahead
and controller here.
00:08:41.300 --> 00:08:46.340
And then here's the actual posts
so you can see that we're
00:08:46.340 --> 00:08:49.700
posting and pushing get
attribute tabs, listing cashed,
00:08:49.700 --> 00:08:55.160
and then this little bit right
here. So I'm going to put a
00:08:55.160 --> 00:08:59.780
breakpoint on 313 so whenever it
hits this, we're actually going
00:08:59.780 --> 00:09:04.400
to walk through it. So if I'm
looking at this correctly.
00:09:05.330 --> 00:09:07.633
So the way I think it should
00:09:07.633 --> 00:09:10.817
happen on load.
Terrible using this
00:09:10.817 --> 00:09:14.030
things track that by
the way so.
00:09:16.330 --> 00:09:20.620
Take a break. Have a break point
here as well in that stuff.
00:09:20.630 --> 00:09:22.028
I'm not here in a second.
00:09:23.130 --> 00:09:28.998
Aqua group is Brandon. Nice
needs dance party 'cause
00:09:28.998 --> 00:09:34.214
somebody, somebody named Brendan
returning at you AG.
00:09:34.220 --> 00:09:37.780
Did you make this
00:09:37.780 --> 00:09:41.180
one? And this one is bringing.
00:09:41.180 --> 00:09:47.420
OK, Brandon.
I got to break points.
00:09:47.420 --> 00:09:49.340
Right, yeah?
00:09:50.450 --> 00:09:52.890
I received a message.
00:09:54.720 --> 00:10:00.722
OK, cool. I think we actually
did. We hit it on the back end.
00:10:01.570 --> 00:10:01.960
No.
00:10:03.060 --> 00:10:08.300
Jazz.
00:10:08.300 --> 00:10:14.808
It is.
So here it.
00:10:14.820 --> 00:10:19.680
More
00:10:19.680 --> 00:10:28.190
important.
I don't
00:10:28.190 --> 00:10:30.860
believe that.
00:10:32.480 --> 00:10:36.972
So
we're
00:10:36.972 --> 00:10:39.218
not.
00:10:39.220 --> 00:10:42.896
Method. To figure out
00:10:42.896 --> 00:10:48.263
why. So we got to see where
this resolved attributes
00:10:48.263 --> 00:10:49.317
being called.
00:10:52.730 --> 00:10:56.640
OK, in the constructor, so that
should definitely be running.
00:10:56.640 --> 00:11:01.876
Where are you? Are you looking
at the product details page?
00:11:04.030 --> 00:11:10.400
No. So I
think error. Sorry yes OK yeah.
00:11:10.930 --> 00:11:14.454
Like no, yes no
00:11:14.454 --> 00:11:20.984
I am. At the get attribute stabs
a listing. I think it should be
00:11:20.984 --> 00:11:24.954
hitting it 'cause it's going
into this doc. You all.
00:11:24.990 --> 00:11:26.958
Up and then.
00:11:26.970 --> 00:11:30.870
Let's now I'm sorry. I think
that might be a catalog one.
00:11:31.530 --> 00:11:37.120
The proud tab widget at it looks
very familiar on.
00:11:37.120 --> 00:11:38.488
She killed him digit.
00:11:39.290 --> 00:11:44.729
Yeah, that's. No, it says it's
imperative product detail.
00:11:44.730 --> 00:11:47.805
Killer where we're at. Product
00:11:47.805 --> 00:11:53.880
details. Most of the time on not
all the time for my experience,
00:11:53.880 --> 00:11:56.155
but most of the time.
00:11:56.160 --> 00:12:00.054
Like if it's actually in product
detail controls, that means it's
00:12:00.054 --> 00:12:01.116
going to be.
00:12:01.150 --> 00:12:04.570
There are plenty of things that
are reused everywhere, though
00:12:04.570 --> 00:12:08.674
like the image card is used like
in different places, so you
00:12:08.674 --> 00:12:10.384
can't really edit it, true.
00:12:10.980 --> 00:12:14.984
That sort of thing. So this is
credit card attributes, Chin
00:12:14.984 --> 00:12:17.532
Widget Controller. That's not
what we want.
00:12:18.150 --> 00:12:21.350
So product card attributes no.
00:12:22.630 --> 00:12:25.126
Product detail attributes which
it controller cool units
00:12:25.126 --> 00:12:29.182
product. So this is where it's
going to drop into it. So let's
00:12:29.182 --> 00:12:31.054
go ahead and put a breakpoint.
00:12:31.950 --> 00:12:37.482
On Go see if we're actually
rolling into that guy on on the
00:12:37.482 --> 00:12:38.946
load of the page.
00:12:39.760 --> 00:12:44.292
Maybe
this
00:12:44.292 --> 00:12:48.824
doesn't
have
00:12:48.824 --> 00:12:53.356
the
product
00:12:53.356 --> 00:12:57.888
details
tabs
00:12:57.888 --> 00:13:03.524
widget? No,
it was. What's interesting is
00:13:03.524 --> 00:13:04.706
hitting it before.
00:13:05.780 --> 00:13:09.938
Product detail attributes which
controller in my hand. There's
00:13:09.938 --> 00:13:12.248
product detail tabs widget now.
00:13:13.220 --> 00:13:17.630
But detailed tabs widget now has
the wrong one.
00:13:18.490 --> 00:13:24.178
Awesome Alright is this one? I'm
just lying. Is this one the
00:13:24.178 --> 00:13:26.074
whole time you guys?
00:13:26.230 --> 00:13:29.282
That were not six days. We want
00:13:29.282 --> 00:13:31.600
this guy. Where I had my
00:13:31.600 --> 00:13:33.720
previous break point.
Cool alright.
00:13:34.990 --> 00:13:42.172
So you can see it's
actually hitting that service.
00:13:43.360 --> 00:13:44.956
And then calling the back end.
00:13:45.900 --> 00:13:47.314
And it's not we have a problem.
00:13:49.820 --> 00:13:55.076
Maybe it doesn't have any
attributes. Well, yeah, check
00:13:55.076 --> 00:13:58.960
first. Bug and so basically the
reason. The reason we're doing
00:13:58.960 --> 00:14:03.250
this is because in the database
this has like a start date and
00:14:03.250 --> 00:14:07.540
end date, but it's not showing
up in the data model on the
00:14:07.540 --> 00:14:11.830
front end and it's in the
database so I got to see whether
00:14:11.830 --> 00:14:15.130
the those attributes aren't
getting passed in the front end
00:14:15.130 --> 00:14:20.080
from the back end so it could be
very well that the model in the
00:14:20.080 --> 00:14:23.710
back end doesn't have those
dates on it out of pressure,
00:14:23.710 --> 00:14:27.010
does they? But you just like
change their data models.
00:14:27.050 --> 00:14:30.118
So it could be something like
that, so we're going to go ahead
00:14:30.118 --> 00:14:31.298
and step over this assignment.
00:14:31.940 --> 00:14:34.756
Of this equals this.
'cause this is just.
00:14:36.180 --> 00:14:39.370
Fun angular JS compile stuff.
00:14:40.330 --> 00:14:43.760
And then it's going to return
this Q Function resolve
00:14:43.760 --> 00:14:46.847
reject. So we're going to
jump into that function.
00:14:49.900 --> 00:14:51.496
And we want to step over this
00:14:51.496 --> 00:14:53.656
function. We don't care about
00:14:53.656 --> 00:14:57.514
that. You don't care about any
of this stuff.
00:14:57.520 --> 00:15:01.010
Actually pull that inside here.
00:15:01.890 --> 00:15:04.314
So maybe we stepped
over too many times.
00:15:06.090 --> 00:15:09.350
Hello, it seems like it went
over everything no no.
00:15:10.710 --> 00:15:12.470
Well, she should sit idle.
00:15:13.420 --> 00:15:17.006
Play, put the breakpoint into.
Let's go ahead and put the
00:15:17.006 --> 00:15:20.266
bridge. Yeah, inside that way
see if we're actually hitting
00:15:20.266 --> 00:15:25.313
that guy. Free point break.
Would you subscribe to it now?
00:15:25.320 --> 00:15:31.808
Like to make a
factory out of you.
00:15:31.910 --> 00:15:39.890
And I can
also show fun
00:15:39.890 --> 00:15:47.870
JS example that
is confusing and
00:15:47.870 --> 00:15:52.100
buggy. Built into angular JS
that I solved yesterday. But is
00:15:52.100 --> 00:15:56.010
it? Angular index.
00:15:56.550 --> 00:16:01.026
Bye bye, it's not always what
you think it's going to be.
00:16:01.650 --> 00:16:06.545
OK, so it is actually hitting
this get attribute tabs listing
00:16:06.545 --> 00:16:12.330
which is I believe, the method
that we were trying to hit this
00:16:12.330 --> 00:16:19.005
guy let me just go go into that
again just to make sure and that
00:16:19.005 --> 00:16:23.455
was the attributes, attributes,
tab listing and this was the
00:16:23.455 --> 00:16:26.298
attribute. Attribute tabs
listing attribute tabs as
00:16:26.298 --> 00:16:30.228
listing and let's go back up to
the definition here.
00:16:30.990 --> 00:16:34.590
Make sure we're on the same
thing 'cause it could be spelled
00:16:34.590 --> 00:16:36.980
different. Try it, try it right.
00:16:37.590 --> 00:16:41.142
Attributes attribute tab
listing cashed OK, so this
00:16:41.142 --> 00:16:42.474
is actually attached.
00:16:43.820 --> 00:16:48.409
So we want it without the cash.
That's why we're not hitting it.
00:16:48.420 --> 00:16:50.460
You're right, look at that guy.
00:16:51.460 --> 00:16:54.835
There's just search
00:16:54.835 --> 00:17:00.063
for. Or or in this 'cause this
was the attributes tab listing.
00:17:00.063 --> 00:17:04.912
OK, so it is get attributes tabs
of listing get attribute tab OK.
00:17:05.730 --> 00:17:08.508
And then we're on the cash.
00:17:09.400 --> 00:17:13.264
And we need to be on Line 307
00:17:13.264 --> 00:17:15.320
instead. Cool.
00:17:19.030 --> 00:17:20.966
I'm always so bad at
spelling you guys.
00:17:21.980 --> 00:17:26.840
Alright. Here the keyboard.
That's it alright, that little
00:17:26.840 --> 00:17:31.065
arrow were in there, so now that
this actually open and we have
00:17:31.065 --> 00:17:34.965
an arrow, we can see that we're
actually hitting this method and
00:17:34.965 --> 00:17:39.515
what you can do is F-11 will
skip over an F-10 will go into
00:17:39.515 --> 00:17:41.465
from that mistake and it could
00:17:41.465 --> 00:17:42.115
be backwards.
00:17:42.130 --> 00:17:48.112
Action.
People are influenced stepping
00:17:48.112 --> 00:17:51.537
backwards. You can also hover
over the buttons at the top by
00:17:51.537 --> 00:17:55.262
the stop button. Where were the
top ones? Always use the
00:17:55.262 --> 00:17:58.221
keyboard up there by continue
and then about five buttons over
00:17:58.221 --> 00:17:59.297
do do do do.
00:17:59.840 --> 00:18:04.916
Show next step into OK, you're
right. Step into step over so
00:18:04.916 --> 00:18:07.454
we're going to head and step
00:18:07.454 --> 00:18:11.062
into that. And then this
00:18:11.062 --> 00:18:14.690
is services. Yes endpoint
00:18:14.690 --> 00:18:20.224
yeah. So sorry for any confusion
there, so we're in here and it's
00:18:20.224 --> 00:18:23.944
going to return get page
results. Passing in an interface
00:18:23.944 --> 00:18:26.920
attribute Tab, Model, Attribute
Tab Model Interface attribute
00:18:26.920 --> 00:18:31.012
tab, search model attribute tabs
tab page result, and some other
00:18:31.012 --> 00:18:35.104
other cool guys stuff that is
passing through that function as
00:18:35.104 --> 00:18:39.196
request. Rework closed attribute
tabs. So we're going to head an
00:18:39.196 --> 00:18:44.404
step into that guy that's 10 or
step over it 'cause I hit the
00:18:44.404 --> 00:18:49.941
wrong button. Go ahead
and run that guy again.
00:18:49.941 --> 00:18:52.856
I think I could just.
00:18:54.220 --> 00:18:56.050
Drag the serial back up here.
00:18:56.560 --> 00:19:03.205
Cool alright. Alright, Here we
go. You guys were inside the
00:19:03.205 --> 00:19:08.540
computer so we just probably
want to step over this step
00:19:08.540 --> 00:19:13.390
into it again with F-11. This
is just looks like.
00:19:14.840 --> 00:19:19.544
And just to get are essentially
we're going to step out, step
00:19:19.544 --> 00:19:20.720
back in OK.
00:19:22.300 --> 00:19:26.584
In this is get paged
results, so we're probably
00:19:26.584 --> 00:19:28.964
going to step into this.
00:19:30.220 --> 00:19:33.220
Step over that. Go into there.
00:19:35.490 --> 00:19:39.156
Step over the water object is.
00:19:39.950 --> 00:19:42.620
OK, just step over that.
00:19:50.230 --> 00:19:54.040
There's always a lot of stuff.
00:19:54.040 --> 00:19:55.760
No results right now.
00:19:56.440 --> 00:19:58.570
That's cool. And then.
00:19:59.360 --> 00:20:00.680
Probably going to have to.
00:20:03.260 --> 00:20:05.410
Go into that really quick.
00:20:07.840 --> 00:20:10.000
Alright, I think this
is actually you guys.
00:20:18.040 --> 00:20:21.736
So you'll generally see this
alot and like a CTX or
00:20:21.736 --> 00:20:24.760
context. But basically just
like getting context of like
00:20:24.760 --> 00:20:28.456
where something is an API,
you'll see that quite a bit.
00:20:33.830 --> 00:20:37.484
So this is just getting the
database context essentially.
00:20:41.360 --> 00:20:43.300
Then we should have.
00:20:44.260 --> 00:20:45.640
Nothing yet looks like.
00:20:48.040 --> 00:20:49.720
We can go over that.
00:20:51.290 --> 00:20:53.540
With zero results.
00:20:55.480 --> 00:20:56.569
All of our.
00:20:58.700 --> 00:20:59.470
Worst.
00:21:02.900 --> 00:21:05.236
There's probably this words
going to set it.
00:21:06.080 --> 00:21:07.000
Then
00:21:08.570 --> 00:21:11.942
Get her in a setter for the
result and it's setting them.
00:21:18.090 --> 00:21:19.968
Getting the paging.
00:21:21.770 --> 00:21:22.952
I would assume it's gonna set
00:21:22.952 --> 00:21:25.550
it. Setting the current count.
00:21:31.060 --> 00:21:33.012
See if we can have 10 over that
00:21:33.012 --> 00:21:36.216
guy. And see what
the results are.
00:21:39.140 --> 00:21:40.890
Alright. Nothing.
00:21:43.070 --> 00:21:47.000
He was going to return here.
00:21:47.550 --> 00:21:51.257
And another you already know,
but another tip for when you've
00:21:51.257 --> 00:21:54.290
isolated where this eventually
goes to and where you're
00:21:54.290 --> 00:21:57.660
thinking the problem is, just
put your breakpoint there and
00:21:57.660 --> 00:22:01.704
ate the old 'cause, then you'll
you'll skip the 'cause you know
00:22:01.704 --> 00:22:06.085
you have like. OK, hang on it
was it? Skip over, skip through
00:22:06.085 --> 00:22:10.129
at this point, like it again at
the Chris Reddick method. But
00:22:10.129 --> 00:22:12.151
trust me, if you think super
00:22:12.151 --> 00:22:15.644
help, great. It's like basically
if you. If you think you're
00:22:15.644 --> 00:22:19.010
going to step in another place
in your like debugging again.
00:22:19.640 --> 00:22:23.248
Just put a breakpoint there.
Yes, because you don't want to
00:22:23.248 --> 00:22:28.168
have to F 11 at 10 your way back
to that point 'cause its value.
00:22:28.170 --> 00:22:30.789
Really works, yeah.
00:22:30.790 --> 00:22:36.346
And sometimes you forget and
step into like you or like some.
00:22:36.346 --> 00:22:40.513
Some like new get package that's
doing something really
00:22:40.513 --> 00:22:44.724
complicated. In in this back end
code that has no bearing on the
00:22:44.724 --> 00:22:46.446
problem itself, so I think you
00:22:46.446 --> 00:22:49.966
guys were not. Getting what we
want out of this.
00:22:50.590 --> 00:22:51.790
This change resolve it.
00:22:53.650 --> 00:22:56.410
OK.
00:22:59.580 --> 00:23:02.658
These are just getters and
Setters, and that's a.
00:23:03.440 --> 00:23:08.230
The interface. So I don't think
that's what we want to do,
00:23:08.230 --> 00:23:11.211
'cause it looks like it's not
getting those at. That's not
00:23:11.211 --> 00:23:12.295
returning what we want.
00:23:13.020 --> 00:23:20.715
So. What is the problem
in UAGF at this time? OK, sorry,
00:23:20.715 --> 00:23:22.320
I'm just here.
00:23:22.320 --> 00:23:27.332
No, not serious, but it was. It
was dates missing but like on on
00:23:27.332 --> 00:23:30.554
what specific? So we have
available for available start
00:23:30.554 --> 00:23:34.850
date and available in date and
that is being saved in the
00:23:34.850 --> 00:23:38.232
database. If this would
slide for me, which would
00:23:38.232 --> 00:23:39.024
be really cool?
00:23:41.660 --> 00:23:46.423
Thank you cite as available and
available in date. Also, you
00:23:46.423 --> 00:23:50.753
guys will notice that there's a
method that I wrote.
00:23:51.680 --> 00:23:55.358
And here that. Is fixed date.
00:23:55.940 --> 00:24:01.400
Because right now it looks good.
Yeah, so dates a date object in
00:24:01.400 --> 00:24:07.280
JavaScript is not the same as a
date object in C sharp. So you
00:24:07.280 --> 00:24:11.480
have to kind of what's different
about Wiggles around everything.
00:24:11.640 --> 00:24:17.008
Completely different like format
and then you have to feed very
00:24:17.008 --> 00:24:22.376
specific things to subject as
strings, and if you don't you
00:24:22.376 --> 00:24:26.906
can't. Object and in angular as
we all know, if you're piping
00:24:26.906 --> 00:24:31.664
and date, it has to be a data
object, so that's cool guy
00:24:31.664 --> 00:24:35.306
stuff. Cool guy angular stuff,
which I think will probably
00:24:35.306 --> 00:24:39.310
you'll probably run into at one
point or another because we
00:24:39.310 --> 00:24:43.314
obviously store dates and and
it's not loading and it's not
00:24:43.314 --> 00:24:46.590
loading the available Thursday
and enable end date. That's
00:24:46.590 --> 00:24:50.594
exactly right. So those are as
attributes that used to be
00:24:50.594 --> 00:24:53.506
serializable attributes and new
data mapping they've been
00:24:53.506 --> 00:24:57.510
swapped around to just there
supposed to be available in the
00:24:57.510 --> 00:24:58.602
same scope as.
00:24:59.660 --> 00:25:03.080
Yeah, just it's under product so
it should be product dot, you
00:25:03.080 --> 00:25:06.500
know. And then for Kavian
Patrick to kind of see what I'm
00:25:06.500 --> 00:25:11.830
talking about. Let me go ahead
and go to my elements tab and so
00:25:11.830 --> 00:25:13.780
essentially if I click on my
00:25:13.780 --> 00:25:16.420
product here. Inspect it.
00:25:18.210 --> 00:25:19.798
And play the game.
00:25:20.530 --> 00:25:25.425
Of PDC that was it. Was it
product details control is
00:25:25.425 --> 00:25:28.620
probably right. Not
product to display.
00:25:29.650 --> 00:25:34.213
Actually, don't think this is a
specific one. I want to be in.
00:25:34.820 --> 00:25:39.050
Where is product to display.
This is a variant.
00:25:40.540 --> 00:25:41.230
Find.
00:25:43.910 --> 00:25:50.198
OK so it has created date. I'm
infect your part number name
00:25:50.198 --> 00:25:53.866
must purchase price production
associates, product categories,
00:25:53.866 --> 00:25:58.058
product notifications, quantity
master pack. Quantity per pallet
00:25:58.058 --> 00:26:01.953
requires. Stuff like that
serialized do an I think. I
00:26:01.953 --> 00:26:05.757
searched the research team again
just to make sure it's not in
00:26:05.757 --> 00:26:09.244
there, but that's where they
should be cut into that they
00:26:09.244 --> 00:26:12.414
should not be in serializable
attribute. That should be. Yeah,
00:26:12.414 --> 00:26:16.218
those updated date is just when
it was up. The actual product
00:26:16.218 --> 00:26:20.339
was updated. Not that other. So
on all of your SQL tables, it's
00:26:20.339 --> 00:26:23.826
always best practice to make a
creative Dayton updated date and
00:26:23.826 --> 00:26:27.947
then updated by and created by.
So you'll see that a lot. We
00:26:27.947 --> 00:26:30.800
follow standards and stuff and
we also follows MDM.
00:26:30.830 --> 00:26:34.340
So if they should not be in
serializable attributes because
00:26:34.340 --> 00:26:37.850
as a customer, whenever they
have serialized or they have
00:26:37.850 --> 00:26:41.009
attributes that we don't
necessarily save and it's custom
00:26:41.009 --> 00:26:44.168
to their business logic, we
shove him in here.
00:26:44.230 --> 00:26:46.890
So you'll see, kind of you know,
associated parts associated
00:26:46.890 --> 00:26:49.816
whole good and stuff like that,
but we should not see.
00:26:50.530 --> 00:26:53.056
Is what I want in here.
00:26:53.720 --> 00:26:54.280
Yeah.
00:26:55.310 --> 00:26:56.730
And it looks like.
00:26:59.870 --> 00:27:03.796
'cause they were in here at one
point and that's what it's wired
00:27:03.796 --> 00:27:07.420
for now. Obviously not showing
up there not in here any longer.
00:27:08.910 --> 00:27:12.010
Excellent.
00:27:14.010 --> 00:27:16.842
Well, it seems like the problem
is that they're not on projects.
00:27:16.842 --> 00:27:19.674
Then you'd be looking at like,
right? So that's why I was
00:27:19.674 --> 00:27:22.506
debugging. That goes to the back
end, like make sure why it
00:27:22.506 --> 00:27:23.686
wasn't getting like handed over.
00:27:24.330 --> 00:27:29.115
But we can kind of jump out of
this 'cause we have a 60 minute
00:27:29.115 --> 00:27:33.581
video and I can figure out this
bed on my own and just debugging
00:27:33.581 --> 00:27:37.592
stuff. But video. Video we're
going to watch T shirt video
00:27:37.592 --> 00:27:42.390
next week. And so basically
I'll go over one other
00:27:42.390 --> 00:27:44.150
solution that I solved.
00:27:45.560 --> 00:27:48.278
I solved yesterday.
00:27:48.540 --> 00:27:52.280
And this was actually. It was
pretty fun problem to figure
00:27:52.280 --> 00:27:57.370
out. 'cause? Definitely doesn't
make sense when you first got
00:27:57.370 --> 00:28:00.515
it. And then it makes perfect
00:28:00.515 --> 00:28:02.370
sense. You'll see.
00:28:03.100 --> 00:28:07.538
I'll show you how do I get to
Christ rules again? Was it under
00:28:07.538 --> 00:28:10.391
your vendors, right there
accounts or using it threshold?
00:28:11.250 --> 00:28:14.168
Boom Thank you card.
00:28:14.870 --> 00:28:18.206
My battery. I
00:28:18.206 --> 00:28:21.950
didn't know. 71 day.
00:28:22.470 --> 00:28:28.606
Yeah.
What do I crap battery man?
00:28:32.260 --> 00:28:50.585
Jackson
Why can't I have no sex with
00:28:50.585 --> 00:28:55.990
three money? I'm gonna need
about tree fiddy.
00:28:56.910 --> 00:29:00.358
Did your laptop is
00:29:00.358 --> 00:29:02.816
dying? Going to grab oh I see.
00:29:04.820 --> 00:29:08.138
This is that again, I forgot.
00:29:11.370 --> 00:29:15.342
Patrick laptops
00:29:15.342 --> 00:29:22.076
time. Project to
2nd one second old.
00:29:22.080 --> 00:29:24.480
Find something really
quick, yeah?
00:29:26.210 --> 00:29:28.940
OK.
00:29:30.700 --> 00:29:33.349
That works alright.
00:29:33.350 --> 00:29:35.708
Your question yet, do
you know how to turn
00:29:35.708 --> 00:29:36.756
on a static shipping?
00:29:38.410 --> 00:29:41.765
Like that, but we're talking
about with Merck. I found out
00:29:41.765 --> 00:29:45.120
that it's literally just saving
to the database, like there's no
00:29:45.120 --> 00:29:48.475
API to hit or anything, they
just they'll handle the shipping
00:29:48.475 --> 00:29:52.440
on their end. They just needed
to add $20 to the total words
00:29:52.440 --> 00:29:55.490
they select that option. It's
just typical business logic and
00:29:55.490 --> 00:30:01.108
check out. I kind of told him to
be done yesterday.
00:30:01.110 --> 00:30:05.766
That's correct on that one, so
that's OK. Alright, I'll let you
00:30:05.766 --> 00:30:08.038
know. Thank you guys.
00:30:09.460 --> 00:30:12.286
What is
00:30:12.286 --> 00:30:15.885
mine? Wait
00:30:15.885 --> 00:30:22.240
so? Peace, hard
to turn on.
00:30:22.860 --> 00:30:25.569
It's not a piece that could be
00:30:25.569 --> 00:30:28.700
turned on. Only grandpa
00:30:28.700 --> 00:30:34.926
Yes. That over promises
and under delivers really to
00:30:34.926 --> 00:30:38.760
grandpa. I know.
00:30:38.760 --> 00:30:45.904
So basically Forward
this is the issue in this
00:30:45.904 --> 00:30:48.914
code is if I can.
00:30:48.920 --> 00:30:54.884
To make dad jokes like another
dead, because then it's a Fox
00:30:54.884 --> 00:30:58.520
Spa. That's fine.
00:30:58.520 --> 00:31:05.584
So show you basically
what's going on here.
00:31:05.590 --> 00:31:10.034
Sorry if you guys do this
another way, I'm always just
00:31:10.034 --> 00:31:14.074
like digging into parents 'cause
it just I like it.
00:31:14.870 --> 00:31:16.628
Read it. Many many, many men
00:31:16.628 --> 00:31:21.106
Chris back. Love Shack
neighborhood. You things slowly.
00:31:21.110 --> 00:31:24.890
I don't know I I like like
figuring out the layers of
00:31:24.890 --> 00:31:28.670
stuff. So this is basically in
record. This is like the entire
00:31:28.670 --> 00:31:31.505
record here, and it's like
showing the different price
00:31:31.505 --> 00:31:35.600
rules that can be added on the
left and then pressures on the
00:31:35.600 --> 00:31:39.695
right right? So this is going to
be in the price rule accounts,
00:31:39.695 --> 00:31:41.270
which is an array, right?
00:31:41.940 --> 00:31:47.428
It's 13 long an every one of 'em
is just basically holds this and
00:31:47.428 --> 00:31:52.524
then the index of this, but the
issue is in the actual HTML.
00:31:53.780 --> 00:31:57.860
Is that you can see in this
energy repeat were doing AP,
00:31:57.860 --> 00:32:00.920
which should be probably
accounts instead of just PD,
00:32:00.920 --> 00:32:04.320
which I would encourage, like
writing code that makes sense.
00:32:04.320 --> 00:32:08.740
But this is just older code so
you have to up keep it.
00:32:10.000 --> 00:32:15.998
But so. Doing
a repeat and peeing price detail
00:32:15.998 --> 00:32:19.070
controller dot record dot
pressure accounts as many
00:32:19.070 --> 00:32:23.678
accounts there are, it's going
to basically you know pin to the
00:32:23.678 --> 00:32:28.286
page. Basically these guys right
here. So for every account is a
00:32:28.286 --> 00:32:32.510
red X and everything in that
array issue arises with it.
00:32:32.510 --> 00:32:36.350
Whenever we're piping this and
we're ordering by the account
00:32:36.350 --> 00:32:40.958
name or the account dot name. So
basically what that looks like
00:32:40.958 --> 00:32:44.414
on the page is even though
you'll have maybe.
00:32:44.490 --> 00:32:49.011
You know Aqua Blue pools of
Central Florida as zero? It
00:32:49.011 --> 00:32:53.943
might not be. Aqua pools of
Central Florida on the right, so
00:32:53.943 --> 00:32:57.231
you can see this ones actually
awkward international
00:32:57.231 --> 00:33:02.160
transaction. Which is not the
first one in the array. Scroll
00:33:02.160 --> 00:33:03.592
down on that list.
00:33:04.250 --> 00:33:11.367
OK, so basically whenever we
click and how index works is
00:33:11.367 --> 00:33:13.308
money sign index.
00:33:14.190 --> 00:33:18.051
As previously, this was just
engie click. Is removing
00:33:18.051 --> 00:33:23.199
account, and it was just money
sign index so that is only
00:33:23.199 --> 00:33:28.776
reading the index of where this
is in the HTML, so it was
00:33:28.776 --> 00:33:30.492
passing the remove account.
00:33:31.090 --> 00:33:34.740
To you know it was passing the
index of 0.
00:33:35.270 --> 00:33:39.250
To the account. And that's
actually going to remove aquatec
00:33:39.250 --> 00:33:43.230
internal transaction instead of
the one that you actually want,
00:33:43.230 --> 00:33:47.608
which is Aqua Blue pools of
Central Florida. So is it.
00:33:48.240 --> 00:33:52.980
Doing a sort on how it's
displayed or why is it different
00:33:52.980 --> 00:33:58.115
is doing a sort on how it's
displayed, but it's not doing a
00:33:58.115 --> 00:34:02.460
sort on the actual data array
itself, so that's that's the
00:34:02.460 --> 00:34:07.200
issue in index or money sign
index and angular JS will only
00:34:07.200 --> 00:34:11.940
give you the position or index
of the actual HTML which is
00:34:11.940 --> 00:34:15.100
filtered, so that's different
than the actual array.
00:34:15.690 --> 00:34:19.266
So basically the issue was is
whenever I clicked on this guy,
00:34:19.266 --> 00:34:23.140
maybe like a couple of guys down
here would delete and then like
00:34:23.140 --> 00:34:25.822
vice Versa 'cause it's not
alphabetical order. So every
00:34:25.822 --> 00:34:29.100
time you clicked on something
most likely what would happen is
00:34:29.100 --> 00:34:32.974
that it would not be the correct
account that was deleted. So are
00:34:32.974 --> 00:34:36.550
really funny way you can kind of
get around that in TypeScript.
00:34:36.550 --> 00:34:37.742
What you cannot do?
00:34:38.420 --> 00:34:42.132
Ann Is preschel
00:34:42.132 --> 00:34:45.739
detail. C remove account.
00:34:48.120 --> 00:34:51.420
So you'll see that we're just
using like a normal splice for
00:34:51.420 --> 00:34:54.720
the price rule accounts and
index one, so the index is like
00:34:54.720 --> 00:34:58.570
what you want to take out, and
then one is how many things are
00:34:58.570 --> 00:34:59.670
going to get deleted.
00:35:00.310 --> 00:35:05.250
And so, like another way to do
this would be in the TypeScript
00:35:05.250 --> 00:35:05.630
normally.
00:35:06.450 --> 00:35:10.760
Although.
00:35:10.760 --> 00:35:13.550
The normal. Pencil.
00:35:15.210 --> 00:35:17.380
Mean.
00:35:18.390 --> 00:35:19.510
Bill.
00:35:22.520 --> 00:35:24.005
So normally you could do
00:35:24.005 --> 00:35:24.599
something like.
00:35:25.100 --> 00:35:37.939
But
That spelled correctly.
00:35:39.510 --> 00:35:41.450
Oh record.
00:35:42.650 --> 00:35:46.210
Well, you'll notice that
we're getting basically this
00:35:46.210 --> 00:35:50.215
issue, because a number is
not assignable to the
00:35:50.215 --> 00:35:53.775
parameter type, price rule
account model, which is.
00:35:55.380 --> 00:35:58.682
I want to go ahead and go to
that to explain that, but
00:35:58.682 --> 00:35:59.698
basically it's an array.
00:36:00.210 --> 00:36:05.046
Of objects so in TypeScript you
can't say the index of an array
00:36:05.046 --> 00:36:09.138
of objects without doing like
some kind of Lambda function on
00:36:09.138 --> 00:36:14.546
it and. But the issue is when
you look for the index of an
00:36:14.546 --> 00:36:18.038
element in a collection, you
have to give it.
00:36:18.840 --> 00:36:24.395
The model that is of that
collection. Sure, an index which
00:36:24.395 --> 00:36:27.930
is the number, is not a price
00:36:27.930 --> 00:36:29.670
role model. Yeah.
00:36:30.360 --> 00:36:34.368
So that is a super simple way of
doing it. Obviously doesn't
00:36:34.368 --> 00:36:38.710
work. I mean you would like. I
mean, I obviously was like. I
00:36:38.710 --> 00:36:42.718
could probably totally do it
this way. I like, no, I'm done.
00:36:42.718 --> 00:36:47.394
I can't do it this way. So I
found a really super simple way
00:36:47.394 --> 00:36:51.402
of doing it and that's just in
the actual HTML. Wherever that
00:36:51.402 --> 00:36:55.000
guy went. Throughout
00:36:55.000 --> 00:36:58.690
No, so you can pass an
expression, obviously through
00:36:58.690 --> 00:37:03.610
angular JS and so in my engie
click methods, you can reference
00:37:03.610 --> 00:37:08.120
that index of P because we're
doing it repeating that product,
00:37:08.120 --> 00:37:12.630
so I just actually put remove
account and instead passing the
00:37:12.630 --> 00:37:18.370
money sign index, which is going
to be where it is in HTML. I
00:37:18.370 --> 00:37:22.880
passed in the actual index of
the object itself by saying
00:37:22.880 --> 00:37:26.160
preschel detailed controller
record, pressure decks of P.
00:37:26.190 --> 00:37:30.798
Returns the actual index of the
object that you want to prove
00:37:30.798 --> 00:37:32.718
out of the array, sure.
00:37:32.730 --> 00:37:35.958
Hey, I missed that.
00:37:35.960 --> 00:37:38.762
The things so long. Long story
00:37:38.762 --> 00:37:42.180
short. Don't use money Stein
index unless you absolutely
00:37:42.180 --> 00:37:45.180
have to, because if you ever
filter anything, this will
00:37:45.180 --> 00:37:46.380
always happen to you.
00:37:47.580 --> 00:37:49.380
Wait, but can you?
00:37:49.930 --> 00:37:52.867
I'm just thinking from a Cup
pagination thing might be best
00:37:52.867 --> 00:37:56.338
method. Can you not just do it
into BP images for every book
00:37:56.338 --> 00:37:58.474
that piece that you're
displaying, have it always
00:37:58.474 --> 00:37:59.809
display the whole Turkey? But
00:37:59.809 --> 00:38:04.240
Angie if. Certain criteria
matches then hides it, so where
00:38:04.240 --> 00:38:09.310
the index is still there, you
would have to filter it. By that
00:38:09.310 --> 00:38:14.770
you could also pass P itself and
then filter the one you want to
00:38:14.770 --> 00:38:15.940
remove IPS properties.
00:38:16.080 --> 00:38:22.572
Yeah you can. You can map over
it and the reason I.
00:38:22.580 --> 00:38:27.112
Play, that is, I would be
concerned that that index of
00:38:27.112 --> 00:38:28.760
would be run for.
00:38:29.870 --> 00:38:32.155
Every
00:38:32.155 --> 00:38:39.240
button. In the
HTML, whether or not it was
00:38:39.240 --> 00:38:42.240
clicked to generate that that
00:38:42.240 --> 00:38:49.198
value. As opposed to
just doing a.
00:38:49.200 --> 00:38:50.980
Search when it's clicked.
00:38:51.930 --> 00:38:55.512
What, why would it be run
without being clicked?
00:38:57.330 --> 00:39:01.926
'cause it is building out the
value that goes into the engie.
00:39:01.926 --> 00:39:05.373
Click attribute instead of
taking some static value and
00:39:05.373 --> 00:39:08.437
passing it to something that
runs a search.
00:39:09.420 --> 00:39:13.494
Yeah, you can do it that way. It
would just be you know, probably
00:39:13.494 --> 00:39:17.277
in case where you have like a
set of data or something like
00:39:17.277 --> 00:39:19.896
that. If you look faster,
particular case we're using
00:39:19.896 --> 00:39:23.097
forces so little it doesn't
really matter. Sure is like 13?
00:39:23.097 --> 00:39:26.589
Yeah, if you're using like if
you have a large collection or
00:39:26.589 --> 00:39:29.499
something like that I could
definitely see that. I'm just
00:39:29.499 --> 00:39:30.663
thinking of best practice.
00:39:31.400 --> 00:39:33.110
Enterprise level practice.
00:39:33.690 --> 00:39:36.826
Brandon level practice really
force enterprise random.
00:39:37.670 --> 00:39:41.030
Did you? Did you have another
way to do it?
00:39:41.530 --> 00:39:47.820
No, my little freaking away
comparatively. Just got said so.
00:39:47.820 --> 00:39:51.912
Yeah, definitely good. And then
I just didn't wait because you
00:39:51.912 --> 00:39:55.632
know, it's just the simplest. I
literally have changed nothing.
00:39:55.632 --> 00:40:00.468
Yeah sure. So I mean, you know
sometimes that works as well. In
00:40:00.468 --> 00:40:04.932
a perfect world where we had the
appropriate amount of time to
00:40:04.932 --> 00:40:06.420
make changes, I agree.
00:40:06.720 --> 00:40:10.440
I agree. Multiple winters
00:40:10.440 --> 00:40:12.200
feral cats.
00:40:12.990 --> 00:40:18.025
Other cats. No man, but
with this killer potato.
00:40:18.630 --> 00:40:22.205
I really like potatoes too
00:40:22.205 --> 00:40:26.150
far. To spend money in money?
00:40:26.810 --> 00:40:30.692
Now you just have to very
00:40:30.692 --> 00:40:33.778
expensive miata. You mean it's
00:40:33.778 --> 00:40:38.598
not accord? Oh, it does look
like kind of like a Honda Civic,
00:40:38.598 --> 00:40:42.174
right? But now, like now spent,
that is Brandon's Honda Civic L.
00:40:42.860 --> 00:40:46.940
I think there's a cheap now.
Brendan drives a Honda Civic and
00:40:46.940 --> 00:40:50.340
it's actually a lot faster than
KB's car right now.
00:40:50.350 --> 00:40:53.198
Infinitely faster, Oh yeah.
00:40:53.700 --> 00:40:58.556
Only hear back on that
recursively, faster, faster
00:40:58.556 --> 00:41:01.690
Britain's card. Lower years
00:41:01.690 --> 00:41:05.874
post. Basically Britain Speed
typing if it's cars getting
00:41:05.874 --> 00:41:09.501
disassembled, does that mean
he's going backwards? It 'cause
00:41:09.501 --> 00:41:11.516
it's less of a caramel?
00:41:11.600 --> 00:41:17.619
Yeah, maybe you need to probably
try to like run a clean and
00:41:17.619 --> 00:41:19.008
rebuild an impartial.
00:41:20.390 --> 00:41:22.960
OK.