►
Description
8th of December 2021
A
Which
soon
will
change
name
but
yeah,
it's
scheduled
as
a
contributor
first
meeting.
So
it's
a
meeting
dedicated
to
folks
joining
us
in
api
or
folks
that
are
already
part
of
the
asking
api
community
and
would
like
to
contribute
to
the
project
so
we're
having
a
set
of
different
live
streams
about
different
topics,
everything
around
contributing
to
the
project,
and
it's
all
for
you
for
contributors.
A
So
you
can
join
us
questions
and
you
can
suggest
topics
that
we
should
cover
so
yeah.
That's
it
if
it
comes
to
the
intro,
especially
for
people
watching
recording,
because
at
the
beginning
of
the
stream
there
are
basically
no
people
really
watching.
So
in
the
meantime,
let
me
please
just
give
me
a
second.
I'm
gonna
copy
a
link
to
the
to
the
live
stream
on
youtube
and
because,
if
you
don't
know
we're
streaming
to
different
platforms,
twitch
twitter,
linkedin
and
youtube.
A
A
Okay,
I'm
almost
there.
A
Oh
yes,
yes,
we
we
see
people
we
so
many
people-
hello,
hey
nice,
nice
to
see
you
like,
not
that
I'm
surprised
but
anyway,
okay,
so
I
have
the
link.
I
have
the
link,
so
I'm
gonna
share
it
with
with
folks
in
our
slack.
A
So
if
you
did
not
know
yet
in
our
slack
we
have
a
how
to
contribute
channel
dedicated
to
contributors.
A
A
A
Okey-Dokey,
so
we
have
a
link
to
the
stream
shared
in
the
slack,
so
we
can
start
a
conversation.
Let's
see
in
the
chat.
A
Okay,
so
I
see
in
the
chat
that
magic
there
are
some
folks
waiting
for
you.
Yeah
yeah
definitely
ask
questions
and
in
the
meantime,
I'm
gonna
introduce
the
topic
that
we
have
for
today.
So
today
we're
gonna
talk
about
a
react
component.
A
A
So
so
yeah,
I'm
not
going
to
talk
more
about
it,
because
we
have
a
special
guest
who's
in
the
backstage
mata
urbanczyk
from
the
same
country
as
I
am
a
beautiful
poland
and
he's
a
main
maintainer
of
react
component,
and
he
will
yeah
make
some
explanation
like
basic
stuff.
You
have
to
know
about
the
project,
but
in
the
meantime,
remember
you
as
get
asked
like.
If
you
want
to
ask
questions,
feel
free
to
to
ask
so
yeah
mache
get
ready,
like
fix
your
hair.
A
I
don't
have
to
but
you're
still
young.
So
it's
it's
a
useful
for
you
to
do
it
so
yeah,
I'm
clicking
a
button
and
you're
gonna
be
visible
to
other
humans.
A
A
So
so
before
you
jump
into
the
explanation
because
like
for
others,
we
we
had
a
quick
conversation
with
with
mache
before
the
stream
like
how
we
should
start
like
what
is
the
most
important
to
for
you
to
know,
and
we
we
came
up
with
two
topics
right,
so
one
was
like
explaining
the
the
difference
between
the
branches
here,
different
the
difference
between
branches,
but
also
before
we
talk
about
differences
in
in
branches
and
playground,
etc.
A
We
have
to
explain
this
like
what
other
async
api
tools
depend
on
react
component,
so
basically
people
so
people
understand
like
if
they
want
to
contribute
to
tool
a
they
need
to
remember
that,
actually
they
have
to
make
changes
in
react
component,
because
it's
just
used
in
this
okay,
yeah.
A
Yeah
awesome
so
so
yeah
before
sorry
for
interrupting,
like
you
can
share
a
screen
if
you
want
just
so
just
let
me
know
what
you
want.
Yeah
okay
stage
is
yours,.
B
Okay,
so
from
the
second
topic,
where
exactly
we
are
using
the
react
component
at
the
moment,
and
the
main
area
is
the
place
where
exactly
we
render
the
documentation
and
at
the
moment
we
have
three
different
tools:
three
different
repositories
where
exactly
we
are
using
the
the
real
component.
The
first
one
is
the
html
template
is
exactly
the
template
that
renders
your
essence
api
document
to
desktop
the
html
markdown
yeah,
it's
a
sort
of
like
swagger
ui,.
B
So
yeah
the
html
template.
It
means
that
if
you
want
to
render
you
exactly
run
the
generator
with
the
html
template
and
then
the
generator
created
the
static
html
markup
from
the
real
component,
I
don't
want
to
focus
what
exactly
we
are
doing
under
the
hood,
because
the
people
know
that
the
react
is
the
javascript.
B
It's
exactly
the
view
library,
it's
not
the
framework
like
the
angular,
so
people
can
have
can
surprise
that
we
exactly
render
the
static
html,
but
I
don't
want
to
focus
on
that.
The
second
second
project
that
we
using
the
rear
component
is
the
playground
where
exactly
you
can
preview,
your
essentially
pa
document
in
the
browser.
So
you
can
also
edit
something
in
the
browser
editor,
and
then
you
see
the
changes
on
the
right.
Yes,
it's
exactly
the
real
component
and
the
last
one
is
the
new
repository
and
new
tool,
the
studio
it
will.
B
A
But
I
I
think
we
can
say
that,
like
among
those
three
different
projects,
people
can
forget
about
playground
right
because,
as
you
said,
like
studio
is
the
next.
A
Because,
like
I'm
not
fully
following
all
the
changes
in
the
studio
because
you're
just
like
flash
gordon
and
I'm
not
able
to
follow,
but
as
far
as
I
understand,
I
think
we're
just
missing
this
playground:
functionality
where
users
can
ask
to
get
a
zip
of
the
of
the
generated
docs
right.
So
that's
the
only
yeah.
B
B
But
if
you
want
you,
you
will
be
able
also
to
use
it
by
the
postman,
some
cool,
yes,
because
it
will
be
the
open,
open
source,
yeah,
okay,
cool,
so
that's
it
and
about
this
first
topic
about
these
branches,
because
it's
very,
very
important.
The
react
component
is
exactly
was
exactly
created
in
my
previous
job.
B
And,
after
my
switching
from
the
sap
sorry
from
sap
to
the
essence,
api
initiative,
we
decide
to
rewrite
the
component
from
the
scratch
and
we
exactly
at
the
moment,
have
two
branches:
the
master,
the
old
one,
with
this
old
styling,
alt,
rendering,
etc,
etc,
and
the
new
one.
The
next
yes,
so
if
you
want
to
contribute,
you
exactly
must
contribute
to
the
next
branch.
Yes,
first
fork.
The
repository
then
switch
to
the
next
branch
and
then
create
the
branch
from
the
next
branch.
A
Yeah
like
yeah,
but
I
can
actually
I
was
like
what
do
you
want
to
want
me
to
explain?
But
actually
I
think
that
now
we
can
just
briefly
like
explain
so
just
just
be
just
so
people
understand.
A
What's
the
difference
between
the
the
default
branch
in
the
react
component
and
the
next
branch,
because,
like
we
went
this
direction
to
have
next
branch
because
of
like
huge
styling
changes
in
the
component,
we
didn't
want
to
release
it
as
yet
another
minor
version
to
not
yeah
confuse
people
that,
like
all
suddenly
the
whole
ui
changed.
So
that's
why
we
went
with
the
next
branch
to
start
releasing
release
candidates.
A
So
you
have
to
know
that,
like
if
you're
contributing
to
master
branch,
the
default
branch
and
we
release
something,
it
goes
the
old
flow.
Let's
say
so:
it's
zero
dot
something
release
like
minor
release,
but
whenever
you
open
apr
against
the
next
branch
and
it's
merged,
then
our
workflows
produce
a
a
release
candidate
release.
A
So
if
you,
for
example,
do
npm
install
as
an
api
react
component
by
default,
npm
will
install
you
the
the
latest
stable
version
which
is
zero
dot,
something
not
release
candidates.
So
you
need
to
remember.
A
That
like
to
use
release
candidates
latest
one,
you
just
have
to
add
this
flag.
Next,
I
think
yeah,
the
next
stock
yeah,
exactly
or
or
just
a
specific
release,
kind
of
research,
yeah,
that's,
okay,
and
and
when
we
release
it,
you
don't
have
to
worry
about
like
if
html
template
depends
on
react
component
like
for
usa
contributor.
Like
do
you
have
to
do
something
like
if
it's
released
in
the
react
component?
How
do
I
have
to
manually
bump
it
in
the
html
template
or
manually
bump
it
in
in
studio?
A
Then?
Then
you
don't
have
to
because
we
also
have
this
part
automated
so
yeah.
It
might
be
confusing
that,
like
in
react
component,
we
have
released
candidates,
but
then
we
use
them
in
production.
B
Yeah
yeah,
but
it's
not
the
production
ready
for
react
application
in
this
way,
but
if
you
use
to
only
render
the
html
static
render
yes-
and
you
don't
want
to-
you-
know,
wrap
this
component
in
another
component,
etc,
etc.
So
it's
not
the
problem
at
all.
Yes,.
A
So
if
you
can
share
a
screen
and
show
this,
I
think
it
should
be
enough,
and
people
can
just
confirm
should
be
enough,
that
you
show
that
there
are
two
branches
and
what's
the
difference
in
the
naming
of
the
of
the
releases,
that
it's.
B
E
A
So
actually,
I
lied,
I'm
not
good
in
making
jokes
and
speaking
about
like
saying
jokes,
so
we
need
to
do
something
different,
any
suggestions.
B
E
B
Yeah,
as
you
can
see
in
the
releases,
we
showed
the
latest
version,
but
latest
production
ready,
not
the
release
candidates,
but
exactly
yes,
so
it's
from
the
master
or
the
main
branch
yeah.
But
if
you
go
to
the
releases,
we
should
also
see-
oh
my
god,
no,
not
this
one,
this
one,
also
something
like
that.
Yes,
the
the
version
9.00
x
25-
and
this
is
the
pro
releases
and
it's
exactly
from
the
next
branch.
Yes,
we
have
automation
in
the
master
and
the
next
branch.
B
So
if
someone
change
or
yeah,
I
mean
fix
back
or
add
some
feature
to
the
master
on
the
next
branch.
We
also
release
that
but
important
thing
that
if
we
release
the
next
branch,
we
exactly
also
release
the
html.
So
at
the
moment
the
studio,
playground
and
the
html
template
only
focus
on
the
releases
of
the
next
branches
yeah.
B
So
if
you
fix
something
in
the
master
branch,
you
don't
worry
about
because
it's
you
know
something
like
that.
I
don't
want
to
how
to
cut
that
that
you
don't
use
bad
words
because
yeah,
but
it's
not
important.
Yes
in
our
ecosystem
at
the
moment.
Only
for
the
people
that
exactly
use
use
it
in
existing
react
application.
A
A
Do
you
need
some
more
details,
but
I
guess
like
the
most
important
just
remember
like
the
flow,
is
a
bit
different
when
you
clone
the
repo,
you
just
have
to
check
out
the
next
branch.
E
And
yeah
too
long
didn't
read
here.
A
A
Wait,
no.
She
she
wrote
that,
like
some
more
into
screen
so
yeah,
I
guess
that
now,
when
you
zoomed
in,
should
be
good.
A
Okay,
yeah,
okay,
so
I
think
we
have.
We
have
this
initial
part
covered
right.
So
there
are
no
follow-up
questions
so
now
the
the
next
part.
B
B
B
B
I
will
also
talk
about
the
monorepo,
because
this
report
is
is
more
different
than
the
other
one
that
we
have
in
the
organization.
Okay,
so
everything
is
installed
and
prepared.
Okay,
so
in
the
rear
component
we
have
exactly
the
monopole.
It
means
that
inside
one
repository,
we
have
a
several
another
project
that
we
can
have
in
the
separate
repository,
but
we
decide
to
have
only
everything
in
one
place.
Why
and
because
the
react
component.
B
We
should
also
testing
but
not
testing
like
in
the
code
that
write
the
unit
test
but
also
see
the
changes.
Yes
see
the
styling
and
it's
very
very
hard
to
test.
So
we
decided
to
go
with
the
monorepo
with
two
project,
exactly
the
real
component
in
a
folder
library
and
also
with
the
playground.
We
have
also
the
web
component,
but
I
will
talk
later
about
it.
So
we
have
three
project
library,
playground
and
the
web
component
and
playground
is
only
for
the
development
purpose.
B
B
B
Sorry
I
have
yeah,
I
exactly
see
that
inside
the
playground
I
used.
The
essence.
Api
react
with
the
latest
version
of
the
next
branch.
If
I
try
to
install
the
playground
in
the
folder
of
the
playground,
I
exactly
install
from
the
npm.
Yes,
so
even
if
I
start
the
playground,
I
don't.
I
won't
see
any
changes
that
I
will
made
in
the
exactly
library
project.
That's
exactly
the
real
component
project,
so
it's
also
very
important
but
back
to
the
installation
process.
B
B
Telling
learn:
okay
learner
start
bootstrap,
all
monorepo.
Yes,
if
you
go
to
the
learner
json,
we
exactly
see
the
three
packages,
library,
playground
and
the
web
component.
It
means
that,
if
learn
a
store
bootstrapping,
it
exactly
start
installing
the
dependencies
inside
these
three
folders
and
also
vertent
learners,
try
to
simulink
the
given
packages,
not
from
the
npm
but
exactly
from
your
local
development.
B
So
she
or
he
I
don't
know
it's
a
diversion.
It's
it.
Okay,
it
yeah,
but
learn
in
the
polish
should
be
the
ship
but
okay
it.
So
it's
tried
to
simulate
exactly
the
folder
so
in
the
playground.
If
I
go,
for
example,
to
the
playground
to
the
node
modules
to
the
essence,
api
organization,
I
exactly
say
see
that
we
have
only
the
real
component
dependencies
from
this
organization,
but
we
have
this
right
arrow.
It
means
that
you
exactly
have
the
same
link
to
this
folder
yeah.
B
It's
very,
very
important
that
you
don't
fetch
from
the
npm,
but
you
exactly
use
the
local
version,
so
it's
very
important
to
install
and
bootstrapping
from
the
root
not
going
to
the
playground
and
then
starting
the
application
yeah.
It's
it's
important.
Only
for
for
developers
but
yeah,
so
if
we
exactly
start
the
booster
by
the
learner,
we
also
see
that
information
about
the
symlink,
the
packages
and
binaries
in
the
console.
D
B
B
So
we
exactly
run
everything
here.
Then
we
exactly
go
to
the
web
component.
Web
component
also
have
the
same
name,
but
I
don't
want
it
to
show
that
to
the
library
folder
and
then
bundle
the
the
difference
between
the
the
library
and
web
component
is
that
that
we
start
preparing
sorry
that
we
bundle
the
all
component
web
component
by
the
webpack,
not
only
transpile
code
from
the
typescript
to
the
javascript,
but
also
bundled
to
the
production
ready
component
yeah.
B
D
A
If
we're
going
to
next
stage,
so,
let's,
let's
summarize
like
so
important
to
remember,
react
component
repository,
it's
a
bit
different
than
the
others.
It's
it's
a
monorepo
with
multiple
projects,
but.
B
B
Illustrations
we
exactly
have
if
you
go
to
in
the
next
branch,
it's
very
important
to
development
dogs,
develop
and
guide.
You
exactly
see
all
information
about
that.
Yes,
the
project
structure.
You
can
also
read
that
before
the
fifth
contributing
how
to
install
dependencies,
yes
to
meet
our
dependencies
for
the
playground
and
and
prepare
assembly
for
the
library
you
should
npm
install.
Of
course,
sometimes
you
will
have
a
problem
with
dependencies,
because
you
know
this
is
the
node.js
and
pm.
B
If
you
install
the
new
dependency
in
the
library
you
probably
will
have,
I
don't
want
to
say
that,
but
it's
more
relevant
the
up,
so
you
should
exactly
clear
dependencies
and
start
installing
from
the
beginning,
yes,
and
also
about
the
launch
development
environment.
Yes,.
B
Okay,
okay,
so
yeah.
So
if
you
want
exactly
start
contributing,
if
you
exactly
is
have
installed
the
dependencies
all
packages
in
all
projects
in
monorepo,
you
can
start
exactly
the
whole
project.
Npm
run
start.
Yes,
as
you
can
see,
okay,
I
guess
the
learner
clear
for
the
children
yeah
to
learn
what
exactly
we
see.
B
We
exactly
see
some
some
info
from
the
every
package
that
we
have
here,
because
learner
not
only
installed
the
packages
but
also
I
can
exact
some
the
npm
script,
not
only
the
npm,
but
also
the
batch
script
in
parallel.
Yes,
so
in
every
project
in
this
mono
repo
we
have
defined
the
npm
run,
bundle
built
or
start
something
like
that-
probably
start
and,
for
example,
in
the
ascent
api
web
component.
It
means
that
if
you
change
something
in
the
web
component,
you
exactly
start
to
build
that
project.
B
If
you
change
something
in
the
rear
component,
you
exactly
start
transpiling
typescript
code
to
the
javascript
contest
that
playground
can
use
and
show
your
new
component
and
in
the
playground
we
exactly
see.
The
output
from
the
crate
react
app
because
we
use
the
create
reaccup
environment
to
to
to
set
up
everything,
and
we
have
also
information
that
the
the
playground
is
on
the
local
33
000.
B
Yes,
if
we
go
to
that
yeah
and
we
see
exactly
the
the
playground,
so
I
will
focus
here
and
that's
it
yeah,
so
how
to
start
contributing,
and
for
example,
in
that
case,
you
wanna
add
something
to
the
real
component.
Yes,
you
find
some
back
or
you
want
to
add
new
field
that
we
don't
render,
but
you
want
to
render
it,
but
at
the
moment
we
probably
don't
render
the
discriminator
the
the
other
case
we
render.
B
But,
for
example,
you
exactly
find
some
values,
so
you
should
go
to
the
library
source
and
you
see
the
structure.
Yes,
the
most
important
part
is
the
components
and
the
containers,
the
difference
between
the
containers
and
components.
That
component
is
a
sum
helper,
some
helper
rear
component
that
we
use
in
several
places,
but
containers
has
this
choker
that
exactly
has
the
essence
api
document.
B
So,
in
the
essence,
api
document
you
have
the
info
object
and
you
exactly
have
the
info
component
for
that
to
render
only
the
info
object.
You
have
something
like
the
operation,
the
channels
yes
and
inside
the
channels
operation.
So
for
that
we
have
also
the
separate
component
only
for
rendered
operation,
the
same
for
the
messages
schemas
and
the
servers
yeah,
so
yeah
and
s
essence.
Api
containers
is
exactly
the
you
know,
one
component.
That
is
exactly
the
main
component
to
render
everything.
B
Yes,
above
one
so
yeah,
you
find
some
error,
for
example,
in
the
info
object.
Yes,
you
go
to
the
info
takes
ex
the
sx.
B
I
don't
focus
exactly
how
it
works,
because
if
you
want
to
contribute
to
the
riak,
you
should
exactly
have
a
basic
knowledge
of
the
javascript.
They
react,
but
they
react
with
the
rear
cooks.
It's
very
important
because
we
exactly
use
the
react
hooks
in
the
several
places
yeah
and
you
find
some
bug,
but
in
that
case
I
only
write
something
so
I
I've
write
only
in
in
the
purpose
of
this
meeting
on
this
recording,
so
I've
write,
I
changed
exactly
some
code
inside
the
info
object.
Yes,
you
like
it.
B
In
the
previous
job,
we
have
something
like
the
micro
frontends.
B
How
do
you
find
micro
front
ends
and
my
microphone
and
application?
B
So
the
learner
helps
us
a
lot
for
that,
yes
to
install
dependencies
and
then
also
the
setup
to
start
exactly
the
the
each
project,
so
yeah,
okay,
yeah,
it's
a
answer
for
the
dave
question.
A
D
A
B
I
want
talking
about
the
deluge:
don't
worry,
yeah,
okay,
so,
as
you
can
see,
I
exactly
make
the
changes
in
the
info
object
and
if
we
go
to
the
yeah,
we
exactly
also
see
that
the
learner
I
mean
the
learner
or
typescript,
don't
see
any
errors.
B
A
Basically,
npm
run
start.
You
get
the
into
the
watch
mode
of
the
playground
yeah,
which
is
one
of
the
projects
in
the
monorepo
and
whatever
you
code,
you
can
always
live
view.
The
preview
of
the
of
the
changes.
B
A
So
so
just
a
message
for
others
like
if
you
want
him
to
talk
more
about.
A
A
A
Remember
how
to
start
the
playground
how
to
develop.
So
that's
all
what
was
already
shown.
How
about
tests
did
you
cover
that
yeah?
We
have
some
tests.
B
Mainly
in
the
helpers,
because
we
have
something
like
the
two
parts,
the
rendering
part
and
some
helpers
and
inside
and
the
each
helper
is
exactly
the
the
the
class
with
the
static
methods
that
we
use
exactly
inside
the
component.
B
B
B
B
A
Oh
yeah,
we
have
mocha,
I
think,
in
into
repos,
I
think
in
parser
js,
but
it's
because
it's
old
but
yeah
and
important
like
why
I
wanted
machi
to
show
tests
like
because,
like
remember
like
in
the
workflows
that
we
have
set
up
for
the
organization,
for
example,
when
you
you
have
you're
used
to
working
on
a
pull
request
that
you
like,
for
example,
create
a
draft
pull
request
first
and
then
iterate
on
the
pull
request
a
few
times.
So
just
remember
that
we
are
not
running
tests
on
on
draft
prs.
A
So,
if
you're
working
on
a
draft
pr
you're
gonna
get
feedback
from
ci
that
your
tests
are
failing
pretty
late.
So
just
remember
like
run
those
tests
locally,
and
so
we
have
unit
tests,
integration
tests,
but
also
remember,
like
this
manual
check
of
of
the
work
using
the
playground
and
and
yeah
something
important.
I
don't
think
you
mentioned,
but
it's
also
important
to
highlight:
don't
remember
if
we
have
it
in
the
component
development
guide.
No,
no!
Like
the
web
components.
It's
it's.
I
think
it's
a
technical
detail
like
yeah,
but.
A
Cool
yeah,
I
just
wanted
to
say
like
that,
when
you
contribute
like,
for
example,
something
more
sophisticated
than
what
mache
showed
like
with
some
text.
But
let's
say
you
want
to
add
support
for
some
new.
A
Some
new
part
of
the
spec
then
remember
that
we
have
some
samples
that
we
have
here
repo
and
they
always
should
be
also
extended,
like
with
the
new
use
case.
So
it's
visible
in
the
playground,
not
only
when
you
develop,
but
like
later
after
merging.
B
Mia,
if
you
exactly
want
to
add
something
new
that
test
your
changes
inside
the
rear
component,
exactly
to
render
the
new
part
in
the
playground
we
have
in
the
playground
in
the
source,
specs
folder,
exactly
the
the
specification
from
the
examples
from
the
specification
repository
but
written
in
the
typescript.
Yes,
it's
a
normal
string,
but
yeah.
We
must
read
that
inside
the
javascript
project.
B
Yeah
and
also
about
the
web
component
yeah,
because
the
web
component
is
exactly
the
contribution
from
the
the
people,
not
the
people
from
the
community
because
they
wanna
to
render
the
all
real
component
inside
the
angular
application,
so
yeah
they
contribute,
and
the
web
component
is
a
very,
very
simple
wrapper
to
use
the
real
component
as
the
web
component.
Yes,
so
if
you
want
to
use
exactly
the
web
components,
you
have
also
the
documentation
for
that
also
in
the
readme,
as
I
remember
not
not
not
in
the
rhythm
but
yeah
in
dogs
usage.
B
So
at
the
moment
we
exactly
support
that
framework
library
that
you
can
that
you
can
render
and
use
our
react
component
in
angular
2,
not
not
the
first
version,
but
two
to
plus
the
next
js
and
also
in
inside
the
view
and
as
the
web
component.
Yes,
so
if
you
decide
to
to
exactly
use
our
component
in
angular
or
in
the
view
you
should
go,
you
should
use
the
web
component
and
also
we
have
something
like
the
standalone
bundle.
D
B
But
it's
very
similar
to
a
component,
but
you
exactly
operate
on
the
references
on
the
rear
component,
not
on
the
web
component.
Is
it's
complicated,
but
you
have
also
possibly
to
do
that.
A
So
we
still
have
15
minutes
left.
So
if
you
have
some
questions
or
you'd
like
to
jump
into
a
live
stream
with
us,
just
feel
free
to
ask
them.
A
A
B
C
A
B
A
A
Oh,
my
god,
that's
that's
nice!
So
I
think
when
we
see
the
drop
it's
when
the
old
project,
we
worked
for
probably
stopped
using
it,
because
there
was
a
lot
of
ci
involved
in
this
project,
so
might
be
yeah
but
yeah.
It's
cool.
B
A
Yeah
but
then
like
okay,
it's
a
topic
for
different
conversation,
but,
like
might
be
because,
like
not
sure,
if
you
noticed
like
recently
these
workflows,
they
are
like,
especially
when
we
are
updating,
workflows.
The
ci
slows
down
like
hell,
and
I
was
thinking
like.
Maybe
we
should
start
really
introduce
start
to
introduce
the
the
caching
in
the
workflows,
so
they
don't
download
all
the
dependencies
with
every
run,
but
just
take
it
from
the
cache.
I
think
it's
it's
pretty
nicely
handled
already
in
github
actions,
something
to
explore,
because
we
need.
A
Because,
like
two
days
ago,
I
added
because
I
I
think
we're
just
still
learning
github
actions
like
sometimes
we
had
some
ifs
in
the
in
between
jobs
in
the
in
between
steps,
while
in
fact
we
should
actually
have
them
on
the
job
level,
so
the
job
is
not
even
triggered.
So
we
have
like
there's
a
place
to
improve
for
sure
that
some
like
to
just
stop
some
workflows
in
some
conditions,
but
the
other
one
is
start
using
cash.
A
I
guess,
but
anyway,
we
will
never
be
sure
where
the
numbers
are
coming
from.
We
know
that
people
use
it.
We
used
it
at
sap
before
we
have
folks
from
backstage
using
it
for
very
long.
B
B
A
B
A
A
Okay,
so
any
other
questions,
because
if
they're
not-
and
I
think
we
ex
like-
we
really
covered
everything-
actually
magic
covered,
pretty
much
everything
how
about
like?
Oh,
maybe
that's
actually
that's
something.
A
A
But
yeah,
so
I
I
think
that
important
question
as
well
from
the
contributor
side
would
be
come
on.
Jonas,
don't
be,
don't
be
a
typical
developer
like
open
your
mind,
you
do
it
for
others,
not
because
you
have
to
so.
The
the
question
is
like
because,
as
like,
maybe
others
understood
already
when
I
said
like
your
fresh
garden
and
like
there's
a
lot
of
there
are
many
changes
happening.
A
No,
I'm
not
sure
how
to
phrase
the
question
like
so.
Do
you
think
it's
the
right
moment
to
actually
push
anything
into
the
next
or
rather
hold
on
with
bigger
changes,
because
of
something.
B
B
B
So
long
to
release
the
major
version,
because
we
want
to
introduce
also
the
another
styling
but
yeah.
We
wait
also
for
designer
few
months,
so
yeah
better
to
go
to
to
the
next
better
to
go
to
the
major
version
and
then
to
this
next.
Second
major
version
change,
styling
again
yeah,
as
I
remember
also
the
backstage-
can
have
this
problem
because
they
go
with
the
next
branch,
the
next
releases
and
also
add
the
dark
team.
So
yeah
it
can
be
a
problem
for
the
factory
people.
C
A
B
Yeah,
we
have
also
the
idea
of
the
plugins
to
the
component
that
you,
for
example,
can
change
rendering
of
the
given
section.
Something
like
that.
You
have
some
extension
for
the
info
object.
Yes,
I
don't
know,
maybe
the
x
twitter,
that
you
have
the
account
of
the
excluder
and
at
the
moment
we
render
that
the
plane
playing
values
as
the
key
value,
but
someone
maybe
can
render
it
as
the
new
component.
B
Yes,
the
new
rear
component
with
with
the
link
exactly
so
we
have
also
the
idea
of
such
a
plugin
is
that
you
can
change
exactly
the
the
given
section,
not
only
the
styling,
but
exactly
will
component
from
the
plugin
perspective
yeah.
So
it
will
also
introduce
the
breaking
chain.
So
we
so
we
should
go
with
the
first
major
version
and
then
make
the
next
version
after.
A
A
So
so
basically
mind
switches
off
and
does
whatever
it
just
goes
with
the
flow,
and
this
question
might
be.
I
think
the
answer
might
be
interesting.
So
basically,
how
did
you
figure
out
the
outline
of
what
we,
what
you
wrote
and
the
content
you
taught
the
community
needs
like
so
basically
how
we
came
up
with
the
content
that
we
already
have
in
the
in
the
tool
like
what
draw
like
what
was
the
driver
here.
A
Of
the
of
like
of
the
quality
of
the
amount
of
the
documentation
that
we
have
in
the
project
like
because,
like
you
know
what
I
said,
it's
one
of
the
best
documented
projects
from
the
developer
perspective,
at
least
in
my
opinion-
and
I
guess
alejandra
is
asking
or
just
throwing
questions
to
help
us
out
to
have
some
questions
but
yeah
asking
like
how
did
we
end
up
with
what
we
have?
I
I.
B
Cannot
end
up
yeah,
I
remember
that
some
people
went
to
render
inside
the
angular
or
one
person
also
in
the
view,
so
I
decided
to
write
that
documentation.
Also
in
the
nxjs
we,
we
have
probably
five
people
that
want
to
render
exactly
the
the
the
component
in
the
energies
project.
B
We
have
some
problems
because
the
people
who
don't
know
about
how
the
setup,
because
it's
a
really
big
component
in
opposite
to
the
another
one
in
the
ecosystem,
something
like
that.
You
know
the
redox
or
the
swagger-
it's
a
very
big
component
to
render
yes,
so
I
decided
to
write
the
documentation
for
an
xjs
view,
angular
and
that's
it.
So
it's
this.
This
documentation
is
exactly
from
the
developer
perspective
or
the
usage
perspective,
not
something
that
yeah.
A
But
I
think
we
can
also
share.
Do
we
have
time?
Oh
my
god,
time
finished
so
interesting,
throw
in
from
my
side
because
I'm
I'm
not
hiding
it.
I
hate
scrum
and
agile.
A
I
don't
want
to
go
into
details,
it's
just
a
statement,
but
but
one
good
thing
about
it,
I
think-
and
that
was
one
of
the
drivers
for
good
documentation
here-
was
that
the
project,
as
at
the
very
beginning
of
this
live
stream.
Magic
said
that
it
was
developed
in
in
an
in
sap
before
and
it
was
basically
developed
like
then
it
was
developed
under
asking
api
organization,
but
it
was
developed
like
fully
maintained
only
by
by
sap,
and
it
was.
It
was
fully
maintained
by
a
scrum
team
at
sap.
A
So
so
you
know
how
instagram
works,
like
everything
assumes
that
everything
everybody
should
know
everything
and
it's
not
sarcasm,
okay,
it's
sarcasm,
but
yeah
anyway.
I
think
that
people
assume
that
everyone
should
be
at
the
same
page.
Everyone
should
be
able
to
understand
the
project
and
contribute
to
it,
and
I
think
that
was
the
driver
like
we
were.
We
had
many
developers
in
the
team
and
we
had
to
have.
D
A
Carolina
and
were
pushing
a
lot
as
well
for
it,
so
it
was,
but
anyway,
like
it
doesn't
matter.
If
I
like
scrum
or
not,
if
it
was,
it
was
a
scram
team
or
not,
but
I
think
it's
everything
was
basically
driven
by
the
need
of
of
other
developers.
B
A
B
A
Definitely
and
thank
you
machi
for
taking
time
joining
me
and
others
on
this
live
stream.
I
hope.
A
It
and
yes,
stay
tuned
with
us
on
the
next
live
streams
for
sure
one
live
stream
will
happen
next
week.
Don't
know
yet
about
around
christmas.
Probably.
A
A
Let
us
know
what
you
want
us
to
talk
about
because,
as
I
said
at
the
beginning,
these
live
streams
are
for
contributors
and
we're
basically
like
we
talked
today
about
react
component
because
we
had
a
explicit
request
about
it
from
the
community
so
yeah.
Let
us
know
next
week,
there's
gonna
be
live
stream
and
yeah
again,
I'm
not
sure
how
it's
gonna
be
around
christmas,
but
yeah
just
stay
tuned.