►
From YouTube: #Hacktoberfest Office Hours - 20.10
Description
A
Hey
we're
live
so
welcome.
A
A
A
A
A
B
A
A
C
C
D
D
D
D
B
B
B
A
A
Okay,
so
let's
let's
leave
it,
I'm
not
gonna
play
with
it
now,
because
I'm
just
gonna
take
your
time
I'll,
try
to
figure
it
out
figure
it
out
later.
If
there
are
no
questions,
oh
okay,
so
before
antoinette
before
we
jump
into
your
questions,
let
me
just
summarize
so
we
have
20th
of
october
two
weeks
left
till
the
end
of
the
october
fest.
A
And
we
have
24
contributors
so
far
on
the
oktoberfest
and
57
pull
request
merged,
which
is
awesome
but
yeah.
Let's,
let's
look
into
the
comment
section,
because
there
are
many
many
questions
I
think
from
unto
death.
A
Okay,
so
the
question
is
to
a
hacktoberfest
issue
about
the
parameters
in
the
html
template
and
the
question
is,
let
me
show
it
on
the
stream.
I
don't
understand
how
you
pass
the
parameters
to
the
template.
I
mean
if
I
want
to
pass
description,
can
I
do
it
like
this.
A
A
A
Let
me
just
turn
on
yeah
it's
the
last
time.
I
have
only
one
monitor.
A
Sorry
for
that,
because
this
way
I
can
see
if
there
are
some
additional
questions,
otherwise
I
cannot
see
them
yes,
so
the
questions
come
to
this
issue,
so
the
issue
title
is
parameter.
Doesn't
description
does
not
render
in
resulting
output
with
html
template?
A
What
is
it
about
in
detail?
So
the
let
me
show
some
awesome
api
file.
A
So
when
an
async
api
file
you
can
have,
you
can
define
a
list
of
channels
and
channels
can
have
parameters
so
those
special
values,
let
me
make
it
bigger
yeah,
so
can
have
parameters
so
those
special
values
in
between
the
mustache
and
you
can
describe
those
parameters
later
in
a
parameters
object.
A
A
A
Let's
double
check
so
typical.
A
A
So
here,
as
you
can
see
what
we're
doing
so,
we
are
rendering
a
div
element
and
we're
templating
we're
treating
parameters.
Let's
say
as
a
we're.
Iterating
over
the
parameters,
objects.
A
A
Schema
the
the
schema
of
the
parameter
to
schema
prop
to
schema
prop
macro
and
that's
the
second
link
I
shared
so
a
macro.
The
schema
prop
macro.
In
short,
what
macros
are
so?
These
are
like
javascript
functions,
let's
say
so.
It's
like
reusable
template
that
accepts
arguments.
A
A
So
I
think
the
background
is
pretty
much
clear
and
now,
looking
again
on
the
question,
how
you
pass
parameters
to
the
template,
I
mean,
if
I
want
to
pass
description,
can
I
do
it
like?
A
A
A
Then
the
schema
prop
macro
just
has
no
access
to
this
description.
It's
just
gonna.
Take
the
the
description
from
the
from
the
schema.
If
it's
provided
in
the
schema.
A
Now
how
to
solve
it,
the
easiest
would
be
just
to
pass
like
like
at
the
end,
let's
say,
extend
the
extent
the
the
macro
pass,
parameter,
dot,
description
and
then
consume
it
here.
Right
so
add
it
to
this
macro
and
then
yeah
add
it
to
the
template.
A
If
it's,
if
it
makes
sense,
because
at
the
end,
this
this
macro
is
purely
designed
to
to
render
the
schema
and
parameter
description,
it's
not
part
of
the
schema.
So
that's
a.
A
A
B
A
So
I'm
now
thinking
out
loud,
but
so
what
what
I'm?
What
I'm
saying
is
basically
have
a
in
between
44
and
45
have
a
logic
that
checks
if,
if
parameter
dot,
description
returns
something,
and
if
this
description
is
returned,
then
it
should
be
added
to
parameter
schema.
A
B
B
A
B
A
A
A
Okay,
I
didn't
use
it
quite
some
time
ago.
Okay,
so
let
it
download
chromium
for
the
first
time
but
yeah.
Let
me
jump
to
the
schema
probe.
A
A
D
B
B
A
A
B
A
A
A
A
A
So
antoneth
are
you?
Are
you
still
there
with
me.
A
Okay
cool,
so
let
me
like
go
through
step
by
step.
The
the
solution,
like
I
say,
kind
of
summary,
what
I've
done
and
then
shoot
me
with
questions.
A
B
A
A
Pass
a
description
to
it
now,
what
happens
if
description
is
is
not
provided
then
it's
I
mean.
Basically,
it's
not
a
problem,
because
if
description
is
not
provided,
let's
see
in
the
api.
A
A
When
we
take
async
async
document,
we
parse
it
with
our
async
api,
javascript
parser
and
as
a
result
of
the
of
the
parsing,
we
give
you
a
a
object
with
a
lot
of
helper
functions
that
make
it
much
easier
for
you
to
access
parts
of
the
async
api
document.
A
So
you
don't
have
to
access
it
like
a
usual
like
json,
but
you
have
those
nifty
functions
available
and
you
can
always
consult
with
the
api
of
the
parser.js.
A
A
Let's
take
a
look
on
the
on
the
operation
because
parameter
is
no
parameter
is
not
part
of
the
operation.
It's
part
of
the.
A
A
These
are
like
mixes,
are
a
way
of
extending
the
models
in
a
nice
way
with
functions
that
are
used
across
the
model,
the
different
models
so
description,
it's
a
function
that
is
used
in
many
different
locations
of
the
spec.
So
that's
why
it's
better
to
have
one
mix
in
and
then
yeah
extend
model
with
this
mixing.
A
If,
if
okay,
if
it's
undefined
and
will
return
null,
okay,
that's
cool,
so
basically
from
this
implementation,
we
know
that,
if
description
will
not
be
there,
it
really,
as
it
stated
in
the
in
the
js
doc,
it
will
return
null,
which
is
fine,
which
means
that
in
this
particular
case
we
do
not
need
to
use
this
test
description
function.
A
A
A
A
Just
different
value
is
passed
to
the
template,
so
this
could
be
taken
into
a
separate
file
and
we
could
have
a
a
macro
just
like
the
schema
html
file.
So
you
would
create
a
separate
file
called
description,
dot
html
in
and
in
this
in
this
new
file.
A
A
A
new
macro
called
get
description,
and
this
this
new
macro
get
description
would
accept
a
a
argument
like
called
description
right.
B
A
Goal
you
even
you
can
even
see
that
this
this
schema
prop
macro.
It
also
uses
some
some
external
macros,
so
adding
additional.
A
A
And
you
can
see
here,
for
example,
how
this
is
used.
Yeah,
of
course,.
A
B
A
A
A
Yeah,
it's
so
at
the
end,
it's
up
to
you,
how
you
name
it
so.
Basically
it's
we
somehow
need
to
to
name
this
variable.
A
A
So
that's
why
I
call
it
out
alt
description
or
late
dsc
like
desk
alt
desk,
but
it
can
be
called
even
long
name
like
alternative
description,
but
all
alternative
desk.
Maybe
this
one
is
better.
A
Code
and
extra
stuff,
if
you
could,
that
would
be
great.
So
the
the
rule
that
we're
following
here
when
we're
when
we're
working
on
templates
is
that
we.
A
Okay,
here
it
is
so
we
let
me
make
it
bigger,
so
we
basically
we
did
not
want
to
abuse
the
streetlight
example
too
much
because
we
noticed
that
we
have
like
every
template
has
its
own
version
of
streetlight
example.
So
we
are
thinking
like
yeah.
Let's
make
a
a
single
dummy
example
that
will
not
be
will
not
serve
as
a
an
example
for
the
community
to
to
to
see
how
async
api
file
should
look
like.
A
So
for
us,
this
dummy
example
it's
something
that
we
can
abuse
we
can
call
over
complicate,
but
the
goal
is
to
have
a
as
feature
rich
example
as
possible,
meaning
we
want
to
present
as
many
features
as
we
can
in
the
single
document.
So
it's
much
easier
to
develop
templates
to
to
have
sample
data
for
developing
templates,
because
the
schema
you
can
imagine
there
are
different
variations
of
of
things.
You
can
do
so
yeah.
A
A
Should
have
an
example
that
you
don't
only
have
a
description.
A
A
A
A
few
minutes
left,
so
let
me
if
you
can
stay
longer
a
bit
to
be
my
voice.
Tester.
That
would
be
awesome.
I
wanna
make
sure
that
I
can
stream
the
music
as
well.
So
I'm
gonna
now
play
with
the
settings.
If
you
don't.
A
C
C
A
A
A
C
C
C
B
A
A
Okay,
so
antoinette.
A
A
For
example,
here
when
I
wanted
to
somehow
make
sure
that
the
schema
description
is
not
rendered
and
only
the
main
description
is
rendered,
I
had
to
extend
dummy
example
manually
with
this
manually
with
this
additional
description,
which
was
fine
for
local
development.
That
was
fine.
I
I
finished
the
work,
that's
it,
but.
B
B
B
A
A
Which
makes
it
super
strange
why
I
cannot
see
it
on
my
local,
what
the
heck
just
happened,
but
yeah
anyway,
if
you
go
to
the
latest
html,
you
see
this
information
about
a
dummy
yam
file
in
the
readme
in
the
development
section.
A
B
A
C
B
B
B
B
B
A
A
A
C
A
Okay,
but
anyway,
there's
this
saying
in
polish,
we
say
fist
cuts,
which
basically
means.