►
From YouTube: Contributor-first @AsyncAPI #10
Description
Date: 3rd of November 2021
Edition: 10
Meeting designed for AsyncAPI contributors that can come and ask for help with the first contribution.
All scheduled meetings can be found in the AsyncAPI calendar https://calendar.google.com/calendar/u/0/embed?src=tbrbfq4de5bcngt8okvev4lstk@group.calendar.google.com or as a list here https://github.com/asyncapi/community/labels/meeting
A
Hey
folks
welcome
to
contributor
first
meeting
it's
3rd
of
november,
and
it's
a
second
edition
today,
because
we
already
had
a
contributor
first
meeting
today
in
european
morning
now
it's
european
afternoon
or
america's
morning,
so
welcome
to
the
live
stream
dedicated
explicitly
to
people
that
want
to
contribute
to
asking
api.
A
So
folks
can
join,
ask
any
questions,
join,
live
stream
or
just
watch
the
live
stream
and
interact
with
us
over
the
chat
and
ask
for
support
and
some
explanation,
but
before
we
jump
into
the
core
of
the
of
the
live
stream.
Let
me
just
tell
some
some
more
details.
A
So,
basically,
as
you
can
see
at
the
top
of
the
of
the
video
in
two
weeks,
we
have
a
async
api
conference,
that
is,
that
has
like
five
platinum
sponsors.
It's
ibm
ably
wso2,
solus
and
postman,
and
we
we
start
in
two
weeks.
A
The
contributor
first
meetings
were
supposed
to
be
only
in
october,
and
that's
what
we
also
told
to
platinum
sponsors
that
we're
gonna
show
the
logos
in
october,
but
yeah
looks
like
people
like
the
sessions,
so
we
will
just
continue
doing
it
twice
a
day
every
week
until
the
conference,
which
means
morning
session
for
the
for
the
live
stream
and
in
afternoon
session
for
the
for
the
live
stream
will
be
as
well
next
wednesday.
A
Then
we
have
a
conference
and
then,
after
the
conference
we
most
probably
will
take
a
short
short
short
break
and
we'll
schedule
a
long
term
invitation
for
the
contributor
first
meeting,
I'm
not
sure.
Yet
what
the
schedule
will
be
super
open
on
to
your
opinions
about
it.
I
think
that
we
should
keep
it
weekly,
but
maybe
not
twice
a
day,
maybe
in
different
time
zones.
Every
week.
A
Let's,
let's
explore,
I
mean
we
have
pretty
scheduled
pretty
regularly
scheduled
public
meetings
with
the
with
the
community
and
the
other
meetings
we
have.
So,
let's,
let's
experiment,
maybe
with
contributor
first,
maybe
maybe
8
a.m.
Utc
is
not
the
best
one.
Maybe
we
should
do.
A
10
am
utc
or
instead
of
4
pm
utc.
We
should
actually
do
5
6
pm
utc,
which
would
be
a
killer
for
me
because
I'm
here
based
in
poland
but
yeah.
Let's,
let's
see,
let's
please
share
your
opinions
with
with
us.
Definitely
in
the
today
you
can
share
your
opinions
about
how
the
schedule
should
look
like
just
share
it
in
the
chat
or
or
just
later,
when
we
start
discussion
in
our
slack.
It
will
definitely
be
in
the
how
to
contribute
channel.
A
Now
I
see
already
some
people
in
the
in
the
live
stream
listening
to
the
live
stream,
so
please
say
hello
in
the
in
the
chat.
So
today
we
will
have
a
special
guest.
So
in
the
morning,
if
you
did
not
watch
the
live
stream
in
the
morning,
we
had
a
special
guest,
which
was
who
was
jonas
lagoni
and
we
talked
about
modelina
and
how
we
can
scale
the
user
base
and
the
and
the
contributor
base
for
the
project.
A
And
now
I'm
gonna
have
a
special
guest
who
is
with,
but
I
probably
did
not
correctly
pronounced
his
name.
I'm
gonna
share
a
link
to
the
live
stream
in
the
chat
as
usual,
for
others
as
well.
A
Basically,
with
will
will
join
me
and
we're
gonna
talk
about
the
java
template
that
we
have
at
async
api,
because
it's
at
the
moment
not
really
maintained
and
does
not
have
a
regular
maintainer
and
visvaprat
offered
that
he
he
can
contribute
to
the
project.
I
also
saw
some
people
in
this,
our
slack
that
expressed
interest
in
in
java
like
code
generators,
so
yeah,
let's
explore
java
template
and
let's
see
what
has
to
be
done
with
the
project,
to
actually
make
it
great
again.
A
B
A
First
of
all,
huge
apologies,
if
I
pronounce
your
name
incorrectly,
and
I
would
love
if
you
could
correct
me
and
say
how
should
I.
A
B
So
I
am
vishwa
prasad
from
india.
Basically,
I
work
as
a
full
stack
developer
or
most
of
the
times
on
the
back
end
in
our
company
at
zoho.
So
during
my
free
time
I
learned
a
lot
of
things
from
open
source
communities.
A
Thank
you
very
much
for
kind
words,
so
I'm
gonna
pay
you
back
because,
like
visva
prasad
for
others
that
listen
joined
not
so
long
time
ago,
you
joined
our
slack
two
months
ago.
I
think.
A
Yeah
yeah
and
you
already
contributed
a
lot
you
you
engaged
from
the
very
beginning.
So
maybe
we're
welcoming
but
you're
also
super
super,
supportive
and
and
yeah.
A
Thanks
a
lot
okay,
so
we're
gonna
talk
about
java
language,
I'm
not
I'm
not
the
best
fan
of,
but
luckily
the
code.
A
Yeah,
so
it's.
A
A
So
far,
it's
yeah
it's
an
one
of
the
first
asking
api
projects
so
javascript
and
the
and
the
code
templates.
I
don't
think
we
support
writing
them
in
typescript.
We
don't
yet
how
to
say
it
properly
like
we
don't
build
them
when
we
when
we
pass
a
template
to
the
to
the
generator.
I
think
there
is
an
open
issue
about
it
to
support
writing
templates
in
typescript.
A
So
if
you're
interested
we
can
like,
we
could
think
about,
like
maybe
first
start
enabling
it
in
the
in
the
generator
but
but
yeah.
Let
me
open
the.
Let
me
start
sharing
screen
and
let's
talk
about
the
project.
A
So
for
others
watching
us,
please,
if
you
can
just
confirm
in
the
chat
that
you
can
like
hear
us
well,
that
the
the
qualities
is
good,
especially
if
it
comes
to
screen
sharing
because,
like
from
my
perspective,
it
looks
good
but
not
sure
about
yours.
A
So
can
you
confirm
if
the
the
quality
of
the
share
screen
is?
Is
it
good.
B
Yeah
yeah,
I
can.
I
can
see
it
properly
that
it's
just
here:
okay,
cool.
A
Okay,
good
so
just
say,
like
yeah
context
for
everyone
watching,
so
we
don't
jump
directly
into
the
code
of
the
javas
spring
template,
so
what
it
basically
means
that
it's
a
java
spring
template
what
it
means
that
it's
a
template.
So
the
project,
the
template,
it's
a
it's!
It's
a
like
a
code
generator.
It's
called
template
because
it's
it's
now
how
the
naming
works
in
asking
api
generator.
So,
basically,
I
think
api
generator
is
a
it's
a
framework.
A
It's
a
a
tool
with
set
of
settings
and
functionality
that
allows
you
to
write
a
a
template
that
later
on
are
are
powered
by
the
generator
functionality
and
you
can
output.
Whatever
you
want,
you
can
write
template
to
output,
markdown
files.
You
can
write
templates
to
output
html
or
you
can
write
templates
to
output,
javaspring
application.
A
Okay,
we
have
confirmation
from
john
that
everything
is
sounds
good.
Thank
you
thanks,
john
and
hello,
so
the
the
templates
they
are,
they
can
be
stored
in
a
separate
repositories.
So
that's
why
they
are
not
part
of
the
generator.
So
if
you're
coming
from
open
api
world
and
one
of
the
most
popular
projects
that
have.
A
That
are
used
to
generate
some
code,
basing
on
open
api
files.
As
far
as
I
remember,
one
of
the
most
popular
it's
written
in
java
and
all
the
templates
actually
are
inside
the
the
same
project,
same
generator
project.
So
so
here
it's
different.
We
because
it's
it's
it's
javascript!
We
it
allows
us
to
also
benefit
from
the
the
whole
ecosystem
of
javascript,
including
the
node
package
manager.
A
Now,
if
it
comes
to
this
specific
java
spring
template,
its
current
situation
is
that
it
has
users.
We
know
that
people
use
it,
because
sometimes
we
get
issues
from
users,
but
the
the
last
maintainer
that
was
helping
out
with
with
adding
improvements
to
the
project
left
few
months
ago,
it's
not
possible
to
contact
him
anymore,
like
we
tried
a
few
times,
so
I
and
sometimes
other
people.
A
We
just
review
pull
requests
only
when
we
just
have
a
we
have
time
and
we
just
make
sure
that
there
are
not
big
changes
in
the
project,
but
it
it's
still
like,
like
bug
fixes,
are
when
the
request
with
bug
fix
is
created.
We
make
sure
that
it's
yeah
reviewed
and
merged.
So
it's
definitely
a
project
that
is
super
open
to
onboard
new
maintainers
someone
who
can
like
take
over
the
responsibility
over
the
project.
A
Now,
that's
if
it
comes
to
current
maintenance
status
of
the
project.
Now,
if
it
comes
to
code
generators
and
the
java
code
generators
there
are
at
asking
api,
there
are
two.
So
it's
this
java
spring
template
and
also
excuse
me.
A
Okay,
I
finally
found
the
proper
location,
yes
submissions,
so
there
was
a
a
submission
from
a
team
at
ibm
with
java
template
as
well,
but
it's
not
like,
and
but
it's
again
something
much
different
than
these,
so
so
in
case
of
java
spring
template.
It's
focusing
on
java
spring
to
what
I
understand
about
java
and
spring.
As
far
as
I
know,
java
spring
is
different
than
java
spring
cloud
stream
and
so
that
this
project,
it's
java,
related,
but
it's
it's
purely
consuming
the
the
spring
cloud
stream
api.
A
And
this
project
it
has
maintenance
when
they
are,
there
are
two
maintainers
from
from
solas
and
and
in
case
of
this
java
template
that
folks
also
want
to
donate
to
using
api.
I
think,
like
I'm,
not
think,
I'm
sure
it's
there's
nothing
related
with
spring.
So
at
this
template
it's
gonna
be
not
spring
related,
but
again
this
one
already
has
a
base
of
developers
supporting
it
this
as
well.
A
But
again,
this
call
today
call
is
about
specifically
this
template.
That
has
has
no
maintenance,
but
has
a
user
base
so
so
far,
so
good,
all
clear,
okay,
cool
now
how
to
start
contributing,
or
maybe
the
goals
for
the
project
for
the
future.
A
So,
basically,
whenever
you
think
about
asking
api
generator
templates.
A
You
always
have
to
remember
about
the
generator
itself
and
the
generator
functionality
and
generator
documentation
so
because,
as
I
said,
like
templates
template
project,
it's
just
a
a
templated
files
that
define
what
you
get
in
the
output,
but
they're
just
using
functionality
that
comes
from
the
generator.
A
So,
whenever
you're
contributing
to
the
template,
you
want
to
use
some
specific
functionality.
There
are
two
resources
you
have
to
look
at,
so
the
docs
of
the
generator
and
the
most
important
is
authoring,
an
emd
file
that
explains
in
details
all
the
all
the
all
the
functions
on
all
the
features
that
generator
has,
but
also
there
is.
A
A
So
so,
basically,
two
main
learning
resources.
Is
this
authoring
so
how
to
write
a
template?
And
if
you
don't
like
to
read
docs,
you
rather
prefer
to
learn
from
the
code
and
like
some
examples,
then
this
is
the
the
example.
You
should
have
a
look
at
now,
something
that
is
a
a
very,
very
challenging
with
java
spring
template
long
term,
if
you
want
to
like
take
over
ownership
and
and
maintaining
long
term,
is
that
if
it
comes
to
the
authoring.
A
A
So
when
you
create
a
template,
one
of
the
configuration
points
is
renderer
renderer,
it's
the
it's,
the
it's
the
engine
in
the
generator
that
consumes
a
template
and
renders
the
output.
So
the
template
at
the
moment
can
be
created
with
two
different
temp
types
of
templates
or
render
engines
the
first
one
that
was
in
the
generator
it's
nunjucks,
it's
a
templating
language
and
and
the
other
one
is
react.
So
the
the
next
render
engine
that
we've
added
was
was
based
on
react
or
react.js.
A
If
you,
if
you
used
it
before,
I
don't
think
we
have
time
to
talk
about
now
like
why
we
did
it
and
what
was
the
benefit
but
yeah.
The
benefits
were
were
great,
like
templates
written
in
nunjacks,
it's
just
super
hard
for
template
developer
to
to
maintain
them
and
to
to
debug
them
so
and
reuse.
Some
more
or
some
some
components
between
different
templates
and
and
react
enables
all
of
that.
A
Now
the
thing
is
that
java
spring
template
it's
written
in
non-jux,
because
it's
an
old
template
and
and
of
course
it's
working,
but
you
just
have
to
keep
in
mind
that
at
the
moment,
among
the
maintainers
of
the
generator,
I
don't
know
even
a
single
maintainer
that
would
love
to
keep
nunjacks
forever
because
it's,
as
I
said,
like
it's
really
hard
to
to
use
in
bigger
code
generators
because
of
the
debugging
limits.
A
So
we
so
far,
all
the
maintainers
of
the
generator
at
some
point
of
time
would
would
prefer
to
have
react
only
and
as
a
main
main
template
engine.
A
But
I
know
that
there
are
templates
that
are
heavily
used
like
the
java
spring
cloud
stream
template
that
are
still
written
with
with
nun
jacks
and
they're
they're
working
fine
they're
used
by
people
and
at
the
in
the
end
the
end
user
does
not
complain,
but
just
you
have
to
take
into
into
account
that
might
be
that
in
a
year
or
two
first
of
all,
we
we
will
think
about
just
staying
with
react
plus
plus
it's
it's.
A
I
think
it's
going
to
be
much
easier
to
get
some
support
from
other
community
members
to
to
review
the
react
engine
in
use
than
than
nunjax.
A
It's
just
my
opinion.
I
guess
that
I
would
help
with
any
anything
you
use
so
but
yeah
anyway.
That
had
to
be
explained.
That's
what
the
situation
is
at
the
moment
now,
rewriting
from
from
nun
jax
to
to
react.
A
It's
not
super
hard.
It's
it's
doable.
We
did
it
already
a
few
times.
We
rewrote
the
the
markdown
template
from
nun,
juxta,
react
and
and
some
other
code
generators
like
typescript
for
for
nuts,
js
knights,
nuts,
io
and
and
some
other
templates.
A
So
it's
not
a
a
very
big
deal,
but
of
course
it
might
be
a
problem
here
in
this
in
this
template
because
we
don't
have
contact
with
the
maintainer.
A
So
we
won't
be
able
to
answer
specific
questions
like
why
something
in
the
template
is
done
this
way
or
not
a
different
way,
because,
like
of
the
and
the
questions
are
related
to
the
java
output,
we
had
similar
situation
with
the
go
template,
so
we
had
a
go
template
that
was
in
exactly
the
same
situation,
so
it
was
written
with
nun,
jax
the
maintainer
stopped
contributing,
but
then,
and
then
anand
that
showed
up
in
the
in
the
community
wanted
to
contribute.
A
A
So
at
some
point
of
time,
if
we
see
that
it's
better
to
really
rewrite
it
from
scratch,
with
some
breaking
changes,
then
let's
let's
discuss,
but
I
think
we're
all
opened
and
if
that's
the
only
way
to
go
we're
just
going
to
take
this
path.
A
So
people
like
that
are
just
in
the
chat,
feel
free
to
to
jump
in
and
and
shoot
your
questions
in
the
in
the
in
the
chat
and
yeah.
So
let
me
go
into
some
tips
and
tricks
like
especially
in
the
java
template.
A
What
you
need
to
remember
is
that
it
has
its
own
samples
that
it's
tested
against,
so
so
you
have
to
have
a
specific,
binding
information
for
kafka,
provided
in
your
asking
api
documents
to
make
sure
that
the
java
template
will
work
with
your
kafka
with
your
document
that
is
describing
a
application
connecting
to
kafka.
A
So,
as
you
can
see
at
the
moment,
template
supports
two
protocols,
mqtt
and
kafka,
and
it
also
has
some
configuration
options
and,
and
that's
what
kind
of
also
will
make
it.
I
guess
much
more
challenging
to
to
rewrite,
but.
A
But
yeah,
as
you
can
see,
some
configuration
options
are
related
just
to
mqtt.
So
it's
very
much
very
much
flexible.
If
you're
writing
when
you're
writing
a
template
and.
A
And
what
else
I
mean
I
I
can
like
goes
through
it
and
and
scroll
just
through
the
through
the
readme.
I
can
also
like
start
it
locally
and
show
you
some
like
specific
types
like
how
to
implement
how
to
support
like
parameters
in
the
in
the
template
or
how?
Actually
it
works
that
once
you
run
it
through
the
generator,
you
can
actually
access
some
like
a
channel
name
in
the
template.
Like
would
you
expect
this
from.
B
I
I
was
not
sure
how
to
run
it
or
district
like
say,
for
example,
the
website
repository
we
know
like
npm
run
bill
opens
up
the
website
in
three
thousand
poll.
That
way
we
can
write
the
code
and
test
it
and
see.
Okay.
This
is
the
output
coming,
but
I
don't
find
any
any
such
file
here,
so
I
was
not
sure
how
to
get
get
started.
Also
like
what
is
the
first
command,
I
should
start
with
after
npm
install.
A
Yeah,
so
let
me
I
mean
I
think
we
have
like.
We
have
30
minutes,
so
I
can.
I
can
do
it
from
the
from
the
ground
up
and
show
it
to
you
so
yeah.
Let
me
let
me
first
give
me
a
sec.
I
will
stop
sharing
and
I
have
to
double
check.
D
A
C
B
Yeah
vs.
A
A
Okay
cool,
so
if,
if
at
some
point,
do
you
think
it's
it
would
be
better
to
like
make
it
larger
than
just
let
me
know
so:
yeah,
it's
spring
template.
Let
me.
A
Update
it,
okay,
cool
so
first
things:
first,
like
start
it
so
like
as
you
as
I
can.
As
I
can
see,
there's
no
like
so
this
template.
Definitely
it
has
no
tests
right
yeah,
because
yeah
because
of
the
legacy
it
has.
A
Yeah
and
that's
definitely
something
to
to
fix,
I
can
I
can
help
out,
if
you're,
for
example,
planning
to
rewrite
it
to
react
first,
we
can
do
it
this
way
that
first
we
set
up
tests
to
that
will
test
the
output
and
then
one
once
you
start
rewriting,
you
can
always
test
if
the
output
did
not
change,
so
that's
not
complicated
to
add
we
did
it
in
the
we
did
it
already
in
few
templates.
A
A
So
definitely
first
thing
to
improve
in
the
template
is
to
get
this
example,
that
is
in
the
readme.
A
Better
have
it
in
a
file
that
is
super
easy
to
use,
so,
let's
maybe
I'll
open
the
apr
after
the
stream.
So
let
me
just
get
a
branch.
D
A
C
A
A
So
the
yeah
I
copied
it
correctly,
so
we
know
that.
A
Template
it's
a
it's
a
correct
asking
api
file.
Yay
next
thing.
F
A
A
A
Now
we
definitely
in
the
readme.
A
And
I'm
not
gonna
be
super,
let
me
not
or
actually
like
whatever
so
like
you
first
of
all
need
to
have
generator
installed
right.
So
that's
that's!
That's
requirement
number
one.
So
prerequisite.
A
A
Which
will
be
npm
install.
F
A
A
A
A
So
I
basically
point
to
the
template
in
which
I
am
right
and,
and
I
need
to
specify
output.
D
A
Actually,
we
can
check
it
templates,
for
generator
templates,
have
everything
here
so
template
for
generator
templates.
A
A
A
Oh,
it
didn't,
which
is
perfect.
Oh
yeah,
okay,
it
didn't
fail
because
I
have
the
template
installed.
Okay,
so
that
there's
there's
one
thing
more.
You
should
always
remember
like
when
npm
would
fetch
your
template
from
note
package
manager,
it
would
install
it
before
it
would
use
it
on
local
when
you,
when
you
develop.
B
Just
a
thought:
can
we
can
we
rearrange
this,
like
maybe
the
first
step
is
chrome
and
then
the
next
step
is
to
install
the
dependencies
and
then
install
the
generator.
Something
like
that.
F
That
will
be
good
yeah
for
very
first.
B
A
Actually,
it's
let's
see
the
preview,
but
markdown
is
handling
it
automatically.
A
It's
much
easier
than
to
use
one
one
one,
because
then
you
don't
have
to
reorder
okay,
so
we
have
installation
and
then
on
agenda.
A
A
A
No,
actually,
it
works
nice.
So
there
are
no
like
required
parameters,
because
sometimes
you
have
required
parameters
and
it's
it's
just
going
to
fail
so
yeah.
So,
as
you
can
see,
template
works
pretty
well
with
the
examples
at
least
now
going
back
to
the
to
the
first
mqtt.
So
when
I
run
it
as
you
can
see,
I
specify
output
output
and
basically
the
output
goes
into
output
directory
and
all
the
files
get
generated
there.
A
A
Way
of
of
doing
it,
but
I
noticed
that
there
are
actually
actually,
I
think
that
semen,
the
the
previous
contributor
he
made
sure
that
there
is
a
that
there's
some
docker
files
or
something
because
I
think
I
saw
some
this
instruction
about
docker
compose.
B
Previously
they
have
mentioned,
like
run
the
grader
gradle.good
go
to
the
maybe
inside
the
generator
file.
A
A
C
A
Yeah
pass
some
custom
custom
parameters
to
the
to
the
project,
but
the
most
important
from
the
from
the
from
the
development
point
of
view
like
like
the
debugging,
and
let
us
maybe
put
it
as
a
note
here-
we
can
copy
it.
I
think
from
template
for
templates.
A
And
yeah-
and
this
is
this-
is
like-
let's
say,
high
level
testing
high
level
high
level
debugging.
A
Basically,
this
instruction
explains
that
you
don't
have
to
run
that
you
don't
have
to
use
the
let's
say,
official
release
of
the
generator,
but
you
can
actually
clone
generator
locally
as
well
and
and
and
run
it
from
the
from
the
sources.
So
you
just
point
instead
of
ag,
you
just
point
to
the
cli
js
in
the
generator
folder
once
you
clone
it,
but
that's
that's
that's
useful!
A
Only
when
you
really
are
super
advanced
with
the
template
and
you
already
think
about
that
something
in
the
generator
lacks
some
fun,
like
generator,
lacks
some
functionality
or
some
functionality
doesn't
work
as
expected,
and
you
want
to
fix
it
in
the
generator.
A
A
So
I
don't
think
we
we
should
put
it
in
the
in
the
readme.
A
Yeah,
let's,
let's
keep
it
just
as
simple
as
it
is
now
and
the
most
important
is
these
two
flags
so.
D
A
A
A
H
A
That's
fine!
That's
fine!
No
worries,
okay!
So
let's
stop
it
because
it's
it
hank,
so
we're
gonna
introduce
a
third
flag
which
is
also
useful
debug,
which
is
console
logging,
all
the
things
that
are
happening
in
the
generator.
A
Yeah,
so
until
we
we
wait,
what
happens
so
yeah
going
back
to
the
output,
there's
no
automated
test
for
checking
the
output,
as
I
I
said
at
the
beginning,
and
what
can
be
done
with
the
project.
A
First,
before
any
any
new
features
are
added
is
the
the
tests
which
are
called
snapshot.
Tests
can
be
introduced,
so
we
we
basically
have
a
have,
a
test
that
performs
the
the
generation
of
the
output
folder
and
then
it
it
stores
a
like
a
initial
snapshot
of
the
it
starts,
the
initial
snapshot
of
the
of
the
output,
and
then
every
new
test
is
checked
against
the
snapshot.
So
basically
it
checks
if
build.gradle
is
exactly
the
same
as
in
the
snapshot
like
as
in
the
initial
snapshot.
A
So
you,
like
files,
are
checked
like
one
to
one.
A
It's
pretty
primitive
because
it's
the
easiest
to
set
up,
but
it's
like
it
gives
you
at
least
some
understanding
like
if
you're
breaking
something,
but
it's
not
the
only
test
that
should
be
here
in
the
future,
of
course
like
in
the
future.
You
would
like
to
also
probably
start
some,
maybe
the
compose
and
the
start,
the
output
application
and
see
if
it's
actually
working
and
also
like
you
would
like
to
test
the
parameters
right.
A
So
I
would
like
to
test
if
the
parameters
that
you
that
are
added
in
the
generation
modified
template
in
in
a
proper
way
like
the
output
is,
is
what
it's
expected.
So
all
of
this,
of
course,
has
to
be
added,
but
the
basic
one
snapshot
testing,
it's
the
it's
the
best
one.
Okay,
so.
A
As
we
can
see
it
all
works,
it
worked
it.
It
took
us
some
time,
first
of
all
because
of
my
poor
internet
and
the
second
one
is
because
we,
as
I
said,
we
passed
the
install
flag.
So
it
basically
reinstalls
everything
because
sometimes
you
may
you
may
just
break
something
when
when
locally
developed,
so
it's
sometimes
when
you
get
some
unexpected
results
or
suddenly
then
just
pass
the
install
flag
and
yeah.
A
A
It
will
pick
up
the
change
in
the
file
start
regeneration,
but
of
course
it's
gonna
take
longer
because
we
have
this
install
selector,
which
was
not
the
smartest
from
my
site
to
keep
it
there,
but
yeah
anyway,
you,
you
know
what
it
what
it
basically
means,
how
that
how
that
flag
works
so
yeah,
let's,
let's
just
stop
it.
A
Let's
change,
it's
picked
up,
it's
regenerated
and
you
can
see
that
in
the
output
gradle
dot
path,
the
additional
files
were
were
generated.
So
that's
basically
what
it
is
so
and
I
think
they
are
super
important
plaques
for
local
development
that
you
should
be
aware
of
so
watch
template,
debug
and-
and
you
know
what
I
think,
I'm
just
gonna.
I
think
the
best
would
be
if
I.
D
Damn
we
need
to
fix
it
so
yeah,
but
anyway,
let's.
A
Wait
we
have
it
damn
it.
I
forgot.
I
created
this
template
like
november
net
last
year.
I
think
so
I
I
just
I
just
forgot
what
I
have
there.
I
actually
have
an
example
of
readme
that
every
template
should
have,
and
I
bet
I
have
pretty
nice
nifty
development.
Yes,
that
I
could
just
copy
paste.
I
guess,
let's
see
what
it's
there.
A
A
It's
six
past
six
whoa
wow.
It
took
us
over
30
minutes.
If,
if
you
want,
we
can
like
you
have
some
questions,
I
can
answer
them
now.
We
don't
have
to
like
cut
now
and
finish
the
stream.
So
do
you
have
some
questions
or
you
prefer
now
to
to
just
digest
what
you've
learned
today
and
then
maybe
come
back
with
more
questions
next
week
or
on
this
on
slack.
A
A
Okay
cool,
so
I'm
gonna,
I'm
gonna
open
apr
with
this.
So
it's
it's!
It's
gonna
stay
like
we're.
Gonna
have
some
useful,
also
for
others
after
the
stream,
so
we're
gonna,
I'm
gonna
open
apr,
so
we
at
least
at
least
have
a
bit
more
much
better.
Read
me,
let's
say
and
and
yeah
have
a
look
play
with
it
and,
as
I
said
like,
I
think
the
best
way
would
be
that
the
first
contribution
would
be
would
be
actually
the
the
basic
snapshot
test.
A
Or
maybe
I'm
not
gonna
just
take
your
time
now
to
look
for
for
the
links,
so
basically
one
whenever
you're
ready.
You
want
to
work
on
this
test
or
just
different
thing
but
like
if
you
want
to
work
on
these
tests,
just
ping
me
and-
and
we
can
do
it
together,
like
next
stream
or
or
whenever
you
think
it's
the
best.
H
A
Awesome
awesome
and
thank
you,
john
for
for
plus
one
for
the
for
for
us
for
having
this
meeting
in
a
america's
friendly
time
zone.
So
thanks
a
lot
for
joining
folks
next
streams.
As
I
said,
we're
gonna
have
wednesday
just
join
our
slack,
how
to
contribute
channel,
and
you
can
suggest
the
topic
for
the
live
stream.