►
From YouTube: GraphiQL Working Group - 2022-12-13
Description
GraphQL is a query language for APIs and a runtime for fulfilling those queries with your existing data. GraphQL provides a complete and understandable description of the data in your API, gives clients the power to ask for exactly what they need and nothing more, makes it easier to evolve APIs over time, and enables powerful developer tools. Get Started Here: https://graphql.org/
A
Giving
it
some
more
minutes
if
I
drop
out,
but
it
seems
like
nothing's
going
on
today.
B
B
B
Oh
is
my,
it
might.
Are
we
the
first
two.
B
B
You
wanna,
do
you
want
to
wait
another
few
minutes
or
do
you
wanna?
Do
you
wanna
jump
in
I?
Think
you
and
I
are
familiar
enough
with
sort
of
the
status
of
things
we
could
just
kind
of
quickly
run
through
some
things.
I
have
some
some
bullet
points,
just
that
are
discussions
like
that.
Aren't
really
notes,
they're
just
discussions
but
and
then
I
just
want
to
have
talks
about
the
operation
Builder
and
that
kind
of
stuff.
Do
you
want
to
just
jump
right
in.
B
Okay,
so
the
first
thing
I
have
is:
let's
get
all
these
quality
of
life
PR's
merged
in
all
the
ES1
stuff.
That
Dimitris
has
been
putting
in
I'd
love
to
just
get
those
in.
They
seem
like
they're
passing
what
they
need
to
pass.
B
That's
a
that's
a
ton
of
work
that
is
gonna.
You
know
it's
gonna,
be
really
helpful.
A
A
A
B
No
worries
it
happens,
so
I
was
just
talking
about
all
these
wonderful
quality
of
life.
Pr's
like
focused
around
es
lent.
That
would
be
nice
to
get
merged
in
I'm,
not
I'm,
not
sure
what
to
be
trees
is
waiting
for.
Maybe
he's
got
more
to
to
add,
but
I'm
very
excited
to
get
this
stuff
in.
A
I
think
it's
just
waiting
for
somebody
to
have
a
look.
I
did
a
pass
last
week
on
some
of
them
and
after
I
approved
them.
We
also
not
merged
up
with
him.
I,
don't
know
10
minutes
or
something
so
but
like
most
of
them,
I
think
I
didn't
look
at
the
new
ones,
pretty
small,
so
I'll,
see
or
like
we
can
just
seem
to
kind
of
get
some
eyes
on
it.
Yeah
well.
B
I
think
I
think
that
I
think
Dimitri
has
I'm
trying
to
find
it
here.
He
has
a
is
an
issue
28.94,
where
he's
he's
got
a
to-do
list
in
here.
I'll
share
this,
so
maybe
he's
waiting
to
get
all
these
to
merge
a
lot
of
these
in
until
he
gets
this.
This
List
complete,
but
I
just
wanted
to
say
out
loud
how
excited
I
am
for
all
these.
For
all
these
updates,
maybe
he's
just
waiting
to
get
to
get
all
that
done.
B
So
there's
no
action
item
there
just
wanted
to
talk
about
it.
A
I
think
like
excellent,
could
be
just
for
us
to
try
to
have
a
look
at
them
and
I
think
it's
it's
usually
doesn't
understand.
Then
we've
just
match
them
and
should
be
fine.
B
B
I
think
it's
okay,
as
long
as
we're
just
making
notes,
I
think
it's
I!
Think
for
now!
That's
fine!
Let
me
I'm
going
to
request
edit
access
here.
B
A
B
Metro,
okay,
so
this
the
second
thing,
the
second
thing
yeah
anyway.
The
second
thing
that
I
wanted
to
I
wanted
to
bring
up.
Was
these
other
P
there's
a
couple
of
PRS
that.
B
I,
don't
know
how
closely
you
were
following
this,
but
the
there's
a
company
called
near
form,
that's
working
on
a
mercurius
plug-in
for
graphical,
which
is
cool.
It's
super
cool,
but
it's
like
a
full
screen,
plug-in
right,
the
their
plug-in,
so
the
the
history
plug-in
and
the
docs
plugin
date
interface
directly
with
the
document
editor
with
the
operations
editor,
this
full
screen
plug-in
that
they're
building
doesn't
directly.
It's
schema
aware
right.
B
It
wants
to
it
needs
to
consume
the
schema
context
and
maybe
respond
to
some
other
bits
that
are
inside
of
the
the
contact
state
for
graphical,
but
it
doesn't
interface
with
the
with
the
editors
directly
and
so
the
there's
two
PRS,
the
original
PR.
B
B
Was
was
a
first
attempt
at
being
able
to
control
the
resizer
pains
at
the
graphical
level
right,
the
graphical
component
level,
which
I
I'm
not
totally
sure
how
I
feel
about
it?
I
think
it
adds
complexity
to
the
API
surface,
the
components
themselves
that
resize
your
component
wasn't
really
built
to
be
changed
like
that
right.
You
know
it
has
a.
A
B
Like
really
good
behavior,
that's
built
into
it,
and
so
the
you
can
see
here,
I
just
wrote
up
a
code
sandbox
really
quickly
that
that
just
sort
of
did
this
that
allowed
them
to
do
this
thing
without
without
all
of
that
code,
complexity
in
graphical
react
or
in
the
graphical
component
they'd
still
like
to
get
the
pr
in
because
they
think
it
might
help
other
folks,
which
I
agree
with
I
agree
that
it
could
be
helpful
for
for
folks
that
get
into
situations
like
this.
B
The
point
that
I've
I've
made
that
I've
made
here
in
in
both
this
PR
and
the
the
follow-up
PR
which
which
did
basically
the
same
thing
but
changed
the
API
surface,
was
that
the
we
should
the
graphical
VT
design
has
get
like
a
full
screen
view.
Changer
right,
like
there's
a
drop
down
there,
that's
meant
to
change
that
primary
view.
That
was
originally
thought
of.
B
I
know
that
there
was
wasn't
a
lot
of
exploration
down
there,
but
it
was
meant
to
solve
these
sort
of
like
it
was
meant
to
be
the
plug-in
space
for
these,
for
these
full
screen,
plugins
and
and
I.
Think,
like
I
said
here
like
this,
is
an
opportunity
for
us
to
do
that,
because,
if
we're
interested
in
helping
people
down
the
line,
the
right
way
to
help
those
people
would
would
be
to
you
know,
Advance
the
plug-in
API
in
advance
of
the
design
a
little
bit
with
this.
This
full
screen
view.
B
A
I'd
love
to
call
that
video
making
with
the
design
so
I
think
that
the
resizing
component
was
really
like
for
this
vertical
horizontal
precising.
It
was
never
intended
to
be
any
more
sophisticated
than
that,
so
I
can
only
agree
to
the
things
that
you've
been
saying.
I
think
this
is
this
could
be
a
good
chance,
especially
if
they
are
up
for
also
contributing
to
this
yeah.
That
doesn't
need
to
be
us
that
do
all
the
work
right.
B
A
B
Be
a
shift
in
just
that
commitment,
so
they've
I,
just
I
just
pasted
in
the
second
pull
request
filed
from
that
team,
which
again
like
it's
all
good
code,
there's
no
reason
that
like
we
would
reject
it,
except
that
this
is
an
opportunity
for
us
to
do
this
thing,
the
way
that
it
had
sort
of
been
thought
of
at
the
beginning,
and
so
I
I
I'm
not
going
to
make
this
decision
I
I
wish
there
were
more
of
us
here
to
talk
about
this,
because
it's
a
like
you
said
it's
a
it's
a
bigger
commitment
to
do
it
the
right
way,
but
it's
the
right
way
to
do
it.
A
Yeah
I
actually
think
we
are
like.
We
have
probably
the
two
main
maintainers
now
of
graphical,
like
not
the
whole
code
base,
because
there's
like
the
editor,
the
the
LSP
and
stuff
in
there,
which
is
more
like
Ricky's,
Ricky
spark
still,
but
I
feel
actually
that
we
are
empowered
to
make
these
decisions.
A
So
if
we
both
agree
now
I
mean
we
show
up
here
to
this
meeting.
If
we
both
agree
that
this
is
the
way
forward
and
I
think
we
can
make
a
decision
on
that.
B
Yeah
and
I
I
think
excuse
me,
you
know
fun
to
reject
a
PR,
especially
one.
That's
that
follows
the
rules
and
is
done
well,
but
if,
if
we
could
make
you
know
if
we
can
propose
path
forward
for
exploring
the
the
full
group
they
know,
if
we
can
get
that
level
of
commitment,
then
I
think
then
I
think
that
we
should
I
believe
I
I.
It's
been.
B
A
B
Solution
so
I
think
after
you've
had
a
chance
to
look
out
both
of
them
and
look
at
the
code.
Sandbox
and-
and
you
know
we
can
async
this
into
scored.
We
can
and
actually
they're
on
Discord,
so
they're.
Also
there
there's
a
long
conversation
about
this,
specifically
on
Discord.
Actually,
let
me
get
that
that
thread,
link
and
I'll
put
it
in
the
notes
as
well,
because
I
think
it's
relevant.
A
Yeah
I
mean
technically,
they
could
just
basically
copy
a
graphical
and
use
graphical
react
to
like
build
this
thing
themselves.
If
they
really
wanted
to
well.
B
They're
so
they're
they're,
building
a
plug-in
that
I
think
that's
yeah,
that's
the
that
was
the
thing
for
them
is
they're
building
a
plug-in
and
they're
also
consuming
their
own
plug-in,
so
their
plugin
is
going
to
go
into
they
into
the
community
and
some
somebody
else
that
might
be
running,
classify
and
you're
curious
might
want
to
use
that
plug-in,
so
they
don't
they're
not
going
to
have
like.
If
you
look
at
the
code
sandbox,
that's
all
at
the
that's
all
at
the
graphical
level.
B
A
Like
sure,
that's
not
so
it's
it's,
maybe
like
a
short-term
fix
for
them
to
to
have
their
the
experience
in
the
curious,
but
yeah
definitely
like
it
would
be
a
way
for
them
to
work
around
it
for
the
time
while
we
like
lay
out
the
path,
as
you
said,
for
this
kind
of
full
screen,
plug-in
experience
and
how
we
want
that
to
look
like.
B
We
go
in
that
discussion,
I
even
I,
even
tagged
Benji,
because
I
know
that
Benji
and
the
work
in
you
know
postgraphile
had
talked
about
early.
A
B
Like
earlier
this
year,
when
Tim
and
Julian
were
presenting
the
design
to
the
to
the
larger
working
group,
Benji-
and
you
know
other
folks-
they
just
I-
went
back
and
I
watched
that
video.
They
had
lots
of
great
questions,
and-
and
this
remember
when
the
plugin
API
had
like
a
lot
of
different,
there
was
a
lot
of
possibility
and
there's
a
lot
of
options
there.
B
So
even
in
that
disorder,
because
I
asked
Benji-
and
he
said
he
did
have
some
ideas,
but
he
wasn't
ready
to
share
them
just
yet,
but
I
know
that
this
is
something
that
people
want
right.
We've
talked
about
this
before
it's
I
think
it's
a
really
be
a
really
cool,
really
cool
way
to
expand
the
plug-in
API
without
having
to
think
about
it.
B
Doesn't
it
it
only
touches
in
information
architecture
right
you
get
into
a
lot
of
weird
information,
architecture
and
layering
problems
with
the
the
sidebar
plugins,
because
they're
they
they're
generally,
it
seems
like
they
are
meant
to
influence
the
editors
directly
right.
Like
the
history
editor.
Sorry,
the
history
plugin
is
destructive
to
the
the
document
editor,
the
operations
editor
and
the
the
docs
plugin
is
linked
directly
right.
You
can
get
you
can
you
can
talk,
you
can
effectively
toggle
between
the
two
they're
connected,
so
working
on
this
full
screen
view.
B
Plugin
allows
us
to
separate
the
thinking
about
what
the
surface
of
this
of
a
plug-in
API
might
be
without
having
to
consider
like
all
of
the
complexity
around
like
the
the
editors
themselves
right
because
they're
this
is
separate
from
the
editor,
and
it
just
gives
us
a
way
to
explore
the
plugin,
so
I
think
it's
a
really
good
opportunity
and
I
I
I
think
it's
a
it's.
It's
not
an
easy
win,
but
it's
easier
than
Monaco
and
it's.
A
It
is
probably
agreed,
I
know
that
the
stalinist
decision
in
our
meetings
notes
I'm
fine
with
that
and
as
we
are
the
only
two
here,
we
have
an
agreement,
cool.
A
Awesome
I
also
know
the
thought
that
I
will
look
at
the
dprs
and
we'll
also
leave
my
my
sentiment
in
there
yeah
sorry
for
not
being
too
active
in
the
reasons
it's
has
been
has
been
hard
to
find
a
time.
B
Yeah
I
understand
the
the,
so
those
are
the
just
two
issues:
the
those
are
like
chores
that
I
wanted
to
to
talk
about
anything
they
wanted
to
discuss.
I
have
not
just
a
status
check.
I
have
not
you
know,
really
Advanced
the
State
Management
RFC,
primarily
because
I'm
I'm
busy
with
other
things,
but
also
a
big
reason
why
I
haven't
Advanced.
That
is
because,
as
you
know,
just
the
tooling
and
the
the
setup
inside
the
repository
it
just
makes
it
sort
of
like.
B
Yeah,
it's
uneasy
to
work
with.
So
it's
just
like
those
kind
of
big
changes
really
require
a
lot
of
these
eslint
plug-in
improvements
are
going
to
be
very
helpful.
B
The
the
pr
so
so
I
started
working
on
the
State,
Management
RFC
and
then
I
realized
like
I.
Can't
do
this
I
can't
reasonably
do
this,
given
the
situation,
and
so
that's
when
I
went
to
I
filed
the
draft
PR
for
for
webpack
to
Vitae,
and
it
sounded
like
Ricky
was
positive
about
it
and
had
some
like
was
was
down
the
road
of
being
able
to
get
it
like
full.
B
Because
I
did
it's
my
it's
just
a
draft
right,
it
wasn't
fully
integrated,
getting
it
fully
integrated
and
then
that
work
hasn't
been
completed.
So
just
the
status
check
for
me
is
State.
Management
RFC
is
just
on
hold
until,
like
the
tooling
gets
cleaned
up,
which
I
feel
like
we're
we're
getting
there,
which
is
a
wonderful
feeling
and
then
the
webpack
to
Vitae
situation.
B
There's,
if
you
have
a
look
at
that
PR
like
there's
a
couple
of
to
Do's
that
just
need
to
get
addressed-
and
it
sounds
like
Ricky
you
know
was-
was-
was
doing
some
things
to
integrate
it
deeper
into
the
mono
repo
build
setup
versus
what
I
just
did,
which
was
really
just
focusing
on
graphical
and
getting
rid
of
some
of
the
webpack
stuff.
So
I'd
love
to
really
get
that
one
moving
through,
because
I
think
it's
an
unlock
for
some
of
the
other
issues
that
we're
having
yeah.
That's
my
that's.
My
status
checking.
A
Awesome
agreed
I
think
the
tpr
has
been
open
now
for
probably
half
a
year
so
plus
one
for
like
it
doesn't
make
sense
to
close
it,
because
it's
the
thing
that
we
want
to
move
towards.
So
let's
try
to
get
this
in.
A
B
Yeah,
so
there
were
two:
let
me
let
me
find
them.
I'll
link
them
up
in
the
document.
The
reason
that
I
started
over
was
because
the
first
one
is
I'm,
just
gonna
find
them
right
now.
The
first
one
was
an
abandoned
attempt
that
after
I
looked
at
it
didn't
even
really
get
close.
I
mean
it
got
it.
Their
Vitae
was
in
there,
but
it
didn't
solve
the
end-to-end
problem.
It
didn't
solve
the
you
know
the
dev
server
it
didn't
do
any
of.
A
B
So
it
wasn't
a
great
starting
point,
especially
just
because
it
was
so
old,
like
it
didn't
make
sense
to
pick
up
and
the
second
one
that
came
in
again.
I'm
gonna
find
these
and
link
to
them.
The
second
one
that
came
in
was
equally
incomplete.
It
just
didn't
solve
like
all
of
the
price.
It's
a
comp,
that's
set
up
in
graphical
is
really
complex,
and
so.
A
B
Both
of
them
I
would
like
to
close
them,
I'm,
just
I'm,
just
going
to
close
them.
If.
A
You,
if
you
have
a
follow-up,
that's
incorporating
like
the
changes
from
those
two.
Then
we
can
just
kills
the
old
ones
and
move
forward
with
the
one
that.
B
A
All
the
changes
in
it
I
know
that
down
you,
you
getting
the
pr
ready
and
me
then
reviewing
it,
then,
and
seeing
that
we
can
get
this
in.
B
Yeah
so
there's
a
the.
Let
me
I'm
going
to
stop
talking,
because
I
can't
do
two
things
at
once:
I'm
gonna
get
these
links
into
the
documentation
before
I
forget
no.
A
A
B
B
B
B
Okay,
so
on
2925,
I'm
gonna
close
these
right
now,
but
on
29.25.
B
In
my
original
comments,
I've
just
got
a
little
punch
list
there
and
so
just
to
give
you
some
context.
As
you
go
over
this,
the
first
one
is
Vitae
doesn't
like
that
inside
the
toolkit
inside
the
create
Vector
function
or
in
the
in
the
lib
somewhere
inside,
create
fetcher
there's
a
require
statement
that
was
put
in
no
yeah
I.
Don't
it
was
put
in
I've
got
it
linked
in
here,
but
it
was
put
in
to
provide
better
feedback
about
graphql
WS
not
being
installed
as
a
dependency.
So
we.
A
A
B
That's
one
and
then
the
the
second
one
is
that
graphical.min.css.map
isn't
generated
right.
I
was
so.
My
approach
to
this
was
just
to
generate
the
exact
same
files
with
the
different
build
system
that
was
that's
all
I
was
trying
to
do
and
then
also
make
end
to
end
work.
So
I,
don't
think
that
this
is
a
big
deal.
I,
don't
think
that
anyone's
looking
at
the
netlify
dev
build
and
trying
to
use
the
CSS
Source
Mouse,
but
I
wanted
to
note
it
here,
because
it
was
an
inconsistency.
B
Those
are
the
two
like
the
two
sort
of
outstanding
issues
outside
of
the
work
that
Ricky
was
doing
to
get
it
to
get
this
into
integrated
into
like
the
full
build
system.
I
believe
they
were
trying
to
like
modify
the
root
package
Json
so
that
like
build
bundles
was
you
know
doing
something
similar
I
I
didn't
really
follow
it
that
closely.
So
those
two
things
that
I
mentioned
are
like
the
ones
that
like
need,
that
you
may
be
able
to
help
just
confirm,
confirm
or
fix.
B
So
those
are
the
two
big
ones
and
then
also
the
rest
of
it.
I
don't
like
I
said:
I,
don't
I
need
to
reread
what
Ricky
was
attempting
to
do
here
before
I
can
feel
confident
about
talking
about
it.
Let's
see.
A
Yeah
I
need
to
take
a
look
at
the
required.
One
could
be
yeah,
that's
a
good
catch.
It's
gonna
be
hard
with
what
I
need
to
look
at
that.
B
A
A
Awesome
yeah,
I,
I,
didn't
like
the
the
only
thing
I
wanted
to
talk
about
was
like
what
or
like
a
chicken
with
the
the
bookstreams
that
are
going
on.
I,
certainly
don't
have
an
access
work
stream
that
I
really
own.
Currently
so
I
don't
have
an
update
to
give
so
I
can
I
can
catch.
B
At
our
at
our
last
meeting,
we
we
talked
about
two
things
right,
the
the
the
the
primary
sort
of
goals
for
us
were
going
to
be
Monaco
and
we're
going
to
be
the
visual
operation.
Builder
I
have
a
ton
to
say
about
the
visual
operating
operation.
Builder
I
also
have
observations
about
the
Monaco
situation,
so
Tim
Hall
excuse
me
from
Postman
was
gonna,
take
a
crack
at
Monaco
in
graphql
or
in
graphical
after
a
few
weeks.
I
think
that
was
the
October
meeting
that
we
talked
about
that
yeah.
B
A
B
Prototype
I'd
love
to
help
out.
If
I
can
I
didn't
hear
from
Tim
I
I,
he
just
seems
very
busy,
but
I
did
Weeks
Later
early
November
mid-november
I
was
filling
out
my
Grant
application
for
the
graphql
foundation
and
so
I
I
checked
in
again
and
didn't
get
a
response.
So
I
asked
doc.
B
I
just
checked
in
with
Doc
I
said:
hey
I'm,
filling
out
the
my
grant
application
and
I'd
love
to
include
Monaco
as
something
that
I
would
like
to
work
on,
but
I'd
like
to
get
a
sense
of
like
where
you
folks
are
at
with
it
or
or
what
was
going
on
and
she
didn't
have
an
update
from
Tim.
B
So
so
I,
don't
that's
what
I
know
about
Monaco
like
there
hasn't
been
a
PR.
There
hasn't.
A
That
I
would
assume
that
there's
still
progress
have
been
made.
If
we
don't
hear
back
sadly,
but
so
it
is.
B
So
that's
that's:
Monaco
I
took
a
swing
at
it.
I
didn't
get
very
far.
It
is
complicated.
It's
you
know
the
way
that
the
the
just
code
mirror
in
general.
The
way
that
it
works
is
just
fundamentally
different,
like
the
the
code
mirror
touches
your
code
base
in
ways
that
Monica.
A
B
I
can
imagine
it's
equally
difficult.
If
you
know
code
mirror
really
well
to
then
try
to
understand
what
what
Monaco
is
doing.
I
don't
know
if
we
have
any
unicorns
out
there
that
you
know
magically
understand
react
integration
of
of
both
of
them,
but
it
might
take
someone
like
that
or
someone
who
just
has
it
in
an
inordinate
amount
of
time
to
dedicate
to
getting
to
getting
that
that
across.
B
But
it
is
going
to
be
very
difficult,
so
it
wouldn't
be
nice
to
see
it'd
be
nice
to
see
Monaco
like
advancing
faster,
but
it's
understandable
that
it's
not
happening.
Visual
operation,
Builder.
B
I
continue
to
iterate
over
the
design
and
build
on
the
design
and
the
Prototype.
That's
online
is
sort
of
in
and
out
of
a
working
State,
because
I'm
just
iterating
so
quickly,
I
am
not
getting
feedback
from
the
community,
which
is
been
kind
of
a
bummer.
There
were
load.
There
was
loads
of
enthusiasm
right
earlier
in
the
year
to
really
make
this
a
core
piece
of
graphical
version.
B
Two,
you
know
we
didn't
have
time
to
get
it
in
and
then
you
you
got
the
Explorer
plugging
in
right,
which
was
great
and
so
I.
Think
what's
I'm
guessing
what's
happened
was
people
are
perfectly
happy
with
the
Explorer
plug-in,
except
when
they're
not,
and
there
are
a.
B
In
the
repository
where
they're
not
you
know,
I
have
I
I
have
plenty
of
design
reasons
why
I
don't
like
it,
but
it
does
work.
You
know
for
most
people
it
works
just
fine,
it's
comfortable
for
them,
they're
familiar
with
it
right.
The
docs
experience
is
there
with
the
docs
plug-in
and
you
get
Explorer
in
there
and
you've
got
something.
That's
working
and
that's
great.
So
that's
my
guess
for
why
the
level
of
enthusiasm
just
hasn't
been
so
great
for
the
visual
operation.
Builder
I'd
love
to
hear
any.
B
B
Ricky
and
I
have
discussed.
Thomas
was
asking
folks
that
are
part
of
the
larger
working
group
asking
someone
that
that
attends
that
meeting
you
know
regularly
to
bring
this
up
just
like
hey.
We
have
a
couple
of
graphical
initiatives
that
we're
really
excited
about,
but
we
just
we
need
more
bodies.
You
know
we
need
more
feedback,
we
need
more
engagement,
so
Ricky
and
I
have
talked
about.
B
You
know
asking
or
approaching
them
to
bring
it
up
at
that
level
again,
because
I
don't
believe
that
graphical
has
been
discussed
at
that
level
since,
like
earlier
in
the
year
when
Tim
was
deep,
diving
on
the
design
and
the
the
plan
for
for
version
two,
so
that's
really
the
only
like
suggestion
that
I
have
for
get
getting
more
feedback,
and
this
isn't
I'm
like
this,
isn't
it
there
were
two
people
doing
this.
It
wouldn't
be
enough.
B
A
Yeah
yeah
I
think
one
word
like
you
say
could
even
be
like,
maybe
maybe
also
turn
it
around,
like
us
being
more
proactive
and
reserving
some
time
for
it
at
a
graphical
working
group
meeting
to
present
this
to
just
have
the
the
audience
for
this.
A
For
that
then
I
would,
or
it
should
probably
be
like
a
real
like
proposal
where
we
say
yeah.
This
is
the
the
more
or
less
final
thing
that
we're
settling
on
now
and
it's
it's
like
now
in
the
process
of
just
ironing
out
potential.
A
Things
that
could
go
wrong
or
pointing
out
things
that
are
not
working
and
proposal
like
basically
identifying
any
blockers
and
seeing
what
comes
back
from
that
and
if
everybody's
happy
then
just
do
it
I
think
eventually
we'll
get
more
feedback
when
there
is
actually
like
a
plugin
that
users
can
just
drop
into
the
graphics.
A
B
B
It
might
not
be
I
know
it's
not
performant
right,
it
hasn't
been
optimized,
there's
that
it
might
not
pattern
wise
might
not
fit
in
like
there's
a
lot
of
reasons
why
the
work
that
I've
done
has
been
scoped
in
the
Prototype
world
and
not
necessarily
reflective
of
like
the
way
that
this
final
product
is
going
to
work.
So
I
would
say,
even
if
the
work
that
I've
done
was
like
right
on
track,
it's
still
only
50,
there's
just
you
know.
There's
the
we've
talked
about
this
before
right.
B
We've
talked
about
the
the
the
code
mirror
versus
Monaco
situation
and
how
you
interact
with
that
and
how
it's
different
enough.
We
talked
about
this
Patrick
brought
this
up
two
months
ago,
at
the
the
to
the
meeting
two
months
ago,
where,
like
theoretically,
you
could
write
an
interface
on
top
of
the
editor
stack
that
makes
the
actual
editor
irrelevant
right.
You
have
an
API
that
you
talk
to.
That
knows
how
to
then
talk
to
code,
mirror
or
talk
to
Monaco,
but
that's
just
another
gigantic
vocal
work.
That
seems
totally
unnecessary.
A
B
We
came
to
an
agreement
like
well:
let's
go
with
Monica
well
with
Monaco,
you
end
up,
then
this
like
rabbit
hole,
sort
of
expands
right.
If
we
decide
like
we're,
just
definitely
going
to
go
with
Monaco.
Well,
then
that
means
that
we
have
all
of
the
there's
still
Monaco
graphql
work
that
needs
to
get
done
like
not
not
UI,
not
editor-wise,
but
Monaco
graphql
work
that
needs
to
get
done.
B
We
have
to
figure
out.
We
have
net
new
features,
then
right.
So
one
thing
that
people
love
about
the
code
mirror
setup
and
the
explore
plug-in
is
they're
linked
together.
You
can
click
inside
of
code
mirror
to
get
you
know
and
then
bring
up
the
correct
documentation.
Panel
I
haven't
figured
out
how
to
do
that
with
Monaco.
Yet.
A
B
Imagine
imagine
it's
pretty
complicated
but
like
I
haven't
even
gotten
a
shot,
so
it's
like
a
net
new
thing.
So
the
whole.
My
point
is
that,
like
we've
decided
we're
gonna
go
with
Monaco,
but
we
really
haven't
like
addressed
that
so
getting
the
design
for
the
plug-in
like
fully
validated
or
at
least
partially
validated,
is
difficult
because
we're
playing
in
kind
of
like
a
soupy
like
ephemeral
world,
where
the
pieces
are
at
different
stages
of
completion.
A
A
B
I
mean
I
think
there
is
there's
UI
work
that
we
can
do
like
design
UI
work
in
the
in
the
visual
operation,
Builder
that
we
can
do
like
that's.
Basically
what
I've
been
doing.
It's
just
it's
UI
work.
B
Does
it
have
all
the
bits
that
it
needs,
but
you
know
more
basic
kind
of
stuff:
the
integration
between
the
two
and
the
docs
layer,
that
is
a
part
of
the
visual
operation
Builder.
Whatever
that
docs
view
looks
like
whether
it's
like
a
popover
or
dialogue
or
whatever
that
ends
up
being.
That
is
going
to
be
the
bit
that
is
either
gonna
need
to
be
integrated
into
Monaco
editor,
so
we
would
detain.
We
need
to
number
one
ensure
that
we
can
do
that,
which
I
believe
we
can
Apollo
sandbox.
Does
that
right?
B
I
know
that
in
Monaco
you
can
grab
onto
a
field
or
you
can
grab
all
you
can
you
can
like
click
on
a
field
and-
and
you
can
use
Monica
graphql
to
get
all
the
data
you
need
to
open
up
the
right
panel
like
inside
documentation,
but
I.
Don't
know
how
it
works
like
I,
don't
I
know
you
could
do
it
I
just
don't
know
how
it
actually
works.
So
I
I
again
like
you
know
the
way
that
my
brain
works
is
like.
B
B
You
know
a
lot
of
new
ideas
that
I
started
exploring
this
week
for
arguments,
because
that's
one
of
the
big
pieces
that
isn't
described
well
in
the
graphql
V2
design
is
like
what
do
arguments
really
look
like
if
we're
going
to
attempt,
as
close
to
a
one
to
one
feature
parody
with
the
existing
one
graph,
Explorer
then
having
input
Fields
inside
of
the
new
one?
Is
that's
a
that's
a
big
one.
You
know
the
ability
to
just
like
toggle
an
argument.
B
That's
a
string
or
a
number
or
an
enum
and
just
get
the
appropriate
field
next
to
it.
I
think
that's
a
really
important
feature
that
we
should
try
to
keep
as
one
to
one
as
possible.
So
I'll
have
some
new
ideas
for
that.
But
again,
just
given
the
complexity
of
the
The
View-
and
you
know,
big
schemas
make
this
even
more
challenging
like
how
do
you
fit
inputs
in
there
in
a
way
that
that
aren't?
B
You
know
like
disruptive
to
to
the
experience
so
there's
there's
work
there
that
I'm
doing
that.
I
will
continue
to
to
do
and
and
I'll
share
that
figma
file.
Hopefully
sometime
really
soon
I
just
want
to
make
a
little
more
progress
on
it,
but
really
it's
irrelevant
because
it's
it's
not
like
it
doesn't
fit.
B
The
current
design
system
and
I've
done
that
intentionally
right,
but
once
I
once
I
figure
it
out
and
it's
and
people
play
with
it
and
they
think
that
they,
like
it
like
I,
think
it'd
be
pretty
simple
to
jump
into
that
original
file.
A
A
Okay
I
mean,
given
that
we
already
have
some
action
items
and
that
it's
Christmas
and
holiday
season
coming
up.
Yeah
I
wouldn't
put
down
anything
for
Monaco
or
the
visual
operation
Builder.
Now
as
part
of
this
meeting
and
regroup
next
year
and
see
where
we,
if
somebody,
if
something
happens,
maybe
something
in
Monaco
did
get
on
we'll
see
and
then
we
regroup
and
we
assess
where
we
want
to
go
from
from
there
in.
A
Sounds
good,
do
you
have
anything
else,
I,
don't.
B
A
I
I
I
was
about
like
okay.
If
at
the
50
minute
Mark
nobody's
here,
then
I'm
gonna
drop
yeah,
then
so
you
you.
A
Okay,
awesome
then
yeah
I
have
a
merry
Christmas,
happy
holidays
and
see
each
other
in
the
next
year
and
yeah
and
hear
from
each
other
like
async,
on
GitHub
and
Discord.
All.