►
From YouTube: GraphiQL Working Group - 2022-06-14
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/
B
All
right,
I
got
my
I
good.
I
got
my
headphones
in
and
you
can
probably
hear
it
they're
doing,
there's
a
maintenance
crew
outside
my
building
doing
landscaping,
so
it
they've
got
a
blower
going
right
now,
so
it
might
go
up
and
down.
A
Okay,
so
we
can
maybe
do
today's
session
fairly
quick.
Did
you
see
the
talk
that
thomas
and
I.
B
Yeah
I
I
watched
all
of
it
tim.
I
listen.
I
really
wish
I
could
have.
I
was
two
miles
away
the
whole
time
two
miles
away
from
downtown.
Where
I
live.
I
really
wish
I
could
have
been
there,
but
I
just
in
the
last
five
weeks,
my
my
group
of
friends
and
I
have
been
very
conscious
and
covered
safe,
no.
B
Covet
for
two
years
out
of,
like
my
you
know
my
my
group
of
friends
and
in
the
last
five
weeks,
two
people
got
covered.
Oh
so
something
in
austin
I
just
I
was
kovaci
about
coming
downtown
and
seeing
everybody,
but
I
I
watched
every
as
much
as
I
could.
Virtually
it
was
great
t-shirts
were
incredible.
I
wish
I
would
have
been
able
to
come
down
and
grab
one.
I
thought
you
guys
did
great.
It
was
awesome.
It
sounds
like
the
conference
was
really
good
in
person.
A
Yeah
I
mean
it
was,
was
great
to
to
see
everyone.
It's
it's
not
a
big
country.
It
was
not
a
big
conference
which
was
good
because
with
that,
like
I
think,
kubecon
was,
it
was
also
hashtag
cubecovet
and
at
least
it
wasn't
too
big
here,
but
someone
and
two
people
in
our
team
got
covered
afterwards.
So
two
people
in
austin,
yes
from
our
team.
B
A
Anyway,
yeah,
let's
quickly
talk
because
we
might
just
be
able
to
do
this
meeting
here.
Charter,
so
thomas
has
implemented
the
new
design
with
the
existing
implementation
without
the
new
dock
explorer.
Obviously
right
and
the
next
goal
is
to
get
that
into
a
state
that
it
can
be
released.
It
will
still
take
a
few
weeks,
but
that's
okay,
and
we
saw
that
you
already
got
quite
far
with
your
implementation.
B
Yeah,
it's
so
I've.
I've
really
been
struggling
with
sort
of
my
original
intention
with
getting
involved,
which
was
just
to
to
be
able
to
build
out
like
a
simple
component
library,
so
that
other
people
would
be
able
to
quickly
prototype
and
iterate
over
the
new
doc
explorer
design,
because,
like
a
lot
of
other
people,
I'm
skeptical
that,
as
it's
currently
designed
in
figma
that
it's
gonna
work,
it
needs
tweaks
right,
and
so
it
needs
to
be
prototyped.
So
I
the
whole.
B
B
I
started
having
a
really
good
time
with
it
and
and
it
and
it
it
grew
into
like
an
actual
prototype
and
as
far
as
I'm
concerned
at
this
point
you
know
what
I
call
pathfinder
just
because
the
docs
explorer
thing
was
it
was
getting
very
confusing.
So
I
wanted
to
compartmentalize
it.
What
I
call
pathfinder
and
what
is
like
the
prototype
for
the
new
dock
explorer,
I
think
it's
ready
for
for
people
to
at
least
start
playing
with.
B
I
know,
there's
a
small
number
of
people
that
have
seen
the
prototype
and
have
sort
of
played
with
it.
I
I'm
not
sure
what
sort
of
plan
needs
to
be
put
in
place
in
order
to
like
properly
test
whether
or
not
it's
gonna
meet
the
needs
of
you
know
version
two
but
it'd
be
nice
to
formalize
something.
I
know
I
told
you
a
month
ago
that
I
was
going
to
put
together
a
list
of
design
needs
and
and
then
of
course
I
just
totally
got
carried
away
now.
B
B
You
can
load
up
different
schemas
and
you
can
explore
them
and
you
can
play
with
it
and
you
can
decide
whether
or
not
it's
going
to
work,
and
so
I'm
I
mean
there's
loads
of
there's
loads
of
bugs,
mostly
related
to
monaco
and
how
the
editors
and
the
models
are
loading
and-
and
so
I
think
it's
in
a
place
where
I
now
can
put
together
a
list
of
like
okay,
like
here's,
a
design
need
here's
a
design
need
there's
stuff,
that's
in
pathfinder
arguments
needs
to
get
iterated
over,
there's
a
number
of
design
needs,
and
so
I've
I've
got
to
do's
here
to
finally
put
together
that
list
that
we
talked
about
a
month
ago
and
I'll
I'll
put
that
together,
I
saw
on
the
github
discussion
that
julian
had
a
look
at
the
prototype
and
was
gonna
think
about
some
things,
so
I'm
gonna
formalize,
you
know
what
I've
identified
as
like
design
needs
that
it'll
get
figured
out
and
I'll
along
with
a
write-up
for
the
repository,
which
is
something
that
I
also
need
to
do
I'll
get
that
done
later
today.
B
A
Yeah,
I
just
spent
a
few
minutes
with
it
clicking
around
a
bit
and
it
already
looks
good.
I
think
that's
perfect.
So
what
we
could
say
is
that
you
create
this
list.
You
can
just
write
us
in
the
graphical
development
channel
in
discord
and
we
can.
I
can
coordinate
with
julian
that
he
has
a
look
there
and
designs.
The
missing
pieces,
basically.
A
And
then
we
can
use
this
as
a
way.
So
if,
if
you
could
enable
a
way
to
add
arbitrary
endpoints,
some
some
somewhere
like
in
a
tooltip
or
pop-over
model,
so
that
people
could
just
add
their
endpoint
and
try
it
out
and
then
we
could,
with
the
graphical
twitter
account,
we
could
tweet
about
it
and
say:
look
this
is
the
prototype.
A
Please
try
it
out
and
give
us
feedback
here
in
this
discussion,
github,
discussion
or
issue,
and
that
way
we
can
now
already
start
validating
the
concepts,
because
before
we
even
go
take
your
implementation
now
and
try
to
merge
it
into
the
main
graphical
ripple.
In
the
meantime,
we
can
do
all
of
these
experimentations
already
right.
B
Yeah,
this
is
just
to
be
again
to
be
totally
clear.
None
of
this
code
is
meant
to
get
merged
right,
it's
simply
to
validate
the
design.
I
don't
have
any
plan,
I'm
not
making
that
move.
That's
you
know
it's
really
just
to
validate
the
design
to
work
out
just
the
kinks
in
it,
because
I,
I
think
that
it's
just
a
it's
a
radical
change
and
it
just
needs
to
get
explored.
I
I've
never
built
a
product
that
had
such
a
controversial
change
to
such
a
such
a
fundamental
piece
of
its
architecture.
B
So
that's
all
this
is.
This
is
just
really
design
validation.
B
Like
input
for
sure
on
my
screen
here
about
the.
B
B
If
there's
an
input
here
for
people
to
just
plug
in
their
urls
as
long
as
it's
as
long
as
they're
open
for
introspection
like
that,
would
work
yeah
so
I'll.
Just
I'll
just
stick
an
input
in
here
and.
A
A
You
will
just
need
to
make
sure
that
they
could
add
headers
right
if
they
need
an
authorization.
Header.
B
Yeah
barry
gold
is
in,
I
don't
know
so.
The
last
time
you
looked
at
this,
I
don't
know,
I
don't
know
how
much
I
I've
just
been
kind
of
like
blazing
through
this
right,
like
all
my
commits,
are
messy
and
I
don't
I'm
sort
of
lost
in
terms
of
the
timeline.
So
I
don't
know
what
you've
seen,
but
currently,
I
believe
the
last
version
you
saw
and
the
one
that
you
shared
with
everybody
during
the
conference
had
didn't
have
like
a
variables.
Editor
had
like
the
easy
variables
thing
right.
B
It
had
like
the
inputs
that
you
can
select
so
now
they're,
both
in
and
so
just
as
an
example.
Here,
we've
added
using
pathfinder
I've
added
a
variable.
You
can
add
some
more
right.
So
it's
automatically
giving
me
in
the
editor
it's
giving
me
what
it
thinks
I
need,
and
then
I
can
toggle
down
here
and
I
also
automatically
get
this
right.
So
I'm.
B
I'm
a
really
big
fan
of
this
interface.
I
think
that
there's
little
reason
to
my
own
personal
opinion
is
that
no
one,
I
don't
think
anyone's
ever
copying
and
pasting
out
of
the
variable,
even
the
current
one.
I
don't
think
people
are
copying
and
using
this
code
anywhere.
So
I
wonder
why
I.
A
The
byron
talked
about
with
lee
byron
and
I
think
we
would
probably
choose
the
json
input
as
default,
taking
it
out
of
the
code
in
the
code.
I
think
that
is
a
use
case.
We
need
to
support
yes,.
B
Sure
I
just
I
wonder,
that's
a
good
point.
Okay,
so
so
that's
in
what
was
I
going
to
show
you,
oh
headers,
so
this
ui
is
in
right
with
the
inputs
for
here.
So
this
is
closed
like
I
can
definitely
get
this
in
the
other
thing
that's
in
is
tabs
in
so
oops.
B
Right
so
that's
in
and
that's
working,
and
so
it's
it's
like
you
can
actually
play
with
this.
You
can
actually
like
move
around
and
test
it.
The
way
that
I
think
people
would
normally
use
it
right.
It's
basically
it's
it's
feature,
parity
with
the
existing,
the
existing
version
in
terms
of
like
the
just
the
fundamental
pieces,
so
I
can
get
the
headers
in
and
then
the
button
and
then.
B
B
Well,
if
you
think
that
it
it's
gonna,
confuse
people
and
I'll
defer
to
you,
I'm
happy
to
just
make
it
say,
docs
or
explore,
or
whatever
like
for.
B
A
B
B
A
A
B
Is
just
the
icon
for
pathfinder,
so
one
thing
I
did
here
is
I
I
was
having
a
lot
of
trouble
with
with
the
drag
bars.
I
know
in
the
demo
right,
so
here's
here's
thomas's
demo,
that's
up
and
running.
B
The
drag
bars
work
like
vs
code,
like
you
guys,
planned
right.
They
work
in
like
a
very
vs
code,
sort
of
way
where,
if
you
snap
it
over
all
the
way.
B
I
don't
know
why
this
is
not
working
right.
It
snaps
over
in
mine.
It
just
doesn't
work
like
that,
because
I
was
having
issues
with
those
drag
bars.
I
think
I
fixed
it
now.
I
can
go
back
and
change
it.
So,
basically,
when
you're
on
the
top
here,
you're
at
just
the
editor
all
by
itself,
which
actually
also
runs
so
here's
just
the
inline
editor
like
this
is
this
can
just
be
dropped
in
anywhere
and
you
feed
it
a
schema
and
it
does
its
thing.
B
A
I
mean
optimally,
you
just
implement
it
as
we
planned
it,
but
I
think
it's
not
too
bad,
because
the
idea
is
really
if
that
thing
is
because
you
have
a
boolean
state
right
that
you
put
into
two
items
here
that
are
selected.
But
the
idea
is
that,
if
nothing
is
selected,
then
if
you
would
click
on
pathfinder
on
the
left
again,
it
would
just
be
unselected.
A
Yeah,
okay
and
just
the
icon
that
we
have
in
the
design,
but
that
is
not
the
most
important
one.
Whatever
it's
important
that
we
get
feedback
around
the,
so
the
biggest
hesitation
or
the
biggest
problem
might
be.
If
people
have
complex
queries,
deeply
nested,
complex
queries.
How
does
that
look
like?
B
Yeah,
I
think
it's
going
to
be
it's
going
to
be
a
challenge
right,
there's
a
there's,
a
level
of
simplicity
around
the
way
that
the
fields
are
collapsing
now
that
will
need
to
get
complicated
right
if
we're
gonna,
if
we're
gonna,
if
we're
gonna,
find
a
way
to
offer
incredibly
complex
queries
that
at
a
glance
in
the
explorer
makes
sense,
because
it
makes
sense
in
the
editor
we
don't.
You
know
like
if
it's
complex
but
over
here.
B
If
you
really
like
deeply
selecting
across
root
fields,
you
just
there's
just
way
too
much
over
here
and
yeah.
You
can
you
know
you
can
toggle
things
close
them
and
you
can.
You
can
have
it
make
sense,
but
in
general,
if,
if
you're
expanded,
all
the
way
down
to
your
selections,
it's
gonna,
it's
gonna,
be
difficult.
B
A
B
A
A
A
Of
course
it's
really
awesome
the
work
that
you're
doing
here
and
that's
when
thomas
said,
the
magic
of
open
source.
You
know.
B
Yeah
yeah
exactly
yeah
yeah.
Well,
it's
it!
This
is
sort
of
right
in
my
wheelhouse
right
this.
This
prototyping
thing
is
as
a
product
engineer.
It's
generally
like
the
first
thing
that
that
that
I
get
involved
with
right
just
to
kick
it
off
to
kick
it
back,
keep
things
back
to
designers.
I
guess
I
guess
that's
just
the
that's
the
the
you
know,
I
think
that's
going
to
be.
B
The
challenge
here
is:
there's
there's
really
a
lot
of
design
work
around
this
and
I
don't
know
if
the
right
place
to
do
that
is
in
figma
or
if
it's
in
some
version
of
a
prototype
right
depending
on
how
quickly
it's
gonna
need
to
get
iterated
if
you
and
julian
and
everybody
are-
are
still
gung-ho
about
sigma,
which
I
I
I
am,
I
think
that's
the
right
place
to
be
the
source
of
truth.
I'm
happy
to
do
like
to
work
in
figma
as
well.
B
I've
been
doing
plenty
of
work
in
figma,
just
sort
of
on
my
own
in
a
copy
of
the
the
figma
file
that
julian's
working
out
of
before
I
move
it
into
the
prototype.
So
if
there's
production
there's
like
design
production
work
that
julian
doesn't
want
to
do,
but
it
needs
to
get
done
inside
of
figma,
I'm
happy
to
to
do
that.
Work.
A
That
sounds
perfect
if
you
could
also
once
you
post
this
in
the
graphical
development
channel,
pause
the
link
to
your
figma
copy,
and
then
we
can
just
ping
julian
and
ask
him
what
he
thinks,
how
we
should
do
this,
but
I
think
giving
you
access
right.
Access
to
the
main
figma
is
also
a
good
option
and
you
can
subner
supplement
anything
that
is
missing.
B
Yeah
that
sounds
great.
There's
there's
a
lot
of
in
the
current
sigma
file,
your
figma
file,
there's
a
lot
that
you
know
we
talked
about
colors.
Remember
we
did
like,
in
my
initial
thing,
like
a
month
ago,
was
like
the
colors
and
those
alpha
values
and
how
difficult
that
is
to
work
around.
B
That's
probably
like
the
number
one
barrier
to
entry
to
getting
production
work
done
in
that
original
figma
file,
because
you're
not
working
with
a
static
palette
right,
there's
40
different
grays
in
that
original
figma
file
because
of
the
alpha
values
and
what's
behind
it,
so
I
step
one.
You
know
if
you
want
to
test
me
out
in
my
sigma
skills
step,
one
might
be
working
on
that
palette.
That's
gen!
That's
that's!
In
that
original
figma
file
and
reducing
it
to
a
static
palette.
A
B
Ten
color
palette
or
whatever,
but
I'm
I
would
be
happy
to
do
the
production
work
to
you
know
to
reset
it
inside
of
the
figma
file,
that's
going
to
unlock
a
lot
more,
a
lot
faster,
figma
iterations,
going
forward
and
I'll
I'll
bring
that
up.
When
I
share.
A
A
A
I
know
it's
much
more
convenient
for
julian
to
use
opacities
because
you
can
do
command
and
then
the
number
in
figma
that's
very
quick
to
design,
but
it's
not
very
versatile.
So
that's
something
to
look
into
and
then,
if
you
could
just
write
an
update
in
the
graphical
development
channel,
what
you
need
from
design.
A
A
Oh
good,
oh
god,
you
had
a
lot
of
progress
since
last
time,
so
it's
it's
open
source
project
and.
B
A
B
The
only
other
note
I
wanted
to
make
about
the
figma
thing
is
that
the
sigma
file
that
the
current
your
current
sigma
file
is
linked
to
the
graph
cdn
design
library
it's
linked
to
or
still
ate
right.
It's
linked
there
there's
shared
their
shared
components
that
are
happening,
so
we,
I
don't
know
how
you
guys
feel
about
that.
We.
B
May
want
to
separate
that
out:
yeah
yeah,
so
that
could
be
another
thing
that
that
I
can
get
done
rather
quickly.
B
Yeah,
those
are
the
two
big
sort
of
blockers
for
rapid
production.
B
A
Okay,
okay,
then,
I
think
we
can
leave
it
at
that
happy
to
see
all
the
progress,
and
I
will
also
write
a
message
with
julian.
Probably
first
need
to
get
him
into
this
channel
and
then
feel
free
to
write.
I
I'm
looking
into
that
channel.
Please
at
mention
me
all
the
time,
because,
as
the
graphql
discord
is
too
big,
I
don't
see.
I
cannot
activate
notifications
and
I
need
to
manually
check
the
channel
always
and
okay.
B
A
Great
thanks,
john
and
then
have
a
good
day
and.
B
Yeah,
it's
I
mean
we're
in
a
triple
digit
run.
I
don't
think
it's
going
to
go
below
triple
digits
for
a
while.
Now
it's
hot,
it's
very
hot
one.
Last
thing
tim,
I
just
wanted
to
say
congratulations
on
the
funding
round.
B
It's
very
very
well
done.
I
thought
you
guys
had
from
what
I
could
tell
remotely.
You
guys
had
a
really
great
presence
at
the
conference,
and
I
hope
they
got
a
lot
of
value
out
of
it.