All right. Can you guys see that?
OK, All right. So this is that this is
that prototype that I built is that I was
working with Cat and with ASD and, you
know, trying to figure out like what they
should look like. And of course us like
as we were kind of iterating through what
this should look like. And so now we've
got this in place as a guide, which is
good. That was a good
meeting earlier today with Brian. Now we
know we've got those, um.
Those are the services that he set up.
You know, we we had the is author Ken is
authenticated 1 is already existing and
then he set up the new card services that
we can use for this. So that's good Um.
I, I think here's what I'd like to
propose, um, and let me know if what
you guys think about this is that I
can go in like today and do two
things. I can update the the gaze test
dot JSON file to add an attribute for
practice. Test for every assessment that
has a practice test, because it's not all
of them, um. So I can I can
do that and then I can also build out a
little bit of the practice test dot JSON
file, enough that Matthew can get started
with his work. Like I'll put in data for
like 3 or 4 assessments.
And then, and then just commit my
changes, submit a PR to commit those to
trunk because it does, because that'll
just be fine for now. Um, in that way,
Matthew will hopefully have everything
that he needs in trunk because he will
have Brian's methods and then the, the
practice test information to, to start in
on his work. Does that, does that sound
reasonable?
Ohh yeah that sounds appreciate. Solid
plan, JSON file updates and strong YEAH
will make it easier for me to hook
into the new series right away.
Yeah, yeah.
And and I will also add Matthew, what
I'll do too is add a bunch of details to
the current JIRA ticket that we have for
this and assign that one to you so that,
so that the you know, the, the, the
different specifications for you were
clear that we have, you know, the
different requirements listed out.
Yeah, and.
To build, I think I'm going to tweak a
little bit. So so when I built my model
here, um, let me let me bring up that
code. OK, zoom in a little. When I built
my is that actually zooming in? I don't
know what that's doing. No, it's not Hang
on a second. OK, when I when I built
this, I put like a little pseudo data
file. Like it's, it's not really Jason,
but it's just sort of set up that way.
But I think, I think I'm gonna do make
a couple of tweaks in the actual JSON
file that I put in Angular. Because what
we know now is that.
There there's going to be like at least
one practice test in the future for some
fields in. So I think what I want
to do is have, you know, have have
a bit of information for every
assessment, but just just probably have
like a separate key value pair with an
array of like standalone of of.
Like whatever the bundles are or
something like that, Like I'll, I'll
basically I need to, I need to future
proof this a little bit because I don't
want to have it not work in the future
when we have more than one practice test
per field. Like right now, the way this
one is set up, right? This is the
information for math. So we have the test
code, we have the purchase code and the
price, etcetera. But in the. Future we're
going to have more than one practice test
for sales, so that needs. So I need to
like bury this in a different array,
right? I need to have like, um.
Make sure that we're saying for like
individually that this, that this
purchase code is aligned, that this one
single purchase code is aligned with
these Teslas and that a different
purchase code will be aligned with
different testlets etcetera, you know,
with different codes for the Tesla.
So I, I have an idea in mind to what that
should look like. I think I'm, I think
I'll just, I'll just do that and get it
into, um, you know, build that file, get
it in to trunk and then we can just make
any changes in that. We need to make sure
that our logic is going to work. But like
I was saying, at least that would give
Matthew some data to work from as he's,
as he's. Building out the page.
Yeah, Brian, I'm wondering would it be so
different than how we already do? Right
start. Ohh, let me, I will look at that.
It might not be Diane, it it might not be
that different at all. The different part
of it though, is the fact that we need a
way to determine which testlets are in
which bundle code. Yeah, that's why I was
hoping we could use some of the. Logic
that's there already because we have like
um, sub area codes assigned and usually
we call out those because those have
the assignments in the in the test
dot Jason file. So those assignments are
already defined. I just
thought maybe there's some way to go, you
know, utilize that information to call it
out. But then my understanding was Brian
did was saying no, no, we're going to
keep it separate. So the logic
would be different, yeah, but it's going
to be a little bit. Yeah, sorry,
Daniel, but then I was going to say no,
but then I was going to say, but then
like the way the right start is, it's
kind of. It's just kind
of a sign through the code itself, so
yeah. And how it's called up on each
page, um. So like we have
like, oh, oh, oh, 5/06/07 and then we
have and then we sell bundle of 05/06/07
or you can buy them individually. So
anyway, that's what right to start on on
series. I don't know. I'll, I will take a
look at it and see if you can see
if that that guides, you know, it might,
it might. Diane, thank you. That I think
because what I was thinking if you like
right now, right, this is representative
for like what we're looking at right now
is for 7:04 we have one standalone
practice tests in the individual
testlets, but when they add another one
we're going to have like a separate node
of info with like something like this
where we have the second form and then.
And then all of these will be like that,
you know what I mean? And so we have to,
we have to like have a way to do that
to build out. And what's the purpose of
having different practice tests? Just to
be a little more involved or Nope, Nope,
just just to give people more
opportunities for practice questions.
Candidates love them, so they'll, they'll
always. Like the one for free and then
and then if they want to purchase the
second one they can then that would be
more options. OK. Yeah, exactly. Yeah.
So I was trying to future proof for that,
although I was very encouraged by what
Dan Adelman said in the meeting
yesterday. You know, wouldn't this be
better if we didn't have a JSON file at
all, if we just. You
know, had a call to their database for
which practice, and the answer is yes, of
course, 100% yes. But. But there's no way
they're going to have that built for
December 2nd. Yeah, that way, you know,
because otherwise we're just duplicating
the exact same info on both sides. Yeah,
yeah. Ohh. That would open the door for a
lot of things then, I would imagine. Ohh,
yeah, that would be wonderful to have.
Yeah, because anything, anything that we
configure is a purchasable. We could just
pull the data from the from the database
that's that's a test name and a test
price and practice test and right starts.
And it's like it's all that stuff that
they have to configure and we have to
configure separately. That would
be so much better if we could just pull
from their database. Yeah, I know. It's
like a, you know, I'm so excited to now
to put in like 60 Texas right. Start
tests. Exactly. Yeah, exactly. Right. And
then if the name was Yeah, exactly.
That's it. That's it. Exactly. Done. We
had to we had to do all that work on the
CCIS site. Now we have to do it. On the
Angular site, it's our, it's in a
database. It's like, why? Why we keep
like repeating it. Yeah, Yep, that's
exactly it. Yeah. It'd be wonderful to
just have an API in place where we could
just grab that info, but we don't so.
So, and, and I wanted to, OK, so and
then, um, and thank you also bringing up
Diane that, you know, do do all current
assessments have practice tests? And the
answer is no. So, so they'll put that new
attribute in place for on the test at
JSON file. Just should we just call it
practice test in the list of attributes?
I think that's fine. Yeah, I
think so. I don't think we're using. We
now let me just check real quick because
we use practice tests for a number of
different things. I believe we do it on.
Which one on this now, um.
We use a different in different areas,
but I don't think we have one called
practice that we put in. And
we do not have. We
have no practice test. OK, so we do the
opposite. So if you have we do basically
if it's less, you know, in in a sense, we
take it off because there's like what the
series I'm looking at series right now.
That's why I've been but we say no
practice test. So if the majority of them
have practice tests, you could also do no
practice test and just once just exclude.
Yeah. Ohh, that's. I like that idea,
right, Right. Because, because, yeah, I
think it's like 2 of them that don't.
Yeah. Then just so you know, practice
test is what we use. Yeah, OK, I'll
confirm that, but that's OK. I like that.
I like that, Diane, Thank you. And then
if I'm not mistaken, I think that
eliminates it from the. A selector list
and they will not show up in your list.
But that logic is also in there already.
For that test selector, so they don't
even show up in that list. And I
think that's where that no practice test
might come in. Pretty sure 9 of well,
I take that back. I take that back,
that's on the other.
Yeah. Anyway, we do have logic to
eliminate, to exclude what's not in
there. I'm just kind of thinking off the
cuff here because with the series and
because I'm looking at serious because
the series, we also had a line item, a
row for practice tests. So this is not
going to be included in any kind of row
on the test. They just, it's just going
to show up on a standalone page. So
in this, correct. So in the in the
test service, we do have, uh, and there's
a service called test dot service dot TS
and in there there is logic for, I
believe, you know, excluding or
excluding. Certain things within that
test selector, I forget if it's, if it's
in that or if he's changed it, um.
Into something else. But if we're looking
at the components and then the.
Assessments control.
We have test select and test
select I think brings everything in.
Yeah. So we have if tests pretty sure
this works still fine. So we have
different conditions for filters excludes
if test attributes includes you know
certain things. So we have different ways
of controlling that test selector. So
this way they don't show up at all. And
I think we have we have one in there
right start, do we have one practice?
Score reporting.
No, we haven't had one so we could add
one for practice tests that would be in
the. Control
Test Selector I'm pretty sure tests and
the TS for that is where we
have.
I'm pretty sure that's still working and
wasn't reconfigured towards another model
at some point.
Alright, do you want me to share my
screen to show you where it is? Yeah.
Could you? Yeah. Could you show me what
you're looking at there? I want to see
where that is. I don't think I've looked
at this part of it yet. So we've got
basically a few versions of this then,
right?Yeah. So we
have the control here, which is and
then you just select the control and
then. Uh, let me
reflow. Did
I not briefly let me move that down?
Um, so this brings up the basic
control, I believe is how we have
that set up. And then back here
we have different conditions and I think
these are working. I'm pretty sure they
work. So we have, you know, if
it's right start. OK. Yeah.
But again, just double check maybe
because we also I think at some
point we eliminate it right start and
everything is determined through the
static purchasable. So that's another one
that we'll just have to confirm me
on. So we have config.
Purchase tables. And
like yours, you're the right start,
Um. But if I
go that's GT, let me just because I'm
looking at series, but they should be
identical.
So my only thing is here, like here is
this. There used to be a 2 step here, two
things that would bring up these practice
tests in series when we did.
But it didn't say no process. But we
don't have that right now. But the other
one was that it was also the list, but
now it has to be in this list. So this
is our practice test list, Jason
currently. And
the right stuff I was talking about.
A little bit here, but you see that
they're all duplicated. So they don't
really do anything fancy with the bundle
except they list it as 1/3.
Option called, you know, it was a fourth
option, whatever. There's different
bundles, you know, and how they OK, OK,
so they and then they put have the
attributes to call in the three different
so it shows up on the three different
exams. So that's how they do it or
they're the OK yeah, so you have
attributes. This purchasable list and
then it however the logic. So this way it
shows it on the test page, but we're not
going to be the test page, but I'll
mention it, but I would imagine it'll be
the same thing whether it's going to show
it on your test page or not, like in this
case, um.
So your you got your old 5 and some
of the repair, but you know, just like
that you bring up your own page. So
you'll kind of want the same thing, but
it'll bring up, you know, you won't have
all this other stuff, but you'll have
technically you'll have this, you know
this part. Here right, right Yep so it's
kind of what I'm thinking it's similar to
what you're doing but ohh, it is it
it's it's completely similar yeah yeah
using it's using the test selector and
the JSON file to bring in whatever
matches Yep so there is an attribute
there yeah yeah and then. Yeah. And then
the tricky part with this one is of
course, putting in the rules around, um,
right, you're different by now. Buttons,
Yeah, yeah, yeah. You service for the API
to determine like what's already in your
cart. Yeah, because this
whole part is built into a table selector
and then the other part is the heavier
right start interactive of course, which
is the other place you can find this is
in the prepare I guess for.
But I don't there's other bundles here.
Uh. Ohh
wait, I'm not I'm sorry, no
one practice test.
Um. The
interesting So we don't do the pitch. I
wonder if that's an oversight. We don't.
Wait a minute, I'm on the wrong one
second practice. No.
Right, right.
Well, there's a bundle. Yeah, it's sorted
differently. OK, this. Yeah, OK. I was
like, wait, we don't do the bundles. It's
just I'm, I'm got thrown off because I
forgot. We do different sorting on this
page for some reason. Yeah.
So basically you have it the logic
somewhat probably in this, you know, and
that's why I think you worked with this
file already, um.
So yeah, this is all given by
the table. Then this part here is
all driven by table selector which is.
I think it's a combination of uh, so you
have test selector is the one and then
the other is driven by.
Um.
It's under shared.
Uh, so actually
page correlation?
No, no.
I forget where it is now. Table dialogues
I see so it's not the side sheet.
I'll select the tables not table selector
so those tables are driven through this
here. Which generates you
get your buttons and everything else that
all that's on this one here. So select
the tables and most of the logic is then
built. Um,
through here. And then
you have this, um, so it
has its own I guess module
for imports and then.
Umm, and I think we, we did a lot
with this because I think the New
Hampshire table, I think some of it was
kind of modified in here. So if it looks
kind of wacky in some cases, it's because
of the new the any of those tables is
driven by this. Also the selected table
where the data is. Brought in and
then there's also of course
your services that calls in.
Um services
here. And
it's going to be a couple different
services with a big, the big E, of
course, is your test service.
That has your purchase tables and things
here that calls them. But I think
Brian, once you have your JSON if
it's structured similar to the right
start. We
might have to there might be just some,
you know, this will have to be modified
to include that the test service to
include the other one because you get
your purchase tables. So a lot of the
logic that's coming from in here.
And then that's that. That should
be about it. Just the.
Think that's it?And
there may be some little things here and
there. And then Matthews worked with the
Jason Loader service. We've used that to
work with the JSON and well, in case you
need it, I don't know.
Anyway, I was just going to point that
out. That's where all your pieces are.
Thank you for thank you for showing us
all of that. Diane. That's yeah, that's
really helpful because yeah, we, I mean,
some of this logic exists, somebody some
of it's been built for other reasons. But
I think this is Matthew. I know you've
seen some of these files, but do you have
sort of an idea in your mind now about
how some of these similar pages on on the
websites?Have been built versus the page
we're going to be building this.
Um, yeah.
And I know that you'll just need to spend
some time. Yeah, I've got,
I've got a, I think I've got a picture
now how those other pages are structured
that helps connect the dots on what can
we, what can be reused and what needs to
be customized for this one.
Yeah, Jason Waters are always special. It
gives me a clear path for where to plug
in the new logic.
Yes, I had. The
test selector selector tables.
And um, test service, I think is where
you going to find the most of it. And
then like you said, Brian, you, you know,
adding the attribute here for no practice
test.
If we needed to find that though, maybe
it's no purchasable practice test. I know
that's kind of long. There's
no difference. There's no difference,
Diane, if there's, um, at least not at
this stage for Georgia. Yeah, if there's
a practice test.
It's going to be for sale. It's going to
be for sale. OK, yeah. Now a candidate
might get it free, but but it's always
also going to be for sale. That's why I'm
wondering like if we could, if we keep
the same logic for series, I'm pretty
sure no practice test. Just
to do with the row and not the actual
buying of the test itself. Let me just
see what that. I
forget sometimes I got to look these up
because I don't remember what they're Ohh
I see what you're what they're used that.
I'm just, I see where the logic and this
comes in because we put it in here, but
I don't, I'm trying to remember where
that logic, um, if it's I'm pretty sure
no practice test means.
Like I think think of.
I'll just click on anyone.
I think for the sake see.
Just test that. We don't.
But on the sea, say you know everybody
will get a practice test, you know when.
We say no. That
does this hide this road. So that's going
to be a little different from gaze. But
what we might do the same thing phase
though already might, right. So it might
serve 2 purposes and then be fine. OK,
Yeah, yeah. I mean, we might let me here
because I'm like, I'm on the gaze prepare
page right now for agriculture, for
example. So we do have a row. The
practice test that says when you register
you get a free practice test. Ohh. And so
and so let me pick one that doesn't have
Let me pick one of those ethics and see
what that's something I'm gonna stop
sharing and let me see what you got. Ohh
you know what? X doesn't have any prep
materials at all. No, they don't. There's
a different so maybe we can use. However,
we set that up for the test page. Maybe
we can just use that attribute?
Yeah. So it's, yeah. So that's basically,
yeah, it's pertaining to having that row
in there when we say no practice tests,
that's what, yeah. So, so I'll take a
peek and see what that is. So we this
might be done for us, right. We might
already have this, some of it. Yeah,
yeah, yeah. I mean, not the whole thing,
of course, but just the indication that
test dot JSON, whether there's a practice
test or not might already.
Let me see if I could
find. So 823 has no on
Netflix? It's somewhat series 823.
2/3.
All right, so I don't, Yeah. So 823
has no practice test row, but if I
go to prepare.
Purchase practice test Purchase the
practice test.
823 and it does not show up on the
list. Yeah, but then again we also have
like I said, it's the list itself is
driven by the purchasable in the JSON
file that we see.
So that's how that was driven.
Yeah, I'll take a peek at how it's set up
currently for for Gays, Diane, and I'll
add that detail to the user story. If it
turns out that I don't need to edit that
file at all, then great. Like if we
already have a value in there that we're
using for gays. Perfect. Yeah, because
let me, I'm sorry, I'm talking without.
Makes it confusing. Um, but you know
what? I what I did just notice was
that um, oops, this thing over there, OK.
Right, so there's here's the the test
page for ethics and and there's no link
to a prepared page because we don't have
they didn't have one. Yeah, right. But if
we go and look at any other, we
do. And like I just clicked on
agriculture. We do have this
link to the prepare page, and on this
page we do say that you get a
practice test. So I'm wondering what it
is about our configuration that does not
include this row, this prepare row for
ethics. OK, and can we use that? I'll
tell you what that is. OK.
And you know, probably or is
it specifically ethics? Yeah, it's
specifically ethics. It's ethics and ASL.
OK, so the two OK, yeah, so gaze is set
up actually a little bit different than
series. And this is one of those series
things that I redid to match gaze, but I
couldn't get the styling of the test slit
at the top to match. So I ditched that
effort because we had to go live and put
it on the back burner.
So the gaze test page is all
JSON where a series is not series
is in the build. So in the
JSON we have the flexibility of including
excluding the rows and that's. So instead
of doing a condition like or you
know on based on an attribute. It's
still based on attribute, but it's it's
excluded differently than it would be. So
it's basically excluding the row itself,
not the tests, practice tests like we did
on the other one. So the other one's not
looking at. I mean, it could be, it could
be we could add that condition. It just
wasn't done that way for for this. Stage
but in particular for the prepared road
to show up that was only based that's
just based on include exclude of ASL or
ethics or ethic you know which to. So
yeah we could actually that's I mean we
could easily change that to be something
else but. So I'm not really
trying to change anything that we did
that is established and working right now
because it's going to be no big deal for
those two or three assessments. If if I
have to add an attribute for, you know,
no practice tests. Practice tests, yeah,
no problem. The lap with
anything that's already out, because
here's the, umm, the config spreadsheet
that I built for, UM. For the developers,
this is what they're updating the
database with. These are all the separate
purchase tables, so here are all the
individual testlets.
You got it all done already. And yeah, I
had to build this for them while because
they were they need this to get the
database and build up, you know, ready
updated and then and then the build the
API and then so it has it has a
type here, whether it's Tesla, it's
assessment or. With
that, there's a, there's a second page
with the bundles like, OK, so if you buy
this purchase code, that means that once
the user checks and pays for it, they
have access to these practice tests and
this bundle code, they have access to
these practice tests. So what the user
will see in their cart is just the
bundle. They'll say, hey, you, you know,
you ordered the practice test bundle for
this field. But of course we don't have,
we don't have a practice test build
called GT 709. What we do is have
practice test builds for all the
individual testlets. So, so they're one
of their back end tasks is to OK, if a
user buys GT 709, we have to give them
access to. These individual Tesla.
That's so, yeah, yeah. Remember when we
were setting up those practice tests,
right. When the user has access to
they're just the individual Tesla, like
the individuals, whatever we built. Yeah.
And so that's being so the back end
team is handling that. But we yeah. So
it's like 189 separate new purchases.
Nice. Um, so it's.
Going to have a Jason file.
Eventually with all the stuff and we'll
we'll build that overtime like over the
next few weeks when I want to get in
place. Short term is just enough so that
Matthew can be working on his part, just
checking out all the making sure the
logic works. Yeah, yeah, yeah. And so.
Yeah. So, so we can start there and you
know, and this will be at, as we've been
saying, this will be added to over time,
right? Like because it could be, you
know, that they're going to have two or
three different practice tests for GTO
one in the future. So, so the test code
will always be GTO one, but the purchase
code will need a new code for each.
Unique practice test that we start
selling.
Um, OK, so.
Flap of meetings this week and more clear
in my mind about how this is all going
to work. So my next I'm going to try
to finish this up today is like we said
Matthew, I'm gonna I'm gonna enter many
more details into the JIRA ticket and
assign it to you and I'm going to update
those. Well, I'm going to
update the test dot JSON file for
Georgia, put in no practice test
attribute where it belongs unless there's
already something in there that accounts
for that. And then I'm going to create
that new practice test JSON file
specifically for Georgia in the Georgia
area with enough data for. Have a handful
of assessments and then turn it all over
to you. I think we should probably, you
know, and Matthew, then I'm thinking I'll
just give you a couple of days to start
work on it and if you need to chat with
us And once you see everything and start
thinking about it, if you need to chat
with us right away to answer a question,
then just let us know and we can meet
again. Otherwise, I'd like to just give
you some. By a time to just really dig in
and focus on it. Yeah, that
sounds good. OK.
OK, this will be um. This
will be good. Yeah, this will be good. So
yeah, Brian, practice tests. Yeah. And
Brian, Dave already put that stuff
through trunk. There was a pull request.
You could just look at the list that was
approved to see what was in there. Ohh.
So the updated services are definitely in
trunk now. Good. OK, well, some of this
stuff like that. Right that he talked
about was in there. Let me see there was
one what might be happening too right
didn't didn't he want us Diane that
although his service is there the back
end isn't there yet in test it's not like
returning any data yet correct Yeah. So
he did say that and then there he also I
have one sitting here for the password
reset and hung kind of. Questioned me
about approving it, but I Ryan didn't
give me the I usually wait until he
requested to be approved. So yeah, um,
even though it's still, you know, it's in
there as being active. I'm waiting for
him because he said don't wait until they
build is done. So I don't know. I don't
know. I'm going to wait and see what I'm
supposed to do with that. OK, I
think I'm supposed to wait but.
I don't know. It's the password reset
because I think if I think if we were to
push that out, it would break things if
the bill's not in there. That makes
sense. I was getting it. That makes. So
if we were to push that out and put it
like in test, then test just would stop
working because the building is not in
test. Yeah, I think so. So that makes
sense. I'm just going to. Event until he
requests from me to update it or someone
else you know if he's not here and
somebody's requesting it then we'll see.
But yeah, I'm going to wait on that
because his he had said let me see
what was the because there was something
about it with Hong had said something.
You know, whenever Hong gets involved and
I'm always like, ohh, no, yeah, but I
know. Well, yeah, I know because, yeah,
she's. She's so on the ball that we want
to keep up with the books she assigned
us. Yeah. Well, and typically what that
means is, right, a developer has signed
off on a story and passed it to her to.
Mikey Way. Yeah.
So she let me see. So this is Angular
forgot password page and I'm sorry, I'm
not there. This is has to do with the
password. Nothing not, not what we're
doing otherwise. So Brian
said this will require content build.
Um, connect your, uh, let CPS know
to approve this on the next build.
Currently, this API change is not in
build due to conflicts at the time.
OK. And then Hong said between you
and I, Brian, could you please make
content change on test?
Ohk OK yeah right and then Brian said
Please wait to push this through until
the next build as it will break once
the next build is out and since I
will be out hung let CPS know.
Time to bring the PR above into the 12
tube build. OK, So I'm definitely going
to wait until we hear the next build is
out because I think that's exactly right.
Yeah, I think that's exactly right. All
right, Thank you, Brian.
We usually don't deal with. So I just
want to make sure that, yeah. And that's
why I was talking rebuild and deployment.
And I haven't seen any.
I haven't seen that they put out a new
build yet. RC
one or something I see
IB. OK, OK.
Yeah, yeah, that's all they've done is
the is Yeah, the initial build. OK. It
was approved but did not complete due to
conflicts. Please wait to retest again.
OK? Ohh OK so ohh. So she she added
whoever the particular QA person was who
was doing this. OK, so now they know not
to test again. OK, so I think,
I think we're, I think we're good with
this one, Diane, until, um, until we're
alerted that there's another build. I
think we're good with this one. OK, I'm
just gonna put myself as a watch on it.
Ohh. You know, I'll watch this one too.
Yeah, stop watching.
OK, OK, so this is what he
was getting. OHK. OK, yeah. So that
was one of them. I don't think
the other. The other stuff is already
put in trunk. So yeah. So I
think whatever we're doing regarding
practice test, I did those pull requests
already. They've been completed.
And those are I'll send. I'll give you
guys a link so you could see.
Um, copy.
So this is what's been put in trunk
that also I don't think anything's going
to work yet until the next build this
out.
Alright. And then so this is this is
Brian's PR for the card service into
trunk. OK, I did not put it into
12 two because then we were saying.
Maybe Matthew, you wanna make a feature
branch for this one and work it as a
feature, but keep it up to date with
trunk. But now, um, but work it as a
feature instead of putting it into 12/2.
I mean, we could probably work it through
trunk, but not, but let's not put it in
12/2 just yet. And then as we get closer
to 12. Do we could always merge it in?
You're probably going to want to keep it
up. You know, if there's, well, I don't
think Brian's not going to be here to add
anything else to it. So, but you'll want
to probably need this part and you
probably need this PR into your features
branch or just make your feature branch
off a trunk for now. Should be fine.
Yeah. And I'll, I'll get my updates. Um,
there's a couple of JSON updates that we
were talking about into trunk like
hopefully today or first thing tomorrow
morning. Yeah.
And that makes the branch afterwards.
Yeah. And then after that, Yeah, yeah,
yeah. See, this is the part, Brian, I,
you know, I would be lost trying to build
this. Yeah, I'm with you. I know,
I know. Yeah. This is fine. Yeah, I
would. I would need a lot of AI. Yeah.
No, this is where. Well, and I did, you
know, I had my meeting with Dan and I did
ask him about, you know, how does all
that training work, all those all those
courses we have access to, you know, when
can why did Janet let the company know?
Like, hey, you guys have X amount of
hours per week to spend on this?Because
we hopefully there's something out there
about, you know, working with services in
Angular and, and, and working with APIs
and Angular and how do you get data from
an API endpoint in Angular and use it
and, and post back to it, et cetera. Like
this stuff that Brian knows how to do.
Like, like, let's, let's see if that's
out there and give people a time. To
learn about it, yeah, yeah. I mean,
I understand the models, but yeah.
Because that's what you Jason, is usually
built off the model.
But then that's the API model, so I don't
know.
Yeah. And I mean, you know, and some of
this is sort of the your typical
JavaScript other other is very much in
the way that Angular does this. And so
it's sort of having all that knowledge.
The async, I don't know if you've ever
written or seen or you know how much
you've used that Diane, like async
functions, because otherwise JavaScript
is just synchronous. So you kind of set
up these promises, which, you know, will
they return a promise like, yeah. So it's
kind of like, yeah, I keep asking AI
explain this again.
To kind of because I need to look back, I
need to go back to the basics almost, you
know well with some of this, yeah, it's
like it's it's tricky because then now
because now what we're looking at right
is code like specifically the way Angular
does things and using TypeScript. And so
if you don't know like the basic like
vanilla JavaScript version of doing this
becomes. Be very hard to decipher for me
anyway. Yeah yeah, yeah, yeah. And I when
I was doing.
I could probably.
Find and put together pieces versus
write it. Myself,
you know that type of thing, you know, I
could kind of pick and choose and seem to
make it work, but to kind of know how
to start it.
Without guideline
um. I
find it more difficult.
Especially with. Especially with the
right calls and.
You know, in the variable name, you know
which variable goes where and when you
sign the. So yeah, there's a, there's
quite a bit. I think there is. Yeah,
there is. Yeah. OK, OK, so this is all
good. I think we've got what we need for
next steps then. And then, yeah, what
I'm, what I'm expecting is over the next
couple of days. And into next week, we're
probably going to have to meet pretty
regularly to kind of, you know, Matthew,
especially as you start digging, digging
in. I'm, I'm guessing that we're gonna
have to meet pretty regularly. You might
get stuck at a certain part. You might
have questions. You might say, hey,
should I take one approach or this other
approach and we'll talk through what the
differences are. Yeah,
did you give us your your picture?
Sorry, go ahead. No,
I was asking Brian for the picture
because I guess we'll need that to build
out the page. Ohh. We, we yeah, we have
it. This is the it's, it's the, it's the
picture that we already use for the
practice tests. Ohh. Good. OK, that's
kind of, I just kind of just say, yeah,
yeah. So it's like, you know what? This
already means practice tests to us, so we
might as well just reuse it. Yeah. Nice.
She's got a good question for us. This
guy's like, ohh, yeah, I'm, I'm all over
that one. He's got my clipboard out and
everything. She's like, well, here's the
big question. So you know, what else do
you need?
OK, All right. I think we got it. I'm
going to dig into these pieces. Um. I'll
let you know if I have any questions,
Diane, just in case I see something in
there in the, UM, that I'm not sure you
know how to proceed with. But I think,
uh, I think the plan we've sketched out
makes sense to me. And then it's just a
function of doing the work and answering
the questions as we go. That we
can, absolutely. I think what's going to
be tough is the fact that, you know, the
the APIs aren't fully working yet. So as
far as like interacting with the cart,
that's not going to be available until
those get into test. So it's going to be,
it's probably going to be difficult for
Matthew to be writing and like confirming
that some of this stuff works as expected
without that working, yeah. Um, so, so
that, that'll be a little bit tricky, but
I mean, we, we, we know what it's
supposed to be because we've got these
services as Brian built. So we know what
we're looking for. We're now we're asking
for, we know what the different, um, you
know, the different values are because
he's got it all sketched out here, as you
know. So yeah, yeah. The purchase code,
the price this is, yeah, this is going to
be, you know, sort of what's in the cart
and the purchasable code is what. It
matters. And so we'll be checking, hey,
is the user clicking on a code that's
already in the cart is sort of, you know,
if the code is already in the cart, show
the button. Um, like if the codes whoops,
yeah, yeah. If the code is already in the
cart, then the button says remove from
part. If it's not, then the button says
add from cart. Like that kind of stuff.
We can build that into the logic even
though it's not working yet. Because we
can see, we can see what these different
values are.
OK, alright, good. Well, all right, I
think we talked enough about this. I'm
gonna get going on my part, see what Beck
has happened in the hour that we've been
talking, because you never know.
All right. Well, thank you both very,
very much. This is going to be a good
feature to get out there. Thanks for
going through that. Yeah, alright. I will
talk to you both soon. Thank you. OK,
thanks. Bye. Bye now. Bye
bye.