0:00:00
did she make herself or she was a
0:00:04
i wait did you make it yourself okay
0:00:11
i'm really hungry and i'm miss
0:00:18
okay um anyway let's get back to it
0:00:21
so for all of those who are new to jira
0:00:25
um so jira is a software where you
0:00:28
work in collaborations um it's mostly
0:00:31
based on a scrum approach of
0:00:33
developing um so if you're wondering
0:00:38
so there are a lot of methodologies
0:00:40
which we deploy when it comes to
0:00:42
software development it's not like in
0:00:45
when you work in company you just don't
0:00:47
think there's a feature and you just do
0:00:50
because some particular features take a
0:00:53
long time and they
0:00:54
require a lot of documentation how
0:00:56
they're done and how they are tested as
0:00:59
things like jira um
0:01:02
like a little too much or a little too
0:01:06
overkill on documenting things but i
0:01:10
when you are developing a project um
0:01:12
it's really important even if it's a
0:01:14
personal project or even if you're
0:01:15
working in a company
0:01:16
yeah going through this scrum process of
0:01:21
makes it right so right right right i
0:01:25
yeah um let's see what we have here so
0:01:28
when you log into here as you you know
0:01:30
you get a website name which
0:01:32
is a thought atlas um
0:01:35
so you have a jira account in that
0:01:39
you can have multiple projects and
0:01:43
like for example i have my jira and i
0:01:47
the project which we are working on
0:01:49
right now which is angular v2
0:01:51
uh that's not our final name for our
0:01:55
we gave right now but we'll agree on uh
0:02:02
there and as you can see i added a in
0:02:06
so just to uh interrupt you
0:02:10
a bit okay um can you possibly show
0:02:13
me and the viewers how to actually
0:02:16
create a book as a board
0:02:23
because you go on projects
0:02:26
and we go on create project all right
0:02:30
right okay so when it comes to creating
0:02:34
there's a lot of different methodologies
0:02:38
so generally kanban is a methodology
0:02:42
for long-term projects like let's say
0:02:45
your project is a six month long project
0:02:48
um it's gonna keep falling and it it's
0:02:51
not gonna be really dynamic like
0:02:53
there will be a pattern so that's where
0:02:55
you kind of deploy
0:02:56
kanban um scrum when you
0:03:00
um do a sprint so for people who don't
0:03:03
with this is when you sit down for
0:03:07
uh like it's kind of like a hackathon
0:03:10
you can say but like
0:03:12
like really get work done and you just
0:03:14
there's a very dynamic environment
0:03:16
um so that's when you scrum board
0:03:20
um bug tracking is as sound it is
0:03:23
um you just kind of list all your bugs
0:03:27
that comes down when you you use this
0:03:38
but as we know it's gonna take a lot of
0:03:43
it only makes sense that the kanban
0:03:46
cool that makes cool um so as it says um
0:03:51
and that is a word for visual signals
0:03:54
this is kind of what you might have in
0:03:57
kanban though you can edit your taskbar
0:04:01
you can create a workflow as well we'll
0:04:03
see how to do that as well
0:04:05
and yeah and then you obviously
0:04:08
um deploy this agile methodology
0:04:13
right right right so
0:04:16
it's really important with a good
0:04:19
as it sounds complementary types are for
0:04:23
kind of like expert configuration
0:04:26
um there's a lot of higher than a
0:04:31
one um is um for smaller teams
0:04:35
inside a company you work at amazon but
0:04:38
you work um software development
0:04:43
or this exact particular feature in
0:04:47
then you'd be looking at something like
0:04:51
configuration so as a small team and
0:04:56
um our hierarchical um configurations of
0:05:01
we manage project um let's name gothic
0:05:06
would you possibly have any external
0:05:08
microphone because your
0:05:10
voice is as in being pressed and then
0:05:14
released being pressed and then released
0:05:18
yeah one second i can put on earphones
0:05:22
okay yeah we can try that as well
0:05:34
i think we might have to edit this video
0:05:40
i spoke about a completely different
0:05:43
we will be doing at the start so
0:05:46
this is just as in
0:06:11
okay um do you want me to go back and
0:06:15
was it audible enough i think
0:06:19
just go back and do a really
0:06:22
fast track one okay yeah let's do that
0:06:31
all right um so yeah as we
0:06:34
just talked about that we're gonna have
0:06:36
an account and you're gonna have a lot
0:06:38
associated with your account um
0:06:42
so it's really important to choose the
0:06:45
um template for your board kanban is
0:06:49
long-term development scrum is for when
0:06:52
you want to sprint
0:06:53
um in the sense that um
0:06:57
when all the developers really get down
0:06:59
to and get work done
0:07:01
in a short period of time
0:07:04
bug tracking is beta testing or alpha
0:07:09
test for um your bugs kind of developed
0:07:13
so for us we have a long-term project so
0:07:16
kanban is the only one which makes sense
0:07:21
all right so let's use this template um
0:07:24
we talked about company management team
0:07:28
company managers are employed when there
0:07:31
huge hierarchical need um on a
0:07:34
company level which means that there's
0:07:37
going to be a lot of
0:07:40
hierarchy in which people are managed he
0:07:42
manages for smaller teams
0:07:44
maybe inside a company or individual
0:07:47
um so it only makes sense that if you're
0:07:50
doing a personal project
0:07:51
you might want to just go for a team
0:07:56
all right so let's name this board
0:08:00
um you can edit your key demo looks fine
0:08:04
yeah yeah that's fine let's go
0:08:08
create the board right
0:08:24
even if you want to create an issue
0:08:26
right now you won't have a lot of
0:08:28
issue types or tasks which is fine
0:08:31
so once you are you have decided that
0:08:34
you will work in a
0:08:35
dial or scrum method um it's really
0:08:38
important that you go ahead and add
0:08:40
a column which is called in testing
0:08:44
um what this means is that
0:08:47
you want to take a feature or you want
0:08:53
make it in progress and then test it as
0:08:56
you're going through the project
0:08:58
rather than what was the um trivial way
0:09:02
dev sit down and um make the project up
0:09:06
and then at the end they start testing
0:09:10
this turns out to be a problem because
0:09:14
um it only makes sense to test
0:09:17
smaller or unique pieces of
0:09:20
your software then doing it in one go
0:09:23
and spending a lot of time
0:09:29
we go on issue types and we go and
0:09:31
manage issue types
0:09:33
um you can see that there is a task
0:09:38
but there's going to be a lot more when
0:09:41
you start developing stuff
0:09:43
um maybe you're working on a
0:09:47
task maybe you're working on a bug maybe
0:09:50
on something personal which you need to
0:09:52
learn so it's important that you
0:09:53
add issue types so uh
0:09:56
as you know we are developing a software
0:09:58
so there's gonna be problems
0:10:00
and um it's only important that we have
0:10:05
so let's add that if you type
0:10:08
um then would you mind using your mic i
0:10:12
i think it's too close to your um
0:10:16
yeah cool um sorry sorry about that
0:10:19
thanks for that jen
0:10:20
um cool so a story is a functionality or
0:10:25
feature you can say
0:10:26
or you can kind of name it as a to-do
0:10:29
thingy for you like
0:10:30
um let's say you're developing a
0:10:32
software but there's
0:10:34
something which you don't know for me
0:10:36
for me for example
0:10:37
i'm working on a project and i don't
0:10:38
know what circle ci is
0:10:40
so in my jira board it is um registered
0:10:44
so let's add that and you can go ahead
0:10:47
and change the name of it
0:10:48
um let's say it is a to
0:10:52
learn um um thing in my
0:10:56
uh that's that's what i want to do like
0:11:00
um something which i want to learn so
0:11:03
instead of task we can have a feature
0:11:08
um work for us and
0:11:11
when it comes down to these things
0:11:12
there's a lot of things which you
0:11:14
need to consider that um so what
0:11:18
um okay we'll come back
0:11:21
we'll come to that later on um and we
0:11:25
have subtasks of course
0:11:26
sub stars are let's say um my main task
0:11:31
connecting dynamodb to api but there are
0:11:35
like um connecting this controller to
0:11:39
maybe solving a airways which we are
0:11:43
so tasks are basically just a
0:11:45
hierarchical day that
0:11:47
is this major task but it involves a
0:11:50
lot of smaller tasks which need to be
0:11:54
cool so i think for our project as of
0:11:57
feature bug and to learn um is something
0:12:01
which we can um have a good start with
0:12:04
um of course we can come back and add a
0:12:07
so if we go back to the demo board
0:12:11
and let's say i click an issue
0:12:14
which is connecting um
0:12:18
or actually communicating
0:12:25
rear back end all right so
0:12:29
as we know um this is a
0:12:33
um second so it's unassigned
0:12:48
it's gonna change that it's a feature
0:12:58
oh yeah that's how i do it um i forgot
0:13:00
to add the feature tab
0:13:02
just one second i'll go ahead and do it
0:13:08
all right so here we should
0:13:11
have and of course um that's
0:13:15
kind of a functionality so it will be a
0:13:18
and we'll call it oh wait we go oh okay
0:13:22
i know what's happening i think we
0:13:25
already have the feature type there
0:13:28
yeah um so that is
0:13:35
not a story that is a task type
0:13:39
um so it is like everything is a task
0:13:44
um but we do need a story
0:13:48
so what's the difference between a task
0:13:51
and a feature then
0:13:54
um everything in jira is a task like a
0:13:57
um what you have to go ahead and learn
0:14:00
is this task but um
0:14:02
feature is just like okay this is a
0:14:05
feature which i need to add in my front
0:14:08
let's say that you have to add this
0:14:11
button in your front name that's a
0:14:13
um and that's the task as well as well
0:14:17
so you're saying that the task and
0:14:21
feature are basically the same thing
0:14:24
um even above the task like even the bug
0:14:29
so i'm just a bit confused
0:14:32
um why have task as a different
0:14:36
issue type and a bug as a different one
0:14:40
if bug is also a task so
0:14:44
um let's say this is task and
0:14:47
bug feature and to learn comes all under
0:14:54
so that's why they have a different
0:14:57
but the task is the above in the
0:15:00
hierarchy in the sense that
0:15:01
task is the superset of all the um
0:15:04
feature types which you're gonna have
0:15:08
okay cool understood cool so if we go
0:15:16
i'll just go ahead and delete this for
0:15:18
now and we'll create it again
0:15:20
so if we go here and as you can see this
0:15:23
is a feature and let's say
0:15:25
making our front end
0:15:28
communicate to back end
0:15:36
so as you can see that i'm the reporter
0:15:40
this is what this means is that i
0:15:43
and this is really important um because
0:15:47
when this ticket moves in a lot of
0:15:50
and it moves back when it feels testing
0:15:53
it comes in progress again
0:15:54
it's really important to make sure that
0:15:58
in the sense of who wrote it so this
0:16:01
thing comes down becomes really
0:16:03
important when the ticket moves around a
0:16:06
um so let's see assign so you you're
0:16:09
gonna have a lot of developers working
0:16:11
in a team or maybe a lot of testers or
0:16:13
um even for that matter product owners
0:16:18
so here works in the sense that this is
0:16:24
if you assign this to me that that means
0:16:28
um i have to go ahead and read this and
0:16:30
this is probably something which i
0:16:32
should be looking at
0:16:33
um this sounds very trivial but
0:16:36
i have i've worked in a jira environment
0:16:39
um a lot of people tend to miss this
0:16:43
a lot of people tend to kind of forget
0:16:44
and i've done it as well i've done it a
0:16:47
i just do my task and maybe it is for
0:16:52
when it's in progress the software
0:16:54
developers are working on it
0:16:56
and when it's in testing maybe the
0:16:59
testers are working on it
0:17:00
and there's actually there's actually
0:17:03
should be one more column that
0:17:09
for release which means that
0:17:13
this feature has been tested and it has
0:17:17
but um when it when things pass testing
0:17:20
that doesn't mean that they're
0:17:22
deployed on production just that second
0:17:25
um so what happens when you're
0:17:27
developing stuff you might wanna
0:17:30
cluster a lot of features together and
0:17:32
positive production at once
0:17:34
not because see when you deploy
0:17:36
something to production
0:17:38
there's things like code build or code
0:17:41
things take place and it really it's
0:17:44
really a pain to do it for every single
0:17:46
you keep a lot of tickets together and
0:17:48
ready for release which is which means
0:17:51
they have been put to staging um
0:17:53
environment but they are not really
0:17:55
in production that means your end user
0:17:57
can't really see it for now
0:17:59
and when they are when they're being
0:18:00
released and maybe
0:18:03
releasing it is a job for a developer
0:18:05
not for a tester so
0:18:07
that's where the assignee column comes
0:18:09
maybe um zen is a developer and i was a
0:18:11
tester so i'll assign it to zen and
0:18:14
when then um is ready to push it to
0:18:17
production and he has done it
0:18:19
he just goes and put it to done and he
0:18:22
important point part is to unassign it
0:18:26
so this was a life cycle of a feature
0:18:31
just being reported to being in progress
0:18:34
developed tested and staging
0:18:39
and i think we should have one
0:18:42
more column saying uh
0:18:45
e in review as in or
0:18:53
let's do peer review
0:19:00
so yeah jen made a really good point
0:19:04
so before um stuff
0:19:07
is gone for testing or maybe after even
0:19:10
it's tested it really depends on how you
0:19:13
um a lot of people prefer that um
0:19:16
so obviously when you're working in
0:19:17
teams um there are juniors and there are
0:19:21
as a junior dev you are gonna do a job
0:19:24
it's not that um your senior dads don't
0:19:27
trust you or something like that but
0:19:29
it's really important for the um
0:19:31
company's point of view that
0:19:33
and even the code which seen a devs
0:19:35
right there it is being reviewed by
0:19:38
other senior devs who uh because
0:19:41
every feature kind of relates to other
0:19:43
features which other
0:19:44
developers may be working on so it only
0:19:47
makes sense that other developers look
0:19:49
so that um when you are doing uh
0:19:52
integration testing
0:19:53
that means to see how well your code
0:19:56
integrates with each other
0:19:58
um this column peer review
0:20:01
really comes handy because um
0:20:04
your developers have to make sure that
0:20:06
you are using the light libraries or
0:20:08
putting in the right method um so that
0:20:11
it does cause integration testing
0:20:14
so and oh so just one
0:20:18
one more thing that we wanted to
0:20:20
highlight about the
0:20:21
peer review stage is that i think
0:20:25
one of the reasons as well why
0:20:29
which um we especially
0:20:32
junior devs have to make sure that we
0:20:36
reviewed by someone senior or even
0:20:40
or even middle level deaf
0:20:43
is because they have already worked
0:20:47
in the company longer than us so then
0:20:51
now the as an overall systems
0:20:54
picture and all all the other moving
0:20:58
components it's not that uh no one
0:21:01
in the company trusts you but um if
0:21:04
say for example i got
0:21:08
requeued in a company say a month ago
0:21:11
i was given a functionality and i
0:21:14
did it i would only focus
0:21:18
fire common sense on that functionality
0:21:22
but if you get the curve review
0:21:25
uh first for you you will get
0:21:29
you will get to know about the best
0:21:32
from uh someone else's
0:21:36
practical experience and second of all
0:21:40
they can actually make sure that the
0:21:44
friend it doesn't from their
0:21:47
level of understanding of the whole
0:21:50
system it doesn't break
0:21:52
some other functionality
0:21:55
that's already working so yeah
0:21:59
that's also is a good way to um
0:22:02
do as in a good reason to do
0:22:06
peer review as well
0:22:12
cool yeah that was a really good point
0:22:15
that's really true like um when you're
0:22:17
working in a company let's say
0:22:19
i mean it's only it only is good that
0:22:22
you get a review or
0:22:23
get a feedback for what you did so yeah
0:22:28
so yeah this is probably on
0:22:31
life cycle how a feature goes through
0:22:34
an agile or let's say a scrum um
0:22:38
methodology um let's look at other
0:22:41
features which jira has to offer of
0:22:44
so um you can go ahead and make a team
0:22:46
as well in the sense that
0:22:48
i'm maybe trying to interrupt your
0:22:52
i think um i almost forgot one
0:22:56
of the step and uh and that was to do
0:23:03
assurance which is the qa so
0:23:07
they just basically ensure that the
0:23:11
code i mean not the code itself
0:23:15
from my understanding and i might be
0:23:18
um they just make sure that this
0:23:23
software overall with those function
0:23:27
functionality is is
0:23:31
performing to a certain standard
0:23:35
yeah that's true um
0:23:38
so when i was working where i used to
0:23:41
when i joined i was given a document
0:23:43
called coding standards
0:23:45
which meant that exactly how
0:23:48
the companies to code um like just the
0:23:51
name of the functions like how
0:23:53
you have to name those functions or how
0:23:57
kind of design a particular code because
0:24:00
same code can be written in like at
0:24:02
least 20 ways i don't exaggerate say
0:24:06
a hello world code can be returned into
0:24:10
writing long complex code um and still
0:24:13
maintaining a consistency so companies
0:24:16
tend to issue a coding standard document
0:24:19
peer review is where um it comes down
0:24:22
that thing is said that the company's
0:24:26
methodologies have been used or not so
0:24:30
yeah that was a good talk um cool
0:24:33
um should we go ahead and look at other
0:24:40
wait can you anything
0:24:44
yes uh i just muted my
0:24:47
cell because you were talking that's why
0:24:49
yeah so you just yeah
0:24:52
good to go and well done on the really
0:24:56
uh explanation as well cool
0:24:59
um so when you are working in a team um
0:25:03
let's say this is a board and let's say
0:25:06
this is a company borah this is your
0:25:09
all the front end and back end and
0:25:13
project management or product indoor
0:25:15
owner issues would be
0:25:17
here in this column and it's
0:25:20
good to make sure that these people who
0:25:24
have a different um let's say like a
0:25:27
different purpose in their team
0:25:29
are in in a company or in the project
0:25:32
are separated in teams so that they can
0:25:36
they need to do so jira does really a
0:25:40
if you go to people and if you go to
0:25:44
and let's say i am in the back end team
0:25:55
right and let's say i want to invite zen
0:25:58
bracken team because um he and we are
0:26:01
working on the backing team
0:26:05
so now that even if our project has a
0:26:09
lot of types of people like front end
0:26:10
devs or back enders or testers
0:26:13
um it's clear that zen and me are in the
0:26:18
you can um assign um stuff to teams as
0:26:22
well and then they can sort it out so
0:26:24
if we go out and filter the back-end
0:26:28
issues then we would be able to do that
0:26:31
zero does a really good job in um team
0:26:34
management as well and that's probably
0:26:37
um what's the reason why it's employed
0:26:39
in a lot of companies
0:26:41
so let's see and let's go ahead and see
0:26:44
what our workflows
0:26:57
um just one second
0:27:02
i forget how oh yeah man it's all right
0:27:06
um so this was on the workflow which we
0:27:10
right now um so of course everyone has a
0:27:14
different workflow so
0:27:16
um jira has um a kind of
0:27:20
place where you can have a template like
0:27:23
you can have like five different
0:27:25
workflows you can make them and
0:27:27
and keep deploying on different kind of
0:27:30
your projects or different boards
0:27:32
so yeah that's probably a workflow and
0:27:34
you can go ahead and change stuff in
0:27:36
these workflows and add or
0:27:38
you can have transitions in these
0:27:39
workflows and as well
0:27:41
or you can have rules in them so i don't
0:27:43
want to go into that because
0:27:45
um that's really specific stuff and if
0:27:47
you're working on a personal project and
0:27:49
even if you're working on a company um
0:27:51
you're probably not gonna do that that's
0:27:55
uh hire companies but all right
0:27:59
um one other thing which is really cool
0:28:03
is that jira apps so jira has a
0:28:06
big marketplace um i'll go into that
0:28:10
one of the things i really like about
0:28:13
um jira slack integration so
0:28:16
let's go to that um
0:28:25
a lot of people tend to use slack for
0:28:28
their um company-wide communication
0:28:31
and that's probably the best software um
0:28:34
i know there are a lot of other
0:28:35
software's out there but
0:28:37
i feel like sled does the best job when
0:28:40
it comes to these things
0:28:41
so what jira has done is that um
0:28:46
it it's it's really important that you
0:28:50
posted on what issues um
0:28:53
you keep getting because if you're
0:28:54
working full-time on a project or even
0:28:56
if you're working full-time in a company
0:28:58
this board is really dynamic though it
0:29:00
looks really empty right now but
0:29:02
they're like 15 or 20 tickets which move
0:29:04
around this board every day
0:29:06
and you want to make sure that you are
0:29:09
kept up to date with these tickets
0:29:10
um as as soon as they are moved and or
0:29:14
as soon as they're assigned to you
0:29:16
so um just like integration is
0:29:19
um just a basic way of getting a message
0:29:23
from jira it's just a basic api um
0:29:26
we'll go and talk about jira api and how
0:29:28
you can use it yourself as well
0:29:30
um i know one of my friend what he did
0:29:33
was use sierra api
0:29:34
and he used to get a message on whatsapp
0:29:37
uh because he was active on whatsapp
0:29:40
you used to get a message on whatsapp as
0:29:42
a ticket it was mode or something like
0:29:45
um jira is really developer friendly as
0:29:48
well so we'll go into that as well
0:29:50
so as you can see um um let's say
0:29:54
this is this theme and you can control
0:29:57
your tasks here as well
0:29:59
um and it sounds really trivial right
0:30:02
now but when you are
0:30:03
working constantly on slack and like
0:30:05
there's like a lot of stuff happening
0:30:07
that's live people
0:30:08
are talking and this has been happening
0:30:10
it's really it's really it's really
0:30:12
um just only that jira can mention your
0:30:16
so that's basically zero slack
0:30:18
integration um and you can find it on
0:30:21
um atlassian's marketplace apparently i
0:30:24
so i can't go ahead and install it again
0:30:30
i can show you where you can get
0:30:34
um yeah i already have it so um you just
0:30:37
get it on the same marketplace but
0:30:40
yeah um let's go ahead and talk about
0:30:50
sounds good all right
0:30:53
um so jira has um two kind of apis
0:30:58
uh which it wants you to do once you do
0:31:03
you guys i think build on java if i'm
0:31:09
let's see what it's tech status
0:31:17
i'm not sure what it is but our
0:31:21
told us yep sodium is built on java so
0:31:24
it only makes sense that um
0:31:28
they they want you to encourage to use
0:31:32
and i can see why they want to do it
0:31:36
more stuff that you can do with the java
0:31:40
rest apis but it's fine um i know a lot
0:31:44
comfortable using rest apis and you can
0:31:47
and as much as required with the rest
0:31:51
so when you sign up you can go ahead and
0:31:55
get a token for your particular board
0:31:59
and there's a really good documentation
0:32:02
don't think it's this one there's like a
0:32:05
proper documentation
0:32:06
oh yeah yeah so you can use um json
0:32:15
a thing like this i don't think i can
0:32:19
is there any online images
0:32:35
i think we we might keep it to
0:32:42
rather than going into a bit more of an
0:32:45
advanced version and
0:32:48
for the advanced version we can always
0:32:52
video cool afterwards
0:32:56
that was all about best apis um if you
0:32:58
guys want to know more um just hit us up
0:33:00
we'll try to help you out anyway getting
0:33:03
back to the board um
0:33:05
so next thing which i want to talk about
0:33:06
is um the atlassian marketplace um
0:33:11
this is a really good um is because
0:33:14
it is open for anyone who wants to
0:33:17
um atlassian itself um really
0:33:21
tries to keep a lot of stuff coming in
0:33:30
so um i'll give you an example let's say
0:33:39
companies it's like a normal company and
0:33:42
versions of your app and let's say you
0:33:46
you wanna deploy something to document
0:33:49
um that's a good example let's say so
0:33:52
you can just go to test management and
0:33:55
um i use this tool before so let's
0:33:58
say i wanna use the fire and i'll go and
0:34:03
just say try for free
0:34:06
oh yeah i'll just log in
0:34:11
all right yep just make sure you don't
0:34:14
forget to cancel it afterwards
0:34:16
otherwise they might charge you anything
0:34:24
after 30 days yeah we'll go ahead and
0:34:28
so yeah so what it'll do is it'll go
0:34:32
refresh this board should have been
0:34:36
just take two minutes um
0:34:40
all right there we go so um
0:34:43
we have these additional features as
0:34:45
well so i'm just giving you an example
0:34:47
that um let's say you
0:34:49
are developing a project and you know
0:34:52
document your testing
0:34:53
um people do that for different reasons
0:34:56
just to have a track of how you tested
0:35:00
because when you want to actually
0:35:01
release it to the market and you want to
0:35:04
patents or i don't know like other stuff
0:35:06
you want to prove that it's work right
0:35:08
these documentations really comes handy
0:35:12
so let's go to the fire squad
0:35:16
i mean i'm just giving you an example of
0:35:19
kind of favoring this software um
0:35:22
a million um other um
0:35:26
issues are like uh software which are on
0:35:29
atlassian marketplace
0:35:31
let's just miss this right now this
0:35:35
we're fine okay yeah
0:35:43
you didn't want um
0:35:54
yep so um this is an example of how
0:35:58
let's say the first code has a project
0:36:01
automation functionality
0:36:02
um so these things could be deployed to
0:36:05
your tickets can interact with each
0:36:09
these marketplace apps have the
0:36:11
capabilities to move your tickets
0:36:13
or go ahead and just have a
0:36:16
little bit of control to help you
0:36:18
automate a lot of your
0:36:23
so i think that's enough uh for us to
0:36:26
talk about jira as of now
0:36:27
um you you guys can go ahead and explore
0:36:31
um it's really helpful um and yeah this
0:36:35
is probably what we use
0:36:36
as um in our project right now
0:36:40
um to make it successful
0:36:43
so yeah then you want to take it from
0:36:51
cool gothic that was a brilliant
0:36:54
explanation thanks for that
0:36:57
i learned a lot just by listening to you
0:37:01
which was pretty much handy um so what
0:37:04
we are now going to do is just
0:37:06
create an issue that we're going to be
0:37:10
working on so if you want to
0:37:13
go and do that you
0:37:17
um i'll go ahead and delete this board
0:37:19
though on the demo board
0:37:23
um so one more thing uh in case you
0:37:26
deleted your board by mistake
0:37:28
jira keeps your data for 60 days uh
0:37:31
exactly after 50 days your data has
0:37:33
permanently moved to trash so there's no
0:37:36
way in the world you can recover it
0:37:40
and i will go ahead and uninstall the
0:37:42
first squad as well
0:38:24
that's one go ahead and continue the
0:38:25
trial as well if you want
0:38:32
it's going to be all projects and this
0:38:34
is the current project um
0:38:36
which we are building right now and you
0:38:38
guys are following
0:38:40
um probably you want to create the first
0:38:44
task and then i'll learn the basics of
0:38:49
fair shape here because i don't know
0:38:50
that at the moment so i'm going to
0:38:53
learn by doing it yep
0:38:57
so let's say our first task is learn
0:39:00
search api is that right
0:39:02
yeah learn fetch appear basics
0:39:09
oh okay um we didn't create the issue
0:39:20
are you hearing me too loudly yeah
0:39:51
that'll all right so
0:40:04
all right um it's a two learn feature
0:40:08
oh i'm sorry right
0:40:12
so um let's say this is assigned to
0:40:16
sam um one thing which i
0:40:20
i'm not sure about can i find all
0:40:24
multiple people i'm just looking into
0:40:28
that signings i don't
0:40:31
think you can i don't think
0:40:35
you can either can you sign the task to
0:40:40
multiple people jira
0:40:46
you cannot no you can't i thought
0:41:06
but you i think you can assign it to
0:41:10
but we're not gonna go into that um
0:41:14
yeah yeah okay cool and then the second
0:41:18
we would have to do is um
0:41:32
make the backhand talk to um make the
0:41:38
okay yeah so that thing is going to have
0:41:43
yeah yeah of course of course
0:41:52
and we can actually break into
0:41:55
sub tasks yep so we'll go ahead and
0:42:14
uh in the subtitles we need to
0:42:22
post the board name
0:42:26
from the front end to the back
0:42:38
content to the backend post the board
0:42:42
all right okay start
0:42:47
from the front end to the back end
0:43:02
um all right so if we go here and do add
0:43:08
choose an existing yeah that's
0:43:12
i think you should
0:43:18
yeah you need to type if i'm not wrong
0:43:25
okay that's interesting
0:43:38
i think we need to consider some more
0:43:39
things but for now let's do this
0:43:55
i'll go ahead and delete this one
0:44:01
okay that's fine uh i had an
0:44:04
other idea but don't
0:44:07
don't worry about it now okay
0:44:10
because i'm not even sure that it would
0:44:17
uh i was just gonna say that maybe we
0:44:22
go to the child task and then
0:44:26
link a parent task to that one
0:44:30
if that makes sense
0:44:34
so you can send link issue
0:44:38
oh i didn't see that oh yeah you're
0:44:46
so we could have done it for in the
0:44:48
sense that let's say we have an
0:44:56
go to the drop down no no no uh
0:45:04
which one this one oh yeah that one
0:45:07
no no i'm wrong it's not supposed to be
0:45:17
okay yeah relates to probably
0:45:21
yeah but relates to is um something like
0:45:28
this issue is not working and it relates
0:45:31
to that issue it's not a sub task if
0:45:33
that makes sense lately
0:45:36
but it can be caused because that thing
0:45:40
yeah right right right okay so yeah that
0:45:43
wouldn't be applied in that thing what
0:45:47
what you did back there was
0:45:50
probably the right thing to do
0:45:54
so let's add more time tasks to
0:45:57
uh post board name at the moment i can
0:46:01
uh i want to do step by step
0:46:04
so let's just do the board first
0:46:08
and then we can go ahead and document it
0:46:10
and we can keep working on it
0:46:13
okay cool um so post
0:46:17
board is done post
0:46:27
yeah yeah yeah we can do that one as
0:46:31
personal from the front and to the back
0:46:35
what else do we have um
0:46:39
we need to get a particular board
0:46:42
is that all the post controls we have
0:46:50
okay so let's type a get one
0:46:54
i think we should do get first but um
0:47:01
we can only do get
0:47:05
first uh we can only to get after
0:47:17
from the back end to the front end
0:47:25
and the one above that as well
0:47:29
get a board from the front end
0:47:33
of from the back end to the front end
0:47:37
well you'd uh is hey
0:47:40
you sound too welcome what are you doing
0:47:44
um so we did a kind of a beginners
0:47:48
um walkthrough of using
0:47:52
jira and we're actually using
0:47:59
uh tool so as in managing
0:48:02
all the tickets creating the phone
0:48:06
features as in essentially to be track
0:48:12
jira now as you can already tell
0:48:15
and currently we are just um working on
0:48:19
big task which is making
0:48:23
the front end talk to the back end
0:48:26
and we are breaking that
0:48:30
feature into subtasks
0:48:39
get a specific board from the brand um
0:48:43
we want we won't be able to get all
0:48:46
boards from the back end
0:48:50
all right that's not the scope of
0:48:58
oh yeah that's true that makes sense but
0:49:00
we do need all notes
0:49:02
yeah yeah yeah and i'll name it a
0:49:10
and i'll delete this one
0:49:20
all right um and what else do we have
0:49:24
let's see get a specific note um
0:49:42
all right and let's delete functions
0:49:48
just a little bit uh yeah but
0:49:51
i think we can implement that
0:49:55
um as if from the front end
0:49:58
but that would only be allowed by the
0:50:04
of the board right yeah yeah
0:50:07
so um so this issue is going to relate
0:50:11
to uh um hierarchy
0:50:14
um like all the types of user which
0:50:17
we're gonna create so we'll make this
0:50:20
correct i can't delete that one
0:50:26
all right delete a note from
0:50:30
the united update yeah
0:50:47
um okay let's create another issue
0:50:58
just thinking about the wording of this
0:51:02
are these really issues or these are
0:51:12
um are these really issues shouldn't we
0:51:16
change the heading of
0:51:19
to do two issues as in issues
0:51:27
yep um so i remember what meaning it was
0:51:36
um i think that is
0:51:40
pbis no no no backlog
0:51:44
would be the right one yeah yeah backlog
0:51:51
implement user hierarchy and let's
0:51:55
delete choose to that
0:52:05
uh can you scroll down or you
0:52:08
you won't let okay 14 so
0:52:19
that's interesting ah here we go
0:52:22
and the other one as well this one is
0:52:35
all right brilliant
0:52:47
user levels like users i guess
0:52:54
like we user types actually
0:53:02
um this feature will really do you agree
0:53:05
with this feature like with you between
0:53:11
i just created this issue um sorry
0:53:18
this is a feature um implement user
0:53:24
and this relates to implement user
0:53:27
um i don't think we have any more
0:53:40
i'll go ahead and create
0:53:56
you can add links as well that's cool
0:54:22
is the skin what is a pbi
0:54:29
pbi basically stands for product
0:54:32
backlog item and basically it's a
0:54:39
would be an item but product backlog is
0:54:43
list of is a list of
0:54:47
new features which can consist of
0:54:51
any new features you want to
0:54:55
implement in order to
0:54:58
get to a specific outcome
0:55:02
it can also include changes to existing
0:55:07
um bug fixes in infrastructure
0:55:10
change you name it yeah
0:55:14
and pbi say product backlog item is
0:55:18
just say one feature that
0:55:22
would be a part of that list which
0:55:26
will be as an item if that makes sense
0:55:31
yep that was pretty um
0:55:34
a good explanation of pbi yeah
0:55:38
thank you i made another field
0:55:51
um what are we trying to do at the
0:55:55
arms just one second um
0:56:41
uh implement users types
0:56:49
i think at the moment we should
0:56:52
leave it at this why do i
0:56:56
so why do i say that because
0:57:00
when we go in each any s
0:57:03
any step we will experience
0:57:06
bugs and fixes that we would have
0:57:10
to do so we can just come back and keep
0:57:14
logging those bugs and things
0:57:17
simultaneously as well
0:57:23
cool oh yeah 15 um
0:57:26
tasks to work on not features wow pretty
0:57:31
so this gonna be a fun ride i would say
0:57:35
yeah yeah cool so shall we
0:57:39
um do you want to cover
0:57:42
anything else about the jira or
0:57:45
shall we move on um
0:57:49
yeah not really we probably pretty much
0:57:51
covered everything um yeah
0:57:53
like one hurricane why not talking
0:58:00
wants to know anything um just hit us up
0:58:03
any of the social media which is
0:58:06
cool um let's move forward then
0:58:10
perfect so um i'll just share my screen
0:58:19
so if you want to just
0:58:22
update the ticket off learn
0:58:26
learning don't fetch
0:58:29
api and that one and
0:58:32
actually i'll just do it really quickly
0:58:36
have you got fast access to that
0:58:40
i did okay cool perfect
0:58:43
so i don't need to do that all right so
0:58:48
i'll tell you why we wanna
0:58:52
learn fetch api because this will act as
0:58:56
middleware as in it would
0:59:01
we have to use it to make sync
0:59:09
which means that basically
0:59:12
whenever we guess as in a board name or
0:59:15
no or anything we want to
0:59:19
be able to send the requests to the
0:59:23
to the back end and fetch apl will act
0:59:27
middleman so say for example
0:59:31
this is our front end but
0:59:36
this is our backhand and
0:59:40
the fetch api will come in the in the
0:59:43
middle so front-end will give
0:59:47
fetch api that information and then the
0:59:51
will actually pass you on to the back
0:59:54
backhand will actually communicate with
0:59:59
dynamodb oh okay that makes sense
1:00:07
that was my understanding of fetch
1:00:10
api um feel free to correct me if
1:00:17
if i missed out something at all
1:00:20
i haven't uh really progressed this api
1:00:27
i um stuff it was mostly using like ad
1:00:31
it was just a synchronous environment
1:00:34
ah okay cool right right i mean uh
1:00:38
this is my first time also dealing with
1:00:41
api and i've just shared my you can say
1:00:45
brand new knowledge with you
1:00:55
um can you share this link with me which
1:00:58
cool i'll just share it in
1:01:10
okay so the reason
1:01:13
why we wanna as in i can't i've already
1:01:17
told the reason why we wanna use fetch
1:01:20
api um on what we are going to be using
1:01:25
api i'll just go a bit backwards
1:01:28
to tell you so okay
1:01:32
so save this is the home page of the
1:01:36
existing scrambler
1:01:39
or obviously the ui has to
1:01:42
change a bit but that's not the concern
1:01:47
the concern is to just work on the
1:01:51
functionality so say
1:01:54
you know how this home dog html
1:01:58
is there and if you do
1:02:02
if you do test and
1:02:10
test is actually appended to the url
1:02:16
in order for this test to go
1:02:20
to the back end into our sam
1:02:24
api we need to be able to pass it
1:02:28
api and then to there which is
1:02:31
our next task after
1:02:35
this fetch appeal learning so
1:02:39
we'll just go together with this
1:02:42
how you can make a synchronous http
1:02:45
okay so it's it deals with
1:02:50
a single request the facebook
1:02:54
i used to work in synchronous
1:02:58
yeah this is like a totally new concept
1:03:05
the friendship is modern interface that
1:03:08
allows to make hp requests to servers
1:03:12
web browsers yeah that's exactly what
1:03:16
we want if you works with
1:03:20
xml http requests object the feature
1:03:23
perform all the tasks as a xhr object
1:03:28
okay so it works similar to that
1:03:32
in addition the fairchip is much simpler
1:03:36
and cleaner it uses
1:03:41
click on that do you know what promises
1:03:46
um is this like kind of um
1:03:49
pushing back stuff there i don't know
1:03:53
to be honest i don't know that's i'm
1:03:57
no not really totally new but we'll get
1:04:00
yeah we'll come back to this off
1:04:04
to words so each users promise to
1:04:08
more flexible features to make requests
1:04:11
to service for from those web browsers
1:04:14
okay that makes sense the fetch
1:04:17
actually um i don't know how long would
1:04:22
i just see a really casual definition of
1:04:26
it because i'm really curious now
1:04:29
i don't want to go to a further step
1:04:34
actually understand the previous ones
1:04:40
the promise object represents the
1:04:44
complete completion of failure of an
1:04:46
asynchronous application
1:04:51
so basically what it does is it just
1:04:58
completion of failure of an asynchronous
1:05:01
operation and and its resulting
1:05:08
okay that makes sense
1:05:14
i just you promise contents about
1:05:17
producing code and calls to consuming
1:05:26
telescope promise lots of appearance
1:05:30
okay it's kind of like um
1:05:33
you know how server requests work that
1:05:36
okay we go to 200 so that means that
1:05:39
this action is completed yeah
1:05:43
so like what i think is that
1:05:47
once you got a promise completely it's
1:05:50
tcp requests work if that makes sense um
1:05:54
once you get a promise complete then
1:05:55
only you move forward
1:06:01
okay i believe right now
1:06:05
what weird but we should probably go
1:06:08
ahead and read more
1:06:10
yeah i'm gonna probably go and read more
1:06:14
i actually wanna unders understand it
1:06:18
properly yeah okay
1:06:21
where's the promise i promise is an
1:06:23
object that may produce a single value
1:06:26
sometime in the future ah
1:06:31
may pretend either
1:06:34
a result value or reason that is not
1:06:38
eg and that will get a record i promise
1:06:41
one of three possible states fulfilled
1:06:46
pending promise users
1:06:50
can attach callbacks to handle
1:06:53
the fulfilled value or the reason for
1:06:58
right promise a uh eager meaning
1:07:03
that promise will start doing whatever
1:07:06
give as soon as the promised constructor
1:07:16
right um from what i'm understanding
1:07:20
it's basically when you send it a reque
1:07:25
when you send the server a request
1:07:28
and it's a promise then it will it will
1:07:32
with of a single value which
1:07:36
can be saved fulfill rejected or pending
1:07:41
but i will never come back with an
1:07:45
if you know what i mean yeah yeah
1:07:48
that's kind of what i thought right
1:07:52
that's what i'm understanding so far
1:07:56
yeah all right let's move on
1:08:02
uh cool so the fash
1:08:06
the fast method is available in the
1:08:09
global scope that instructs web browser
1:08:13
to a url okay cool so essentially
1:08:17
we'll be using this fetch method
1:08:20
and then inputting our api url there
1:08:26
oh then just one second i'll get some
1:08:45
the fetch requires the fetch requires
1:08:49
only one parameter
1:08:51
so it's saying that the fetch requires
1:08:53
only one parameter which is the
1:08:55
sure of the resource that you want to
1:08:59
okay cool that that makes sense
1:09:04
the fetch method returns a promise
1:09:07
so you can use then and catch
1:09:10
methods to handle it right right right
1:09:13
handles the response and then handles
1:09:16
so then handles the response and then
1:09:22
when the request completes the resource
1:09:27
okay yeah obviously because it's
1:09:30
at this time the promise will resolve
1:09:33
into a response object
1:09:35
okay so essentially by saying that when
1:09:40
com completes the promise which is
1:09:43
the single single value that is
1:09:46
go it will be it will be into
1:09:50
a response object basically
1:09:58
object is the api wrapper for the fash
1:10:03
response object has the number for
1:10:07
properties and methods to inspect the
1:10:11
uh-huh call to response reading the
1:10:16
if the contents of the response are in
1:10:24
context where you can use text method
1:10:26
now return the parameter
1:10:28
okay so this is that one
1:10:32
but we don't wanna we don't wanna fetch
1:10:36
handling the status code okay go down
1:10:41
let's go down javascript ap example
1:10:45
um we want to do a post
1:10:49
to click get users okay that's fine we
1:10:52
don't want to get we want to
1:10:55
render users then develop okay
1:10:59
summary post okay cool
1:11:02
so it's not there what i'm gonna do is
1:11:23
okay i've actually gone through a bit
1:11:28
all right but um this is only talking
1:11:32
fetching okay enjoy getting
1:11:36
we don't want to do that we want to post
1:11:40
isn't it yeah so what we can
1:11:44
probably do is post with fetch api
1:11:48
and check this one out fetch api
1:11:52
tutorial with fash post and header
1:11:55
which is exactly what we need to do yeah
1:12:03
so crash course on recipe okay yeah
1:12:06
that's exactly what api is
1:12:13
simply put uh as you push all the data
1:12:18
simply pull that yeah
1:12:21
okay that's fine that's easy get post
1:12:26
request uh this is the data you send to
1:12:31
like an order id to fetch okay that's
1:12:35
getting responses we need headers
1:12:39
okay we might come back to this one
1:12:43
right um hey before
1:12:46
jason took over okay the points in the
1:12:53
success this gets we don't need get
1:12:57
we need post fetch api
1:13:02
handle then respond convert to jason
1:13:05
this is still getting the account
1:13:07
working with headers
1:13:09
yep passing data to a post request okay
1:13:14
this is our beast here
1:13:17
yeah so we got the url
1:13:20
um we know that it's a
1:13:27
and body and id right
1:13:35
for us um the title would be
1:13:38
the name of the board which the person
1:13:42
yeah yeah which is in the url
1:13:45
yep and the body is
1:13:49
i don't think initially we have a body
1:13:55
for the board at least
1:14:02
oh there and and we have a board id
1:14:07
um i think we probably have to
1:14:11
make a method first right isn't it
1:14:19
we do have this yep
1:14:24
um just wanna console.login
1:14:28
check where the board id is actually
1:14:47
no way no i don't need you
1:14:54
i think what i have to do is console.log
1:15:03
windows.log this is industrial html so
1:15:20
okay let's see if this does it
1:15:45
you should bring it up yeah okay
1:15:48
test why is this coming up as test
1:15:54
um because you already are in the board
1:16:01
no i'm not in the board already this
1:16:18
okay i want to make sure that i'm
1:16:20
getting the board id there
1:16:23
uh not the body the board names sorry my
1:16:27
ah thinking of that we might need to
1:16:40
because at the moment they've only got
1:16:43
but that shouldn't be a big
1:16:46
non-functional problem yeah true
1:16:50
okay let's do this test
1:16:53
and go i should see a board
1:16:57
board name here okay perfect
1:17:01
so that does come up so all we need to
1:17:14
the javascript code
1:17:21
you know what i'm gonna do this is
1:17:24
really really too much
1:17:27
things going on here i'm going to do is
1:17:31
create a separate file
1:17:39
news i think good old c sharp
1:17:58
actually i'll do yeah
1:18:01
middleweight should be fine
1:18:14
i'm gonna do all this
1:18:23
because i don't like including
1:18:26
javascript as in the
1:18:28
yeah inside it i get what you mean
1:18:30
things inside html
1:18:33
just yeah i can't stand it yeah for sure
1:18:37
i don't know how people do that but
1:18:41
okay cool so this is the script
1:18:48
uh what did we do wrong here did we do
1:18:54
because i can't script.js
1:19:02
because it's not showing in the colors
1:19:11
what did i do wrong here interesting
1:19:32
wait that looks fine to me
1:19:35
yeah but actually i might have to import
1:19:39
yeah i'd probably have to import it
1:19:43
uh that file in this
1:19:50
yeah but it's already included wait
1:19:53
you didn't end no it's not so
1:19:56
in order javascript to work in this
1:20:00
file i need to import this
1:20:03
file in this page as in in industrial
1:20:07
html page only in the same folders
1:20:13
yes they are in the same folder
1:20:24
like how it's written on the top ones
1:20:27
yeah yeah that's right
1:20:30
and middleware.js yeah
1:20:41
so now what i can do is get rid of all
1:20:46
yep and just end that yeah
1:20:51
yeah for consistency purposes in the
1:20:54
yeah pull and i just want to
1:20:58
try this and see if it still works
1:21:02
yep um we don't need even this
1:21:08
yeah we don't because how he has done it
1:21:14
ah okay cool i know i know what's the
1:21:18
this is the problem yeah
1:21:29
okay i'll just check if this
1:21:35
that's true should probably work
1:21:39
it's always good to keep
1:21:42
checking as in testing after small
1:21:55
html and i should still get
1:21:59
the console saying
1:22:02
the log here same coordinate
1:22:05
oh yeah yeah perfect that works
1:22:09
encore error script.js ah
1:22:13
io is not defined core so i'm not gonna
1:22:18
for now because we don't have anything
1:22:22
script.js at the moment yeah
1:22:25
comment that one out okay
1:22:28
cool so and all our
1:22:32
gs code can come here now yep that's
1:22:41
uh i think it would be
1:22:45
function post board name
1:22:53
and how rare was that
1:22:57
right fetch no not that one
1:23:01
can we define data first yeah and i'm
1:23:06
pretty sure data is a key word here
1:23:13
oh yeah because they have got
1:23:17
underscore is it yeah
1:23:20
or i could be wrong but
1:23:23
yeah really did you try this
1:23:31
it's a calls yeah um
1:23:39
see this is where we need to make some
1:23:42
change in the database now um
1:23:46
i'm going i'm just trying to think how
1:23:49
we will do it um can you possibly add a
1:23:56
okay in jira saying
1:24:01
as in a sub task of
1:24:05
posting a board name as in change the db
1:24:13
to actually include the board name okay
1:24:20
so i'll link that issue to
1:24:47
so that can be one two three i don't
1:24:50
really care at the moment i just wanna
1:24:52
want this to work yep
1:24:59
name would be in the body
1:25:03
yes that's right isn't it yeah
1:25:09
this would come from the board name
1:25:15
um just one second then a little bit
1:25:25
all right that one's there and then
1:25:29
user id one we don't really need the
1:25:36
cool so that one's there and then we do
1:25:41
and we need to give our api
1:25:45
name which i'll get from
1:25:53
board yeah that's the
1:25:56
url so i'll give it here
1:26:07
okay and then what i'm gonna do
1:26:11
is that's the board
1:26:27
i will use it don't worry and
1:26:30
um i'm going to use method
1:26:45
jason or stringify
1:26:50
and then that would be on data
1:27:01
and then headers i need the headers
1:27:43
do this content type
1:28:02
this the content type okay must be the
1:28:14
contents application.json
1:28:20
let's try this one as well
1:28:24
okay and then once this is done
1:28:59
and then this one comes yeah headers
1:29:03
then first api is done
1:29:06
then what i want to do is do then
1:29:10
this will handle our response
1:29:32
risk so then in this one our response
1:29:36
will be handled which will be in
1:29:47
okay and then we're gonna
1:29:53
console.log json there
1:29:56
the object that we receive console.log
1:30:09
and then what's going to happen is cat
1:30:13
but if it if anything goes wrong
1:30:17
then we're gonna do
1:30:21
we're gonna cache the error and then
1:30:31
but why is it giving me these errors now
1:30:35
any declaration all expected
1:30:38
so where did i mess up
1:30:42
where did i mess up hdmi one second you
1:30:45
probably can't hear me
1:30:48
i can't i can sorry i had to use the
1:30:55
all right um i've just coded this bit
1:31:01
how's it going and i'm actually
1:31:06
getting a few rest quickly lines
1:31:11
okay so we have data on board id which
1:31:16
no not to worry about we need to get
1:31:19
i found the problem i'm gonna win it
1:31:24
yeah find the problem
1:31:42
actually i need ah
1:31:48
yeah okay there is
1:31:52
expert before response
1:31:59
what's this for them
1:32:02
that one is closing there that was
1:32:07
that one's there that was there that was
1:32:11
then catch declaration respect
1:32:18
oh sorry i was muted i was trying to
1:32:24
so what are we trying to do copy and
1:32:27
this and see if it still gives me the
1:32:30
yeah it still gives me there so
1:32:34
what we're trying to do here is
1:32:51
we have this object
1:32:55
that we want to post and then
1:32:59
we are getting the api
1:33:07
and then we are simply uh telling you
1:33:10
it's about the post
1:33:15
stringifying the body yeah
1:33:19
and then including the headers as well
1:33:27
handling the response the
1:33:30
json object and then just console
1:33:34
logging the json object and then
1:33:38
if it fails then we want to build to
1:33:41
catch it and console log there but i've
1:33:47
i don't know why this is saying that
1:33:50
that one is fine that one ah
1:33:54
no that one's fine as well
1:34:01
actually i wanna change all these to
1:34:07
hmm that's interesting
1:34:23
so that's how with that
1:34:26
and this is our this one
1:34:35
no no maybe try running it
1:34:38
looks fine i think that's a good idea
1:34:43
run it and see how it goes
1:34:59
i'll go ahead and edit the video today
1:35:02
yes please w that'd be great
1:35:08
okay let's see if it does the trick
1:35:25
is this was morning about
1:35:35
i think we might have something
1:35:44
why is he going to print data to
1:35:47
console convergent data and catch errors
1:36:03
i'm pretty sure that was a problem
1:36:07
he's got that but i don't know why he's
1:36:14
but hey he doesn't there should have
1:36:17
been some including some
1:36:19
it does not oh no um
1:36:22
let's see if any other site has to say
1:36:24
something else i guess
1:36:30
i'll do post yes it's post method
1:36:33
in french first yes
1:36:57
body parts that's not what we are
1:37:14
um there's one on stack abuse
1:37:20
that's a funny name to be honest stack
1:37:35
ah it's here first example
1:37:40
yeah why does he have
1:37:43
two of the of the thens
1:37:48
that doesn't make sense
1:37:52
hmm interesting just remove one
1:37:56
um then for now and
1:38:00
see where we got or
1:38:11
ah yeah no i should
1:38:15
there's one warning
1:38:18
that's fine i don't really care whether
1:38:22
warnings at the moment to be honest
1:38:26
open bracket before
1:38:29
responding no that's fine um all the
1:38:31
brackets are fine so
1:38:32
um okay cool i'm gonna
1:38:37
run this and see what happens yeah
1:39:04
give me some magic
1:39:08
test so he's just printing that one up
1:39:18
just bringing that one based on coming
1:39:25
are we even calling this function
1:39:26
anywhere we have to call this function
1:39:33
why am i doing what am i doing
1:39:37
yes you have to call the function
1:39:41
so when the when this button click just
1:39:43
call this function i guess
1:39:46
yeah yeah that's what i'm gonna do now
1:40:01
it's it's not in there it's
1:40:14
this is go so what i'm going to do now
1:40:18
call that function why
1:40:22
but then you have to include in this
1:40:26
yes i'm gonna do that because i don't be
1:40:29
this is not my way of doing things at
1:40:33
whatsoever so i'm gonna probably do is
1:40:37
i just can't stand it man so i'm i'm
1:40:41
a bit with it so this is the code which
1:40:45
uh made through or this is the um
1:40:51
um i don't want to blame
1:40:54
anyone at all so i'm not even going to
1:40:58
i'll just you can just think of it
1:41:01
i don't i don't really know who did it
1:41:04
i don't want to name people here
1:41:08
so yeah yeah i'll just do
1:41:12
that one and then create a function here
1:41:21
you can go return false
1:41:25
and then that's the function that one
1:41:33
so now all i can do is call these
1:41:36
functions over there
1:41:42
where was it home uh
1:41:48
no why do i mean that too cold
1:41:52
do you have to call that much no
1:41:58
yeah yes i see that
1:42:08
you probably need needed that but
1:42:22
in the go button where we go button is
1:42:26
we need return go so we are
1:42:30
we we probably have to put every
1:42:34
because it's having one
1:42:37
yeah fair enough um we can do that so
1:42:41
call multiple functions on click but
1:42:44
make sure to call the go function first
1:42:48
okay how do we do that i think you just
1:42:51
them in comma one second okay cool i
1:43:05
name so again i'll go ahead and confirm
1:43:08
write it separated by a semicolon okay
1:43:12
oh so in in that way
1:43:16
semicolon semicolon and after
1:43:19
post board name as well semicolon
1:43:23
yeah that's cool brilliant
1:43:27
so let's see if this works um
1:43:33
well we could probably call it a night
1:43:36
it's half 11 already
1:43:42
to be honest it has been it's been it's
1:43:46
yeah no i mean we got we almost stole a
1:43:49
whole function which we just started
1:43:55
hopefully what am i doing
1:44:06
come on walk for us please i'm asking
1:44:14
all right it didn't give us any console
1:44:46
and do the same here
1:44:50
just wanna check if it's even coming in
1:45:01
i have a feeling that it's not able to
1:45:02
access the probably
1:45:05
middleware.js so i think wait
1:45:08
and then can you go back on home.html
1:45:12
onto html right where did you declare
1:45:16
um this thing middleweight.js
1:45:19
yeah you didn't write type um
1:45:24
is that really the problem yeah
1:45:28
um so type equal to
1:45:36
friends love just but um no text
1:45:42
i don't know i haven't done that that
1:45:44
way so maybe i don't know sorry
1:45:48
sorry i don't need to be sorry okay
1:45:52
cool we can try that one as well
1:46:03
i think that must have been the problem
1:46:06
yep um let's we'll see
1:46:28
i'm typing ah actually
1:46:33
that's too hard refresh
1:46:39
of course because it's not there
1:46:42
yep it's never there
1:46:47
is he always coming back with
1:46:51
actually that's not our issue
1:46:54
i'll just go and do this
1:46:59
okay let's let's leave it for today yeah
1:47:02
that's all cool it's very productive
1:47:06
though i like it more for sure
1:47:10
keep that ticket in testing only for now
1:47:14
and um and probably
1:47:17
remove uh do the fetch
1:47:20
api as probably done as in
1:47:23
that's going to be the process as in we
1:47:28
yeah for sure yeah there's no point
1:47:31
so yeah cool anyway um thanks thanks for
1:47:34
joining in today um
1:47:35
and thanks again for having me
1:47:40
thanks all for turning up and um thanks
1:47:44
the viewers spell it's been
1:47:47
incredible fun it was a pro productive
1:47:52
we'll see you guys tomorrow nice
1:47:55
same time and same duration of the
1:47:59
two hours so stay tuned to
1:48:04
watch us code and how we do this
1:48:07
incredibly fun stuff online yeah all
1:48:11
have a good night good night kathy
