►
From YouTube: Community Meeting - July 26 2022
Description
A
Good
good
good
afternoon
and
welcome
to
asking
api
community
meeting
just
before
we
usually
we
started
as
usual.
Oh
no,
I'm
stressed
missy
okay,
so
we,
the
live
stream,
is
just
started
before
we.
We
continue.
Remember
it's
a
live
stream,
so
you
don't
have
to
join,
live
with
us
on
zoom.
You
can
also
join
us
on
one
of
the
social
medias
that
we
share
the
live
stream
and
if
it
comes
to
interacting
with
us
through
chat,
we
only
listen
to
the
chat
on
the
live
chat
on
youtube.
A
Yeah
and
it's
community
meeting
so
welcome
everyone
before
we
jump
into
a
usual
agenda,
can
do
you
have
something
that
you'd
like
to
mention
first,
because
you're
rushing
for
another
meeting,
that's
totally
fine!
If
you
want
to
do
it.
A
Okay,
perfect,
so
yeah.
Let
me
look
on
the
agenda,
so
the
one.
The
first
topic
is
something
that
I'd
like
to
highlight
to
everyone.
I'm
gonna
send
a
link,
so
you
know
async
api
specification
is
released
on
a
schedule
that
we
agreed
with
the
community.
A
The
last
release
was
in
april
and
then
the
release
from
june.
A
We
skipped
it
because
there
was
nothing
to
release
which
made
sense
to
not
release
and
and
now
the
next
release
window
is
september,
and
there
are
some
items
that
I
think
will
be
released
so
far
as
I
remember
so
as
far
as
I
remember
so,
let
me
share
the
link
in
a
live
chat
and
also
in
youtube
and
also
in
in
zoom.
So
please,
if
you'd
like
to
be
a
release
coordinator
for
that
release.
Please
yeah
join
this
discussion
that
sergio
started
release
coordination.
Is
I
mean
it's
not
easy?
A
Liking
knocking
different
doors,
but
the
what
you
get
in
exchange,
you're
learning
like
the
whole
process,
you're
understanding,
actually
how
spec
is
being
released
from
the
technical
point
of
view
and
also
soft.
B
Oh
lucas,
you,
like
you
like,
stop
you
froze
for
a
second
there.
A
But
am
I
like:
I'm
stopped
and
you're
losing
some
context
or
you're.
You
can
actually
listen.
Everything.
A
So
what
I
was
saying
is
that
if
you
become
a
release
coordinator
like
damn
it,
it's
not
my
day
today.
So
when
you
become
a
release
coordinator,
you
learn
not
only
in
practice
how
technically
we
do
the
release?
What
are
the
like?
What
are
the
prerequisites?
What
are
the
crucial
dependencies?
A
So
you
really
understand
how
complex
the
process
is,
but
you
also
understand
how
it
looks
like
from
the
practical
point
of
view
like
the
whole
process
like
who
you
talk
to,
who
is
responsible
for
what
part
of
the
spec,
so
it
helps.
You
learn,
really
async
api
in
details.
So
that's
why
I
definitely
recommend.
Oh,
so
I
was
talking
talking
and
I
already
saw
a
comment
in
in
youtube,
so
tabak
wrote
I
would
love
to
be
one
of
the
release
coordinator,
which
is
awesome.
A
Just
please
go
into
the
discussion
that
I
linked
in
the
in
the
chat
mentioned
there
that
you'd
like
to
do
it
and
not
sure.
What's
because
it's
sergio
started
the
the
discussion,
but
we
already
had
three
release
coordinators
before
it
was
me
sergio
and
and
dale,
so
we
will
for
sure
support
so
yeah.
Thank
you.
A
Wow
first
item
on
the
agenda:
gone
done.
I
mean
yeah,
the
the
next
one.
Do
you
like
or
actually
actually
there's?
No
there's
just
one
there's,
no
next
one,
so
I'm
rather
open
for
questions
like
because
I
did
not
plan,
for
example,
to
do
the
update
on
the
asking
api
conference
organization,
but
because
I'm
not
sure
how
many,
how
much
people
follow
the
to-do
discussion
that
we
have
do
you
like?
A
That
sounds
like
yes,
no,
maybe
better
do
it.
So,
let's
let
me
just
share
some
links
at
the
moment
if
it
comes
to
conference
organizations.
So
of
course
we
do
everything
like
all
the
discussions
we
do
them
in
public
on
github
on
community
repo.
We
also
have
a
separate
checkup
meeting
every
two
weeks
and
this
week
is
another
one
on
on
thursday.
A
Final
extension
went
to
linux,
request
went
to
linux
foundation,
so
we
will
wait
until
the
second
week
of
august
and
that's
the
final
deadline,
because
then
we
need
people
that
will
review
and
then
this
work
on
the
schedule
would
be
awesome
to
complete
it
before
the
end
of
august.
A
I
don't
have
access
to
the
information
like
real
time
to
see
how
many
cfps
we
have.
So
I
can
just
show
you
that
wednesday,
tuesday
or
wednesday
like
or
actually
no
actually
thursday,
I
think
it
was
thursday.
A
Last
week
I
got
email
from
from
linux
foundation
with
the
list
and
there
were
already
13
proposals
submitted,
but
I
also
know
that
already
few
people
submitted
because
some
people
do
write
to
me
to
ask
for
the
process.
That's
why?
Actually
I'm
not
gonna
do
the
review
of
the
call
for
papers
like
last
year
because
yeah
I
advise
people
too
often,
so
I'm
I'm
too
biased.
A
So
that's
if
it
comes
to
cfp,
where
we
are
at
now
currently
also
alejandra
she's,
coordinating
the
topic
of
actually
finding
volunteers
to
do
the
review
of
the
proposals
and
then
work
on
the
schedule.
So
I'm
gonna
send
you
a
link
to
a
dedicated
discussion
about
where
you
can
volunteer.
If
you
want
to
help
with
review
of
of
the
proposals.
A
And
most
important
is
the
update
I
think
from
today
from
bc
that
went
to
the
conference
website.
Do
you
want
to
show
it?
You
see.
D
B
B
Okay,
so
I
was
kind
of
messing
with
like
a
little
bit
of
an
art
direction
for
the
conference,
and
this
is
like
in
the
web
in
the
form
of
a
website
right
now,
but
I
feel
like
we
can
use
the
same
kind
of
art
direction
across
like
any
other
assets
that
we
need
for
the
conference
this
year.
So
it's
just
like
kind
of
just
a
prototype
of
what
like
I
was
kind
of
messing
around
with
just
like
you
know
straight
up
like
this
is
what
we're
doing.
B
We
can
get
more
info,
and
this
would
probably
like
scroll
down
here,
but
there's
like
a
little
illustration
here
that
I
put
together
that
I
think
fits
with
the
brand,
but
could
be
a
good
like
visual
thing
to,
like
you
know,
use
in
a
bunch
of
the
conference
stuff,
yeah.
Here's
just
some
information
like
what
the
conference
is.
B
I
just
kind
of
came
up
with
any
kind
of
writing,
but
we
can
edit
that,
as
we
need
to
a
link
to
the
website,
here's
to
apply
to
be
a
speaker
and
to
submit
a
proposal
and
then
oops.
This
is
not
refreshed
one
second
and
then
here's
to
sign
up
for
updates.
I
don't
know
if
we
have
plans
to
like
send
people
updates
on
a
mailing
list,
but
I
assumed
that
it
would
be
better
just
to
grab
email
addresses
anyways
in
case
we
wanted
to
do
that.
B
So
that's
my
email
and
then
subscribe.
This
is
a
place
where
I
would
think
that
you
know
our
sponsors
could
go.
I
think,
instead
of
like
separating
them,
like
you
know,
platinum
and
gold's.
Here,
like
we
just
make
the
platinum
ones
bigger
and
then
you
know
put
the
other
ones
below
it
kind
of
like
in
a
hierarchy
sense.
So
you
visually
know.
What's
you
know
who's?
B
B
Yeah
yeah,
there
are
a
few
other
ones,
but
these
I
just
kind
of
repeated
just
for
visual
sake,
but
I'm
sure
we
can
pop
in
whatever
we
need
to
button
to
become
a
sponsor,
which
I
guess
would
link
out
to
a
separate
thing.
I
think
we
have
like
a
form
for
that
somewhere
else,
and
then
I
thought
it
was.
B
It
would
be
a
cool
thing
to
show
some
of
the
past
recordings
from
last
year,
since
we
did
release
all
of
them
slowly
over
time,
and
here's
like
some
buttons
that
you
can
use
just
to
you
know,
go
right
to
the
videos
on
youtube.
B
It's
in
like
a
little
slider,
so
we
can
add
as
many
as
we
want
there
and
yeah.
Then
just
the
footer.
We
can
put
some
links
here
if
we
want
to
and
then
just
that
button
again
to
add
the
event
to
your
calendar
and
then
some
social
media
links
so
yeah.
That's
basically
the
direction
I
have
for
the
website
as
of
right
now,
but
I
think
like
with
this,
we
can
like
always
add
more
to
it.
B
If
we
over
time,
like
figure
out
more
things
like
I
know,
we
still
need
to
figure
out
like
the
schedule
and
we're
not
sure
how
we're
going
to
implement
that
schedule.
Yet,
but
yeah
so.
D
B
A
So
yeah
the
submission
form.
It's
awesome
to
have
it
there
because
yeah
we
oh
yeah,
like
that's,
that's
how
we
started
and
we
should
continue
like
we
already
collected
emails
from
people
that
were
interested
and
voted
on
like
where
we
should
conference,
so
we
will
definitely
send
updates
to
them,
but
so
with
future
websites
like
this,
that
we
should
always
have
this
kind
of
subscribe
call
out.
A
A
The
illustration
do
I
get
it
right
that
it's
because
even
driven
architecture,
so
it's
like
an
architectural
stuff.
That's
why
there
are
stairs
and
different
items.
B
Yeah
yeah,
that's
exactly
right!
Oh
I
yeah.
I
guess
I
also
forgot
to
give
some
explanation
of
my
creativity
for
that
one.
Second,
I
can't
multitask
it's
something
that
I'm
really
bad
at
I'm
trying
to
work
on.
B
Let's
see
so
I
don't
know
if
you
guys
know
what
like
barcelona
looks
like,
but
it's
like
very
gritted
like
this,
like
all
the
streets
that
are
very
like
square
and
gridded
and
yeah,
so
that
was
kind
of
like
the
initial
inspiration
behind
the
illustration.
But
then
I
was
like
oh,
how
can
we
make
it
look
like
event
driven
architectures
and,
like
you
know,
but
it's
still
so
abstract
that
you
could
like
do
anything
with
it,
but
yeah.
I
had
fun
making
that
one
for
sure.
B
A
B
B
Yeah,
so
I
I
added
in
the
zoom
chat
a
link
to
the
issue.
If
you
want
to
leave
feedback
there,
I
don't
know,
can
you
share
that
in
the
youtube
chat,
lucas.
A
So
so
yeah
the
website
is
in
progress.
Cfp
is
in
progress.
Venue
like
the
last
memo
I
got
from
linux
foundation
was
that
this
week
we
should
get
answers
from
all
the
different
venues
if
they're
available
and
what's
the
price.
A
I
really
hope
it's
gonna
happen
this
week
because,
like
it's
kind
of
blocking
us
to
decide
how
much
we
should
charge
sponsors
for
sponsoring
how
much
money
we
need,
otherwise
we're
gonna
improvise
and
just
ask
more
than
we
would
so
that's
if
it
comes
to
the
conference.
Any
specific
questions
from
anyone.
A
Okay,
so
regarding
other
community
activities,
so
asking
api
mentorship
yeah
not
much
to
share
really
it's
just
running
now
I'll
ask
like,
in
the
future
I'll
I'll
ask
from
time
to
time
ace
if
he
can
share
some
updates,
because
now
it's
fully
under
ace
wings
yeah.
A
Yeah
it's
under
his
wing
now
and
so
I'll
ask
him
if
he
can
share
some
updates
in
a
month
or
so.
A
If
it
comes
to
ambassador
program
now
there
was
final
polish
by
done
by
barbano.
Yesterday,
I
think,
or
today
so
it's
yeah,
it's
almost
almost
not
merged.
Actually
it's
almost
submitted
for
voting
of
tsc.
B
B
She's
in
the
process
of
getting
pricing
for
the
ambassador
swag
as
well,
the
t-shirt
design
with
the
community
gardeners
so.
A
Oh
yeah,
because
there's
this
depending
on
the
color
details,
right,
yeah,
yeah,.
B
A
So
yeah
so
swag
store
is
also
super
advanced
so
but
yeah
it's
we're
never
committing
to
any
date.
So
we're
not
going
to
say
when
it's
ready,
especially
that
it
also
has
to
be
submitted
for
voting
of
dsc,
because
that's
expensive
and
by
the
way
barbara
is
listening
in
the
background
and
she
wrote
a
comment
that
she
loves
your
design
missing.
A
Okay,
so
that
would
be
it
from
my
side
if
it
comes
to
different
activities.
Most
important
is
that
in
two
weeks,
you're
not
gonna,
see
my
face.
Finally,
so
I'm
next
next
two
weeks,
I'm
out
on
holidays,
if
there's
anyone
watching
this
recording
and
is
in,
is
based
in
ireland,
let's
sing
because
I'm
gonna
be
in
ireland,
so
maybe
we
can
exchange
a
few
beers
and
so
in
two
weeks
the
meeting
will
be
still
hosted
again
morning.
Time
for
emea.
A
That's
how
we
say
it
right.
Yes,
you
know
what
I
mean
like
india,
like
europe,
middle
east
africa,
in
the
abbreviation,
oh.
A
I
think
that's
this
abbreviation
right.
Can
you
see
in
the
chat.
A
Yeah
so
yeah
morning
in
the
morning
of
morning
for
emea,
emma
jesus
and
ace.
B
B
I'm
not
sure
if
anybody
saw
this
in
the
issue,
but
I
like
posted
a
video
explaining
kind
of
like
the
idea
behind
it,
but
essentially
like
the
context.
I
guess
is
that
I
don't
know
if
anybody's
seen,
like
the
output
of
the
payload
on
the
async
api
studio
or
using
the
async
or
the
html
template
generator,
but
I
think
that
there's
a
huge
problem
with
like
just
how
it
is
visually
getting
outputted.
B
I
think
it
like
could
get
pretty
confusing,
so
we're
just
trying
to
come
up
with
a
new
idea
on
how
to
structure
it.
So
this
is
kind
of
like
an
idea
that
I
have
where
things
are
more
rendered
like
in
line.
So
it's
easier
to
see
everything
of
the
payload
structure
and
then
we
go
to
the
so.
This
is
like
the
prototype,
but,
and
then
you'll
see
like
this
little
underline
of
the
type
of
what
item
line.
B
I
don't
know
how
to
what
the
technical
term
is
for
that,
but
but
when
you
hover
it'll
give
you
like
an
info
window
of
what
format
it
should
be
in,
and
this
could
include
other
things
like
if
you
need
to
define
like
a
certain
set
of
values
like
if
it
were
a
number
from
like
0
to
100,
for
example,
it
would,
it
could
show
up
underneath
that
format
as
well
in
the
same
window.
If
that's
what
we
needed
to
do.
B
So,
that's
like
an
idea
to
kind
of
limit,
or
just
like
visually,
deliver
that
information
like
a
little
bit
more
easily.
I
guess
and
then,
as
far
as
like
objects
goes,
I
have
this
idea
of
like
having
like
a
well.
We
already
kind
of
have
this
where
it
like
toggles
down,
but
I
think
that
having
all
of
the
items
in
line
like
somewhat
makes
it
like
a
little
bit
easier
to
read.
B
B
So
my
idea
was
like
making
it
inline
like
the
most
important
information
would
be
in
line
and
then
whatever
else
needed
to
fall
below
that
would
fall
below
it
like,
for
example,
in
this
from
user
object,
we
have
a
markdown
description,
so
something
that's
like
a
little
bit
more
longer
of
a
description
would
render
in
a
block
like
this,
and
then
something
like
this
would
be
more
of
just
like
a
string
description
and
that's
kind
of
the
question
that
I
had
in
that
channel
before
lucas.
I
think
you
responded
to
it
where
I
was
like.
B
Can
you
like
check
if
it's
markdown
or
whatever,
so
that
it
would
just
conditionally
replace
it
this
way?
And
then,
when
you
expand
this
description,
it'll
render
the
markdown
for
you
in
the
component
so
yeah.
This
is
just
like
the
basic
implementation
that
I
have
and
was
going
to
iterate
on
it
more,
but
just
wanted
to
know
if
anybody
had
like
feedback
on
it.
A
So
so
question
so
because,
like
now,
we
show
format
out
of
the
box.
Now
it's
going
to
be
on
hoover.
B
B
A
I
mean
the
debatable
debatable
like
it
depends
on
the
audience
of
the
dogs
right
so
uid
from
someone
for
someone
that
is
gonna
write
code.
I
think
it
might
be
interesting,
especially
with
code
generation.
It's.
It
pays
for
really
critical
role.
C
C
C
Yeah,
so
by
default,
for
example,
the
way
that
the
current-
I
can't
actually
remember
if
it
if
it
renders
this
but,
for
example,
this
or
the
react
component
at
the
moment.
It
renders,
for
example,
additional
properties
I
allowed
and
I'm
pretty,
I'm
not
sure
magic.
Does
it
render
the
not
keywords
or
the
not
validation
rules?
Does
it
render
that
as
well
and
the
if
and
then
an
else
statement.
B
Yeah,
that's
like
a
note
that
I
got
from
fran
when
I
was
talking
to
him
about
it.
The
next
step
is
going
to
be
like
figuring
out
how
all
of
these
like
json
schema
rules
would
fit
into
like
yeah.
A
visual
like
this.
C
C
And
whatever
other
payload
scheme
is
that's
allowed,
because
the
moment
at
the
moment,
the
way
that
everything
works
is
that
the
parser
converts
all
of
the
schema
objects
or
all
of
the
schema
formats
to
json
schema.
But
it
also
means
that
you
are
displaying
maybe
incorrect
information
or
not
the
entire
information
that
that
the
user
wants.
B
D
Yeah
you
say
that
yeah
at
the
moment,
with
everything
convert
to
the
jason
scheme,
avro,
ram,
etc,
and
sometimes
it
can
be
a
problem
to
to
display
some
values.
As
I
remember,
the
avro
or
ram
parser
change.
D
C
Yeah-
and
I
also
like
that-
I
know
that
me
and
matic
talked
about
it
at
some
point
where
we
or
I
had
a
use
case
where
I
really
wanted
just
the
payload
like
design
component
in
react,
because
I
had
other
use
cases
where
I
would
love
to
just
show
the
json
schema
that
I
had
without
async
api
anywhere
near
it.
I.
C
This
means
that
if
that
could
be
completely
decoupled
from
so
basically
the
async
api
react
component,
just
installs
this
async
api
json
schema
react
component
and
uses
that
I
can
in
my
tools
or
in
my
website
I
can
use
the
same
underlying
component
and
everyone
else
that
wants
to
render
this
json
schema
can
use.
This
react
component.
B
B
A
And
then,
actually
we
had
some
inquiries
for
if
there
are
plans
to
have
the
component
that
renders
schema
as
something
that
people
can
use
directly
without
using
api
component.
A
But
that's
not
design
related
right,
it's
because
technically
we
will
go
there
right.
I
mean
in
the
end,
that's
the
plan
of
the
design
work
and
this
I
don't
remember
the
technical
term,
but
basically
that's
the
goal
to
have
a
gallery
of
components
right.
B
Well,
I
mean
yeah.
I
think
that,
like
what
jonas
is
saying
is
like
to
just
like.
Take
apart,
like
actually
create
like
a
component
like
visual
output
for
json
schema
itself
and
then
like,
we
could
use
it
in
this
payload
output.
Right.
Isn't
that
what
you're
saying?
But
we
could
also
use
it
across
like
other
projects
that
we
need
it
for,
and
I
I
could
see
that
useful
for
a
bunch
of
different
things
like
if
it's
open
source,
like
maybe
people,
would
just
use
that
in
their
own
projects,
for
whatever.
C
B
True
yeah
I
mean,
would
it
be
safe
to
say
to
like
start
with
jason
schema
and
not
like
others
or
yeah,
because,
like
you,
can't
do
everything
at
once?
So
I
would
say,
like
is
json
schema
like
the
priority
you
think
to
create
a
component
for
that.
C
B
A
Just
to
confirm
that's
the
scope
of
the
design
system
right
to
have
an
ability
like
to
have
a
set
of
components
that
I
can
combine
and
use
as
one
big
component.
I
probably
have
it
pre-configured,
but
also
I'd
like
to
have
just
a
component
that
only
displays
info
about
the
app
and
then
I
can
use
it
separately
directly.
A
B
Yeah
I
mean
I
have
this
idea
of
creating
like
so
this.
This,
like
smaller
portion
like
this
payload
like
documentation,
output,
is
part
of
like
a
larger
project,
called
that
I'm
like
calling
it
docs
ui.
B
So
I
guess
like
what
you
guys
are
saying,
with
the
json
schema
like
making
components
for
that
output
that
could
essentially
be
like
nested
within
this
and
decoupled,
like
you're
saying
I
guess
would
just
be
part
of
that
whole
docs
ui
like
project,
I'm
not
sure
though,
but
I
mean
it
would
still
be
rendered
in
like
some
kind
of
pack
or
it
would
be
created
in
some
kind
of
package,
so
that
it
would
be
easy
to
use
it
across.
D
B
But
I
mean
as
far
as
like,
like
with
jason
schema
like
aside
or
just
like,
you
know
that
kind
of
stuff.
Like
our
do
you
think
this
is
in
the
right
direction,
or
should
we,
like
you,
know
kind
of
deviate
from
this
a
little
bit
or
is
the
way
that
this
is
like,
like
offering
the
information?
Would
that
seem
useful
to
you
guys
as
developers
or
I'm
not
sure.
A
B
A
B
Container,
but
it
would
essentially
just
stack
if
needed,
or
you
know
whatever.
However
layout
we
determine,
but
I
mean
I
guess
how
complex
would
a
window
like
this
get
like
how
many
different
things
can
you
define
within
one
property?
You
know
like,
I
assume
that
it
wouldn't
get
too
hectic
like
you
would
probably
have
one
or
just
like
two
one
or
two
of
these
right.
B
Like
format
and
accepted
values
is
what
I'm,
I
guess,
I'm
saying
like
accepted
values
could
look
like
something
like
a
string
or
a
number
with
a
minimum
and
a
maximum
or
whatever.
But
then
you
could
also
add
values.
Right
is
what
you're
saying
like
there's
accepted
values
after
like
the
third
like
first
two
have
to
be
these
strings
or
something
and
then
the
third
could
be
any
string
or
any
integer
stuff
like
that.
A
Yeah
but
as
far
as
I
know,
yeah
you
would
have
two
maximum
yeah.
B
B
C
B
B
Yeah,
that's
why
I
guess
I'm
like
gonna
look
at
some
like
use
cases
and
see
how
I
can
apply
those
use
cases
to
a
design
like
this.
So
if
you
guys
have
anything
that
I
could
see
or
use
that
gets
pretty
complex,
that
would
be
great.
A
I
think
that
in
the
json
schema
community
there
was
a
discussion
where
they
at
some
point
of
time
started
collecting
the
real
life
examples.
Yes,
you
remember
like
when
they
I
think
they
were
at
least
they
planned
to
collect
example,
json
files,
and
they
were
especially
targeting
the
complex
ones.
A
So
you
can
definitely
try
to
ask
ben
from
json
schema.
Okay,
there's
also
this
hashtag
hashtag,
whatever
json
schema
channel,
name
that
we
have
on
asking
api
slack
that
is
connected
with
there
slack
so
ask
there,
because
yeah
jason
schema
can
be
super
complex.
C
C
C
D
C
B
A
B
Yeah,
I
think
I
know
like
I
was
seeing
like
the
ones
that
are
supported
currently
in
studio.
Like
the
the
cases
like
I
I
mean,
I
think
the
important
thing
is
like
obviously
we're
not
gonna
be
like
getting
every
edge
case
out
there,
like,
I
think
it
it's
important
to
like
stay
focused
on
maybe
like
the
normal
use
cases
that
we
see
all
the
time
first
and
then
we
can
start
to
like
support
edge
cases.
B
A
I
mean
the
most
important
is
to
not
have
any
regression
in
the
ui,
so
we
should
definitely
support
what
we
already
support.
B
A
D
A
I
mean
and
what
liana
said
like
we
are
not
showing
in
the
docs
I
mean.
I
think
it
actually
is
important
feature
to
show.
Okay,
we
react
component
operates
on
on
schemas,
converted
to
json
schema,
but,
like
the
user
would
like
to
see
another
schema
in
the
end
right,
so
there
should
be
in
the
future
some
button
that
they
can
click
and
see
the
original
schema.
D
A
But
from
what
I'm
looking
at
now,
when
you,
when
you're,
showing
so
and
after
the
discussion,
so
basically
what
you
want
to
do
is
like,
like
now,
we
display
everything
like
format,
information,
minimum
maximum,
like
everything
all
the
details
we
put
on
the
ui
and
you
want
to
do
minimal
ui
and
then
everything
additional
and
extra
data
should
be
on
demand.
So
you
don't
see
the
format
and
you
have
to
hover
to
see
the
format
and.
D
A
B
But
I
guess
because
they
are
interactive
components
in
the
end
like,
as
in,
like
obviously
like
if
you
print
it
on
a
page
like
on
a
piece
of
paper
like
you're,
not
gonna,
see
all
of
the
information,
but
they
like
they
are
like
interactive
components.
So
we
should
like
lean
on
some
of
these,
like
interactions
that
we
can
use
in
order
to
like
keep
everything
visually
digestible
because
I
think
that's
like.
B
Maybe
one
of
the
biggest
problems
is
because
it
can
get
very
complex
that
you
might
see
everything
all
at
once
and
it
just
like
is
like,
like
visual
overload,
what
am
I
looking
at
kind
of
thing?
So
if
we
don't
want
to
hide
things
like
this,
that's
like,
I
guess,
that's
another
discussion,
but
I'm
really
just
trying
to
like
make
sense
of
what
we
should
do,
based
on
like
what
the
needs
are
of
like
async
api
users.
C
I
think
there
can
be
different
levels
to
it
as
well.
Now
it
kind
of
depends
on
what
you
want
to
see,
but
the
problem
is
that
if
you
decide
to
not
show
something,
for
example,
if
validation
rules,
if
you're
not
show
them,
there
might
be
something
within
those
validation,
rules
that
renders
a
property
unusable.
For
example,.
C
C
You
define
that
if
there
is
this
property
then
validate
against
this,
but
there's
all
of
these
other
validation
rules
that
might
render
this
structure
unusable
or
okay,
so
that
that's
why
we
can't
see
this
structure
that
you're
showing
here
as
as
structure,
but
it
needs
to
be
shown
as
validation
like
it.
It
needs
to
validate
that.
If
I
see
this
property
then
validate
against
this
and
it's
in
it's
all,
I'm
not
gonna,
say
it's
impossible
to
to
design,
but
it's
it's
hard
to
it.
Had
it's
hard
to
explain
in
like
a
design
component.
C
B
You're
saying
that
like,
if
we
wanted
to
validate
against,
like,
for
example,
this
html
property
that
sent
wouldn't
be
shown
in
the
in
the
payload
schema
like
we
wouldn't
want
to
show
it
at
all.
In
the
in
the
payload.
D
A
No
just
nine
minutes
left
so
no
more
threats
into
discussion.
D
But
could
we
have
two
modes
for
render
the
you
know
the
additional
metadata
I
mean
with
this
tooltip
the
power
or
the
second.
B
D
D
D
D
D
D
C
D
D
B
B
B
D
B
A
D
B
Yeah
yeah
yeah.
I
I
think
I
do
remember
seeing
an
example
that
fran
was
showing
me
about
that.
A
So
in
the
meantime
see
I
will
recommend
you,
I
just
pasted
in
the
chat
this
person-
okay,
ludovic,
so
he's.
B
A
So
definitely
engage
with
him
because,
like
when
you
drop
a
message
like
not,
everyone
sees
the
messages
in
general,
but
he's
a
his
atsc
member.
That
is
like
now
maintaining
the
avro
parser
that
passes
schema
to
jason
and
but
the
most
important
is
that
he
also
contributed
to
html
template
before
it
became
the
same
as
react
component
and.
D
A
So
and
he
contributed
it
because
that
was
a
explicit
request
he
get
from
who
he
got
from
developers
as
far
as
I
remember,
because
the
so
ludovic
is
working
for
a
company
that
works
with
another
big
company
that
is
doing
a
they
have
like
a
bunch
of
teams.
They
share
like
for
them.
Critical
is
documentation
because
they
share
their
api
documentation
with
other
teams,
and
the
schema
like
schema
is
the
most
critical
for
them
like
that.
It
has
to
be
accurately
displayed
so
definitely
like
check
with
him.
A
Maybe
even
set
up
a
call,
because
I
I
bet
that
he
will
have
some
good
insights,
and
maybe
even
if
you
ask
him,
maybe
he'll
test
it
with
his
folks,
your
new
design.
I
think
he
would
okay
good
input
because,
like.
B
Okay,
great
I'll
I'll,
get
in
contact
with
him,
but
I
see
jonas
has
his
example,
ready.
C
C
D
B
B
C
B
B
A
And
and
even
though
we
should
finish
like
just
when,
throughout
the
whole
discussion,
we
had
missy
just
give
it
a
thought.
Maybe
we
can
discuss
it
on
thursday
on
a
conference
related
meeting
but
like
like,
if
you
want
to
do
it,
of
course,
but
like
I
remember
from
the
previous
company
that
when
I
was
working
when
we
had
some
new
topics
and
designers
were
involved,
we
were
some
like
they
were
sometimes
organizing,
like
not
a
guinea
pig,
don't
remember
the
name
like
user
testing
but
like
in
real
life.
A
A
Yeah
because,
like
the
schedule
is
not
set
up,
yet
it's
really
up
to
us
the
community,
how
we,
how
we'll
shape
it?
A
Why
not
trying
maybe
having
this
like
happy
hour
for
like
for
this
kind
of
session,
maybe
like
just
that's.
A
Oh
yeah,
let's,
let's
continue
on
thursday,
so
thank
you
so
much
everyone
for
joining
and
missy
for
putting
in
a
very
important
topic.
No.
A
I
didn't
even
notice
when
40
minutes
just
passed
like
this,
so
it's
it
was
a
good
topic.
Definitely.
A
A
What
yeah
I,
but
I
I
start
my
run
at
eight-
I
mean
in
one
hour,
so
I
still
have
time
to
write
the
in
minute.
I'm
meeting
minutes
anyway,
it's
too
past,
like
we
should
finish.
Thank
you.
Everyone
for
joining
and
yeah
join
us
again
in
two
weeks
under
ace
wing.