►
From YouTube: GraphiQL Working Group - 2022-05-10
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
B
C
B
We
did
the
triaging
yesterday.
I
think
it's
certainly
fine
to
skip
this
unless
there's
anything,
you
want
to
talk
about.
B
Yesterday,
thomas
and
I
discussed
the
next
steps
with
graphical
tldr,
we
want
to
do
the
modernization
of
components
at
the
same
time,
implementing
the
new
design,
the
new
design
will
end
up
as
a
breaking
change.
Graphical
two
will
come
out
of
that
and
monaco
will
come
later.
There
are
some
questions
open
questions
from
an
echo
technical
challenges.
B
We
need
to
find
solutions
for,
for
example,
how
to
deal
with
a
web
worker,
because,
depending
on
your
build
setup,
you
might
have
to
add
like
a
read
webpack
config
plugin
whatever,
and
that
is
something
we
need
to
figure
out,
because
that
might
be
like
a
big
braking
change
as
code
mirror
doesn't
have
that
worker.
That's
the
option
to
not
have
a
worker,
but
it's
advised
against
by
the
base
code
team,
anything
anything
else.
Thomas.
A
B
B
B
C
I
was,
I
was
excited
to
show
up.
I
popped
in
to
the
graphql
the
discussion
about
2.0
yeah,
I'm
a
designer
developer,
and
so
I
was
super
into
the
figma
file
that
was
created,
so
I
started
like
just
kind
of
poking
around
with
it,
and
I
asked
that
question
on
the
issue
about
the
font.
Face
that
was
being
used.
It
was
circular,
was
being
used
or
comments
was
being
used
anyway.
C
I
started
going
down
this
rabbit
hole
with
the
figma
file
and
started
like
building
out
a
component
library
that
I
thought
would
be
helpful.
C
Oh
and
then
I
ended
up
I've
like
just
done
a
ton
of
work
and
I'd
like
to
show
it
to
everybody
quickly
to
see
if
it's
valuable,
it's
a
ladle
library,
I've
got
monaco
working
with
the
explorer
and
it's
I've
just
spent
like
the
last
two
weeks
kind
of
going
nuts
with
it.
I
had
a
head
cold,
so
I
was
at
home
all
the
time.
Oh
so
when
we're
ready
I'd,
love
to
show
it
off
and
ask
some
questions
about
the
project
and
how
I
can
get
involved
and
all
that
stuff.
B
Whoa,
that's
awesome.
Okay!
Didn't
expect
that
that's
super
awesome.
I
will
quickly
create
the
collaborative
document
prepare
that
so
that
we
can
take
collaborative
notes
here.
D
B
Also
get
started
perfect,
that's
really
great.
To
hear
can
also
do
quick
intros
in
the
meantime.
Jonathan,
are
you
still
there.
B
Quick,
oh
good
yeah,
so
I'm
tim
co-founder
of
graph
cpn
and
we
have
thomas.
Do
you
wanna
quickly,
introduce
yourself.
A
D
C
C
C
I've
done
a
lot
of
agency
work,
a
lot
of
agency
work,
both
working
for
agencies
and
consulting
for
agencies,
and
I
left
my
I
left
my
startup
job
last
october,
because
I
was
just
burned
out
just
full
on
two
years
of
covid
just
totally
burned
out,
and
I
took
it
took
about
six
months
off,
just
not
being
in
front
of
the
computer,
which
was
great,
and
I
came
back
about
a
month
ago
a
couple
months
ago
and
I
started
working,
I'm
a
big
fan
of
prisma,
and
I
know
that
has
certain
connotations
in
the
world
these
days.
C
I
happen
to
love
it.
I
just
I
think
it's
great,
so
I
used
playground
for
a
long
time
and
I've
recently
switched
over
to
graphql
yoga,
I'm
a
big
fan
of
the
graphql
ecosystem,
and
so
I
use
graphical
graphical
all
the
time
I
use
a
lot
and
then
I'm
now
that
I'm
like
getting
back
in.
I
don't
have
a
full-time
job.
Yet
I'm
just
getting
back
into
like
getting
the
fingers
fresh
and
and
doing
that.
C
I
noticed
that
y'all
were
rebuilding
it
and
that
it
seems
really
cool
and
I'm
great
with
component
libraries
and
design
systems
and
all
that,
so
I
thought
I
might
be
able
to
help.
So
I
just
started
pitching
in,
like
I
said.
B
B
Typical
nobody
heard
about
it,
yeah
it
is
in
austin
and
we
are
even
giving
talks.
We
will,
I
will
even
talk
about
graphical,
so
I
think
you
should
come.
B
A
B
Oh
yeah,
there
we
go
yeah,
so
we're
coming
with
the
whole
team
we
have
to
meet.
I
mean
that
would
be
would
be
great.
C
That's
awesome:
it's
going
to
be
hot.
C
You
can
see
it's
I'm
sweating
already
and
I'm
inside
it's
96
fahrenheit
today,
so
whoa
it's
gonna
get
it's
in
a
month.
What
is
that
wait?
You
said
june
right
yeah.
So
a
couple
of
weeks
a
month
yeah
it's
gonna
be
hot.
B
Yes,
that
will
be
great,
so
I
will
quickly
share
the
document
with
you.
Other
notes.
D
C
D
B
B
B
Okay,
maybe
jonathan
before
diving
into
that
thomas
and
I
can
give
you
a
quick
update
of
the
next
steps.
What
we
have
talked
about,
because
we
did
the
triaging
meeting
yesterday
and
we
talked
about
next
steps
a
bit
like
contacts
already
and
then
would
love
to
hear
yeah
what
what
you
have
been
working
on.
Okay,
so
I
will.
I
will
just
share
my
screen.
I
think
I'm
quickly
sure
that
stuff
so.
B
So
what
we
basically
realized
is
that
both
the
design
and
monaco
is
a
breaking
change,
why
there
are
people
who
are
extending
the
design
and
they
have
their
own
like
plugins
and
so
on.
For
them
it
will
be
breaking,
but
also
the
component
structure
will
change
and
again,
if
you
are
a
bit
more
advanced
user,
who
is
not
just
using
the
cdn
version
of
the
of
graphical,
it
is
a
breaking
change.
B
What
we
also
discuss
is
that
modernizing
the
components
and
the
new
design
can
be
done
in
parallel,
the
order
doesn't
really
matter,
and
that
is
a
perfect
thing
to
coordinate
with
where
the
two
of
you
can
coordinate,
for
example,
so
from
graph
cdns
thomas
is
the
main
contributor
now
for
graphical,
I'm
more
in
like
a
coordinator
role
now,
and
so
after
that,
we
would
like
to
tackle
the
monaco.
Monaco
has
some
challenges
to
it,
mostly
around
the
web
workers.
B
You
might
need
a
veed
or
webpack
plugin,
but
there's
also
an
option
to
have
a
cdn
built
for
that,
so
that's
something
to
explore
and
find
good
options,
but
that
is
breaking
also
from
the
perspective
of
key
bindings,
as
monaco
is
already
bringing
a
lot
of
goodies
with
it,
it
just
makes
sense
to
adopt
them,
but
with
that
we
will
also
have
then
a
few
breaking
changes
on
that
front
and
then,
last
but
not
least,
the
new
sidebar.
We
just
put
that
as
the
last
action
here,
because
it
is
very
ambitious.
B
It
has
a
lot
of
things
we
need
to
figure
out.
We
will
need
to
stay
in
the
feedback
loop
with
a
julian,
our
designer,
because
edge
cases
might
not
yet
be
fully
expect.
So
that's
a
rough
plan
just
breaking
things
down
a
bit
more
into
smaller
components.
Instead
of
the
big
bang,
everything
is
new,
so
yeah,
that's
basically
it
thomas
from
your
side.
What
are
the
next?
Do
you
already
know
what
the
next
concrete
things
are
that
you
will
work
on.
A
Not
really
not
very
completely,
it's
basically,
I'm
gonna
continue
trying
to
modernize
the
components
and
also
we
want
to
create
a
new
package
at
graphical
react
which
should
basically
contain
the
building
blocks
for
the
graphical
ui,
so
both
the
ui
components
and
everything
you
need
for
state
management
so
like
hooks
and
context
that
glue
all
the
things
together
and
the
graphical
package
will
basically
be
the
like
a
reference
implementation
of
of
graphical,
of
how
you
can
build
a
graphical.
A
But
folks
can
then
also
use
the
graphical
react
package
to
build
their
own
version
if
they
want
to
basically
we're
using
the
the
building
blocks
that
we
already
provide-
and
I
don't
know
just
like
rearranging
them,
adding
stuff
to
it.
Whatever
fits
things
so
yeah.
Basically,
next
things
continuing
modernizing
the
the
current
react
code
from
the
graphical
package
and
moving
staff
gradually
over
in
this.
C
C
B
C
C
So
I'm
sharing
on
my
big
monitor,
let
me
get
in
here,
so
you
guys
can
see
it
a
little
bit
better.
Okay,
so
I
started
with.
C
Just
looking
at
the
figma
file
and
trying
to
piece
it
together,
trying
to
piece
together
what
I
knew
was
what
was
it's
all
great
but
like
what
was
going
to
work
in
terms
of
a
component
library
and
what
wasn't
going
to
work,
and
so
what
I
came
across
in
the
figma
file
was
a
couple
of
things.
This
can
get
kind
of
rambling,
okay.
I've
spent
the
last
two
weeks
just
like
full
on
in
this
so
whoa.
C
The
first
thing
is
that,
after
I
learned
monaco
and
learned
you
know,
I
took
apart
the
one
graph,
explorer
and,
and
another
person
stone
x,
I
believe,
is
his
github
name.
Had.
C
Had
like
you
know,
done
a
bunch
of
work
on
the
explorer
I
just
started,
taking
all
that
apart
in
the
end,
I
realized
that,
because
monaco
only
takes
hex
colors,
if
you
wanna
you
wanna,
you
wanna
customize
monaco.
We
need
hex
at
some
point
like
to
feed
in.
If
we're
gonna
have
this
thing
be
themeable
and
in
the
design
file,
all
of
the
not
all,
but
a
lot
of
the
colors.
Let's
see
I've
got
it.
C
Divided
up
here,
let's
see,
I
think
it's
this
one.
So
these
these
colors
are
the
colors
that
are
used
throughout
the
actual
designs,
both
in
the
components
file
and
in
like
the
the
screens,
the
final
screens
and
there's
alpha
values
and
they're
they're.
Just
it's
not
the
color
structure
isn't
tight
enough.
C
So
that's
one
thing
it's
gonna
take
I
mean
if
we're
going
to
use
we're
actually
going
to
use
the
figma
file
like
for
real
use
it
like
ongoing
and
and
keep
it
up
to
date
and
make
sure
that
you
know
we're
starting
here
when
we
want
to
make
changes,
that's
going
to
have
to
we're
just
going
to
have
to
change
those
colors
are
going
to
need
to
get
flattened
into
hex
colors.
B
That's
julian's
style
how
to
use
the
colors
it's
much
easier
and
figma
to
do
the
opacity-based
levels,
but
I
we
always
notice
when
we
implement
them
on
our
own.
You
need
the
absolute
colors
right
and
converting
them
into
the
hex
from
the
rgb.
Rgba
is
absolutely
legit.
No.
D
B
C
I'd
be
happy
to
it's
a
lot
of
work,
though,
to
go
through
and
do
it,
which
is
fine,
I'm
happy
to
do
it.
I
think,
there's
a
lot
of
value
in
it
again.
I
think
the
decision
really
has
to
be
made
as
to
whether
or
not
we're
going
to
use
the
figma
file
as
this
source
of
truth
for
design.
I
think
that
we
should,
I
think,
it's
a
great
idea,
there's
no
reason
not
to,
but
it
just
I'm
sure
you
guys
know
it
just
means
it's
a
lot
more
work
right.
C
When
you
start
a
change,
you
have
to
start
in
the
the
figma
file
and,
and
you
have
to,
and
it
has
to
flow
into
the
component
library.
So
that's
that's
just
kind
of
a
thing,
I'm
happy
to
do
it.
I'd
love
to
do
it,
but
it
just
means
that,
like
we're
committing
to
keeping
the
figma
file
up
to
date,
it
also
means
that
thomas,
like
you
mentioned
earlier,
when
you
know
when,
when
you
said
like
when
you
and
julian,
were
going
through
and
working
on
everything
there's
quite
a
bit.
C
This
is
all
messy.
This
is
my
copy,
so
I've
kind
of
been
mussing
around
with
it,
but
there's
a
lot
of
stuff-
that's
missing
in
here,
just
in
terms
like,
if
we're
actually
going
to
be
building
components.
Out
of
this
example,
it's
like
how
does
the
arguments
drop
down
work,
what
not
just
the
interactivity,
but
what
does
the
expanded
menu
look
like?
It
doesn't
exist
here.
So
there's
a
lot
of
work
to
get
done
in
here
and
and
again,
I'm
happy
to
take
over
some
of
the
work
that
julian
did
it's
gorgeous.
C
B
Colors
right
yeah,
that's
why
we
need
some
part
of
the
process
and
I'm
absolutely
happy
to
schedule,
calls
there
and
literally
go
through
these
things
and
give
julian
a
brief
what
we
are
missing.
B
B
Let's
say
this
way:
if
you
are
actually
working
on
it
full
time,
we
might
be
able
to
change
our
plan
here,
but
otherwise
we
would
even
let
julian
design
an
intermediate
sidebar
or
a
docker
explorer.
That
is
basically
the
old
one,
the
old
functionality,
just
with
a
new
look,
so
that
we
can
already
get
something
out.
You.
C
B
C
Yeah,
well,
I
think
it's
important.
C
If,
if
the
explorer
is,
is
really
going
to
be
like
a
we're
going
to
go
with
this
plug-in
based
system
right
and
we're
going
to
build
it
like
that,
I
think
we
really
have
to
try
to
get
it
as
complete
as
possible,
and
you
know
not
do
like
an
intermediate
step
and
then
and
then
a
rebuild
I'm
struggling
to
like
see
in
the
future.
C
How,
if
that
might
be
a
breaking
change,
if
that,
if
that
swaps,
I'm
not
sure,
but
I
think
there's
not
that
much
missing
from
the
figma
file
in
terms
of
like
actual
component
structures.
There's
there's
some,
but
it's
the
bulk
of
the
work
is
already
done.
But
I
think
the
challenge
really
is
more.
As
I
is
I
I
I
as
a
developer
and
a
designer
I
go
through
this
iterative
process
a
whole
lot.
C
I
never
advocate
for
building
a
full
design
and
then
trying
to
or
designing
something
fully
and
then
trying
to
build
it,
because
you're
always
going
to
have
to
go
back
and
forth.
You
always
have
to
move
back
and
forth
so
with
the
work
that
has
been
done
by
a
bunch
of
different
people
on
starting
to
build
out
the
new
dock.
Explorer
we've
already
got
a
list.
I've
already
got
basically
a
list,
I
don't
have
it
written
down,
but
a
list
of
like
what's
missing.
So
I
don't
know
that.
C
Yeah,
I
think
it
makes
like
I
said
it's
almost
all
there.
Let
me
just
show
you
guys
what
I
have
here:
okay,.
C
This
is
this:
is
ladle
ladle's,
a
storybook
alternative
if
you've
used
storybook
before
I
have
used
it
a
lot.
This
is
my
first
time
using
ladle.
I
use
storybook
a
lot,
it's
so
slow.
I
just
I'm
so
glad
something
else
came
along
this.
C
It's
been,
it's
been,
it's
been
fun
to
learn.
It's
been
challenging.
Here's
the
config
file
for
ladle,
here's
that
vitae
plug-in
from
that
you
mentioned
earlier
right.
I
had
to
to
figure
that
out.
There's
a
this
isn't
clean
like
it's,
not
clean,
but
there's
a
lot
here.
So
there's
some
basic.
Let
me
actually
go
back.
Go
back
to
the
code,
so
here's
the
components
folder.
I
have
these
components
all
kind
of
broken
down.
There's
a
base
ui,
that's
just
fundamental
ui
components
that
take
basic
props.
C
There's
some
shell
components.
I
haven't
used
a
whole
lot
of
this,
yet
there's
a
reference
folder
that
contains
like
any,
like
actual,
like
organism,
style
components
that
I'm
using
in
this
case
there's
only
one
and
it's
the
demo
for
the
app
there's
a
layouts.
This
is
all
just
like
layout
components.
There's
only
one
right
now,
there's
an
explorer
folder
that
has
this
is
basically
like
the
new
docs
explorer.
This
is
all
that
stuff.
C
You'll
probably
recognize
like
the
names
of
some
of
these,
because
I'm
just
building
off
of
work
that
other
people
have
done
and
then
there's
an
editor
folder.
That's
got
an
editor.
C
An
editor
group
which
is
like
the
the
query,
the
variables
and
the
response,
and
then
a
tab
set
up.
I
haven't
worked
on
this
tabs
yet,
but
that's
basically
what
this
looks
like.
So
if
we
go
over
to
ladle
here's
an
editor,
so
there's
a
story
for
the
query
editor.
I
haven't
done
much
work
on
customizing
the
view
for
these
editors.
I
figured
it
out
last
night
finally
hit
me
like
how
to
do
it.
C
C
Does
the
thing,
and
then
it
also
includes
the
tabs
and
and
then
any
of
the
the
sub
content
right,
the
headers,
the
network
response.
Whatever
else
is
going
to
be
done
there
there's
a
lot
of
design
work
to
do
there.
I
think,
and
then
the
big
one
is
just
the
the
demo
right.
So
here's
explorer
working.
B
C
C
Works,
it's
all
tied
in
with
monaco
whoa.
So
there's
a
lot
here.
Arguments
are
not
done
yet.
I
I
have
the
the
the
descriptions
in
this
caused
a
lot
of
issues
like
on
the
on
the
thread
on
github
with
like
how
we
do
these
descriptions,
and
can
you
really
fit
them
in
in
line?
C
I
prefer
the
design
tim
you
and
julian
released
a
video
on
green
right
where
you
took
us
through
a
tour
of
the
design
that
you
have
been
working
on
and
in
the
video
the
figma
file
has
the
descriptions
below
the
field
name
and
the
type
which
I
think
is
was
really
good.
That's
not
in
the
current
sigma
file.
So
this
is
going
to
be.
You
know,
that'll
probably
be
an
issue
with
with
how
to.
B
Options
there
one
was
inline
but
cut
off,
but
on
the
other
was
below
and
full
we
weren't
sure,
which
one
makes
most
sense
happy
to
talk
about
it
and
also
experiment.
I
think
we
just
need
a
few
test
schemas
and
look
how
it
looks.
C
I
think
that's
exactly
right.
That's
one
of
the
reasons
I
really
wanted
to
jump
in
and
just
start
start
getting
stuff
on
the
screen
here,
so
we
can
start
playing
with
it
and
using
it
and
I'm
a
massive
fan
of
prototyping,
like
I
said
iterative
right
in
between
design
and
develop
constantly.
That's
how
I
work
and
more
than
likely,
I
would
just
build
in
two
versions
right.
You
can
flip
a
flag
on
that
component
that
either
puts
it
in
line
or
drops
it
below
something
like
that,
and
we
can
play
with
that.
C
So
let
me
show
you
a
little
bit
of
just
the
state
management,
because
I
think
it's
going
to
be
controversial
and
you
know
like
I
said
I
built
this,
not
necessarily
for
the
final
product.
I
love
it
if
some
of
this
gets
included,
but
I
also
just
wanted
to
get
going
as
fast
as
I
can,
and
so.
For
that
reason
I
use
the
stand
as
the
state
manager
there's
this.
Have
you
guys
used
this
as
a
stand
before.
C
So
that's
what
I'm
using
for
the
state
manager
here
I
I
know
it's
not
it's
a
dependency.
It's
probably
not
going
to
be
popular,
but
I
wanted
to
just
get
something
going
as
fast
as
possible.
So.
C
There's
a
single
hook,
that's
called
use
graphical.
With
the
stand
you
create
a
hook,
you
create
a
store,
that's
automatically
a
hook.
You
can
use
it
anywhere.
So
this
isn't
like
a
typical
react
hook.
The
hookness
is
all
coming
out
of
the
stand,
so
here's
the
shape
it's
got
a
schema.
It's
got
a
function
to
initialize
the
schema.
It
holds
the
query,
a
function
to
set
the
query.
It
holds
the
variables
a
function
to
set
it
the
operation,
the
results
and
then
execution
execute
operation
and
operation
action.
C
This
is
all
tied
together
to
the
way
that
the
explorer
works
with
the
editor
group.
A
lot
of
this
work
comes
directly
from.
C
C
And
so
basically,
let's
see
let's
go,
let
me
show
you
the
story
for
that
app
container,
so
you
can
just
sort
of
see
how
it
all
comes
together.
It's
I
don't
remember.
If
I
have
resizing
working
again,
I
think
I
do
yeah
yeah.
So
the
app
is
in
a
horizontally
resizable
container.
It's
got
a
left
pane
and
a
right
pane.
C
You
can
see
that
we're
just
grabbing
everything
out
of
the
state
hook
and
feeding
it
in
to
the
editor
group
component.
The
explorer
is
also
doing
something
similar
where
we're
just
grabbing
the
schema
from
the
hook.
The
schema
is
initialized.
C
Currently
it's
initialized
at
the
ladle
level,
so
there's
a
provider
that
just
wraps
the
whole
thing
and
that's
where
I'm
initializing
the
schema
so
like
I
don't
have
this
hooked
into
you,
couldn't
really
you
can
only
play
with
this
in
ladle
right.
It's
not
really
set
up
to
be
like
that.
Much
of
a
demonstration.
It's
just
meant
to
get
stuff
on
the
screen
and
get
us
playing
with
it.
That's
the
basic
setup,
like
that's
the
challenging
stuff.
C
C
So
there's
there's
the
stitches
thing.
Let
me
look
at
the
let's
go
over
the
package
face
on
here.
Just
so
we
can
see
it.
C
Colors
from
radix
stitches
from
radix,
I
don't
think
I'm
actually
using
imr
anywhere
it's
just
in
there
from
like.
When
I
was
playing
with
it.
Monaco
monaco
graphql
react
and
to
stand.
C
I've
got
my
own
eslint
configuration
that
I'm
using
in
here,
but
like
there's,
nothing
crazy,
like
the
only
stuff.
That's
crazy
is
stitches
and
it's
a
stand
and
while
that's
not
necessarily
like
easily
swappable,
it's
certainly
not
a
crazy
thing
to
like
get
those
swapped
out
at
some
point
for
whatever
the
final
css
and
state
management
solution
is
gonna,
be
so
that's
the
basics.
D
C
So
next
up
for
me
in
this
world
and
I'd
love
to
hear
opinions
and
how
you
all
think
we
could
should
go
go
forth
here.
Next
up
for
me,
is
just
working
on
the
ui
for
the
editors
just
customizing
it
more
to
fit
the
design
as
it
stands
right
now,
just
so
it
when
people
light
this
thing
up.
It
looks
like
the
design
and
not
like.
C
It
looks
right
now,
so
the
editor
stuff
that
will
only
take
another
couple
hours
and
then
I
need
to
figure
out
the
logic
for
the
arguments
like.
I
said
a
lot
of
the
code
that
I
used
in
the
explorer.
C
Handle
operation,
so
this
is
the
button
that
triggers
the
change
in
the
in
the
fields
in
the
explorer.
A
lot
of
this
code
was
taken,
was
mod,
taken
from
and
modified
based
on
what
stonex
did
and
also
what
one
graph
did,
I'm
sort
of
in
the
middle
of
translating
a
lot
of
what
goes
on
in
one
graph
in
terms
of
the
arguments.
That's
what's
left,
so
just
the
arguments
is
really
all
that's
left
and
then,
like
you
said
earlier,
all
the
edge
cases
of
which
there
will
be.
C
There
will
be
plenty,
but
once
once
that's
done,
I
think
this
is
like
pretty
much
going
to
be
in
a
place
where
people
can
start
playing
with
it.
You
know,
there's
a
lot
of
bass,
components
that
still
need
to
get
built
like
buttons
and
just
kind
of
like
really
simple
stuff
that
I
skipped
over,
because
I
I
realized
I
had
a
lot
of
learning
to
do
with
monaco
and
with
just
the
craziness
of
handling
selection
sets
and
field
selections
and
all
that
graphql
stuff.
C
So
that's
where
it's
at.
D
B
A
I
think
this
is
great
work,
especially
on
the
ui
side,
looking
at
the
docs
explorer
and
what's
already
what's
already
there
and
I
believe
from
the
ui
side,
we
could
probably
take
it.
Take
a
lot
of
this.
These
things
that
we
already
ditched
over
and
over,
as
you
said,
I
think
we
still
need
to
figure
out
how
we
wanna
do
state
management.
So
currently
it's
basically
react
state.
A
I
personally
leave
it
at
that
as
long
as
we
don't
really
need
some
more
advanced
state
management
like
if
we
hit
any
kind
of
limit
in
terms
of
performance
or
complexity.
I
just
like
to
keep
it
more
simple.
I
think
you
also
what
we
also
didn't
decide
yet
is
basically
or
region.
Design
is
how
we
want
to
do
or
handle
css
and
theming.
B
C
B
Yeah
like
directly
as
css
variables,
that
would
also
mean
it
doesn't
really
matter
what
we
internally.
B
To
do
the
css,
because
the
interface
that
people
would
use
to
do
theming
is
css
variables
anyway
right.
It's.
B
A
I'd
probably
say
integrate
it
them
later,
so
basically,
I'd
like
to
stay
with
the
incremental
approach
that
we
decided
on
to
just
move
step
by
step
towards
the
goal
that
we
have
in
front
of
us,
but,
like
both
things
that
you
worked
on,
jonathan
are
basically
the
two
big
new
things,
namely
monaco
and
the
dogs
explorer.
A
So
this
is
something
that
we
don't
have
anyways
yet
in
the
current
graphical
and
or
like,
we
have
like
examples
around
moneco,
but
nothing.
That
really
looks
like
the
final
thing.
C
C
Some
of
it's
really
complicated.
I
was
surprised
at
how
complicated
some
of
it
was,
and
you
know
the
monaco
stuff
and
the
explore
stuff.
It's
really
hard
to
look
at
existing
code.
That's
written
for
that
like
in
separate
things
right.
It's
you
can
look
at
one
graph
explorer
and
they've
got
a
file.
It's
like
2700
lines
of
code
right,
it's
really
hard
to
sort
of
grok.
C
What's
going
on
and
get
a
good
understanding
of
it
as
an
example,
and
there
really
doesn't
seem
to
ex
another
example-
doesn't
really
seem
to
exist
of
that
kind
of
work.
So
that's
really
hard.
Additionally,
the
monaco
stuff-
I
don't
I'm
not
sure
what's
going
on
at
microsoft,
but
it's
really
hard
to
just
find
like
base
basic
tutorials
for
how
to
use
it,
not
monaco
graphql.
I
just
mean
monaco
in
general,.
C
C
I
think
it's
going
to
give
anybody
who
wants
to
get
involved
here,
a
a
leg
up
in
just
learning
some
of
the
basics
right,
because
you
can
put
this
in
front
of
somebody
and
they
can
begin
to
understand
the
complicated
parts
a
lot
easier
than
if
they
were
just
out
on
their
own
working
on
it,
and
I
know
that
I'm
not
the
only
one.
I
might
be
the
only
one
that
went
this
nuts,
but
I'm
not
the
only
one
that
wants
to
get
involved
with
this
project.
C
There
seems
to
be
a
lot
of
interest
and
having
a
tool
that
people
can
just
play
with
and
use,
and
everybody
can
can
use
as
a
as
a
prototype,
I
think,
is
incredibly
valuable.
My
goal
is
not
to
like
get
this
integrated
into
the
react
package,
because
I
know
that
I've
made
decisions
that
are
not
the
they're,
not
they're,
not
good.
For
the
final
product.
A
Still,
it
looks
already,
I
mean
if
the
markup
and
like
the
styling
looks
very
similar.
I
mean
it's
like.
We
can
basically
take
a
lot
of
this
right
over,
like
maybe
not
just
not
copy
the
file
one
to
one
into
into
the
graphical
repository,
but
still
the
work
that
you've
done
probably
is
gonna.
Gonna
save
us
already
like
a
lot
of
time
when
it
comes
to
the
to
the
sidebar
at
2.64,.
D
B
A
B
So
then,
moving
forward
jonathan.
First
of
all,
I
want
to
offer
here
so
how
I
see
that
is
that
we
can
kind
of
have
two
track
development,
meaning
we
have
the
official
track.
That
thomas
is
working
on,
which
is
like
the
modernization
implementing
the
new
design,
not
yet
for
the
docker
explorer
but
like
for
around
the
editor
and
so
on,
and
then
you
can
already
de-risk,
basically
the
sidebar
and
I'm
happy
to
connect
you
with
julian
and
also
with
thomas.
We
can
schedule
a
call.
B
I
don't
think
that
needs
to
be
a
long
call
and
if
you
could
just
prepare
all
the
questions
you
have
and
to
be
fair,
we
might
not
even
need
a
call.
We
can
just
have
a
channel
together
where
you
can
just
prepare
them.
Hey
it's
unclear
about
arguments.
These
points
are
unclear,
unblocking
you,
because
what
you're
doing
you're
de-risking
the
sidebar
and
with
that
we
can
already
get
all
of
these
tricky
interactions.
We
can
kind
of
quickly
iterate
on
them
prototype
them
find
out
if
they
work
and
from
there
once
we're
in
our
plan.
B
At
the
point
where
we
want
to
go
for
the
sidebar
which,
depending
on
how
quickly
we
get
the
rubber
on
the
road
here,
could
be
already
in
a
few
weeks,
then
we
could
just
start
integrating
that
work.
B
So
from
your
interest
of
commitment
here,
jonathan,
would
you
also
be
interested
in
working
on
the
kind
of
slow
path
of
like
taking
the
existing?
Oh
doc
jones?
Coming
hello,
hello,.
D
B
Jonathan,
would
you
be
interested
in
also
working
with
thomas
on,
like
this
quote,
unquote
slow
path,
or
would
you
like
to
rather
focus
more
on
your
prototype
for
now?
What's
your
interest,
there.
C
I'm
I've
had
a
really
good
time
working
on
this,
the
last
couple
of
weeks
and
I
plan
to
continue
working
on
it.
So
I'm
I'm
happy
to
slot
in
we're
at
like
wherever
it's
necessary.
I
don't
know
that
we
that
I
can
make
a
decision
right
now
about
what's
best.
I
think
I
love
to
put
this
code
in
front
of
people
and
I'd
love
to
do
some
work
in
figma
just
to
sort
of
reset
the
baseline
before
just
deciding
exactly.
C
B
Okay,
but
generally,
I
would
say
it
seems
like
the
way
you
can
have.
The
most
impact
right
now
would
be
where
you
already
have
the
most
contact
switches
in
the
project,
because
you
built
up
a
lot
of
contacts
over
the
last
two
weeks
and
I
think
would
be
great
if
you
just
continue
exploring
that
and
then
we
can
later
work
together
on
integrating
that
into
the
main
repository
yeah.
C
Yeah,
I
I
don't
have
context
for
I've
done
a
lot
of
reading,
both
in
the
discord
and
through
the
github
repository
for
for
graphic
ql,
but
it
you
know,
it
seems
like
there's
been
start
and
stops
to
this
2.0
thing
for
the
last
couple
of
years,
and
so
it
was
really
hard
for
me
to
get
just
to
get
a
baseline
to
get
an
understanding,
which
is
why
I
just
started
kind
of
working
on
my
own
before
I
got
to
meet
everybody
and
participate.
C
I
did
message
ricky
on
discord
a
couple
of
weeks
ago,
just
saying,
like
hey,
I'm
working
on
a
component
library
and
and
I
want
to
help
contribute
so
I
haven't
actually
talked
to
him.
C
It's
been
about
a
week
since
we
messaged,
but
I
haven't
delivered
anything
so
I'm
I'm
I'm
I
at
the
very
least
there'll
be
shell
layout
and
base
ui
components
that
can
effectively
be
like
one
to
one
moved
over
right,
the
base
components
and
then
there's
a
lot
of
logical
stuff
that
that
I
think
will
be
able
to
get
worked
out
in
my
component
library
as
well.
So
I
agree
that
that's
that's
probably
the
strongest
place
for
me
to
be
is
just
to
keep
plugging
away
in
a
prototype.
B
Makes
total
sense,
we
have
another
person
who
is
not
here
today
who
wants
to
help
as
well
moritz,
who
will
talk
with
thomas
and
I
think
generally,
it's
not
the
lack
of
willingness
from
the
community.
It's
really
getting
the
project
into
the
state
that
people
can
contribute
first,
and
that
is
what
even
for
thomas
and
me
who
are
looking
into
this
for
weeks
and
months.
It's
not
always.
D
B
What
we
do
every
monday
now
can
join,
but
you
don't
have
to
is
a
triaging
meeting
one
hour
of
just
going
through
old
issues.
B
But
then
I
would
say:
that's
that's
a
good
state.
Where
can
I
best
reach
you
jonathan?
Are
you
in
discord.
D
B
Okay,
so
what
I
suggest
is
that
if
you
could
just
prepare
a
list
of
questions,
you
have
jonathan
and
open
questions
for
the
design,
and
I
would
just
open
a
chat
with
julian
or
even
better,
probably
would
just
go
into
the
graphical
contributors
channel,
a
graphical
development
and
add
julian
in
there,
and
you
can
just
ask
the
questions
there
and
I
will
make
sure
that
julian
answers
and
if
it's
something
we
cannot
make
clear
in
written
form,
then
we
can
also
jump
on
a
quick
call.
B
C
I'll
take
that
to
do
of
a
list
of
sigma
questions
or
concerns
or
comments,
give
me
24
hours,
because
I
haven't
been
in
the
figma
file
really
for
about
a
week
and
a
half.
So
I
want
to
now
I'm
going
to
go
back
in
there
and
just
just
try
to
build
my
list
by
looking
at
it.
So
give
me
till
tomorrow
to
do
that.
B
Okay,
perfect
thomas,
I
guess
we
meant
in
the
comments,
not
the
prisma
file
but
the
figma
file.
I
don't
know.
B
Okay,
great,
so
super
awesome.
Jonathan
to
see
this
work
happening
here
really
great
in
a
month.
Pretty
much
on
the
day
is
the
graphical
conf,
where
I
will
present
things,
but
I'm
also
thinking
you
should
actually
be
on
the
stage
because
you're
doing
the
work
we
can,
we
can
coordinate
things,
maybe
even
doing
the
talk
together
or
something
and
with
you
yeah
I
mean
thomas
and
jonathan
great.
So
then,
if
there's
nothing
else,
we
can
just
leave
it
at
that
and
give
everybody
some
time
back.
B
C
B
Moving
these
things
forward
and
let's
just
use
the
graphical
development
channel
as
the
main.
C
B
C
Is
that
is
that
triage
meeting
in
the
working
group
folder.