►
From YouTube: GraphQL Working Group (Secondary, EU) - 2023-04-20
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
I
was
I
was
trying
to
work
out
what
the
is
was,
but,
of
course
it's
a
typo
foreign.
A
Well,
the
only
agenda
item
today
is
from
Michael,
so
I'm
gonna
see
if
I
give
him
a
remind
us
if
he's
coming.
A
But
I'm
off
topic,
or
slightly
on
topic,
I,
suppose
I'm
hoping
to
spend
a
little
bit
more
time.
Looking
at
the
incremental
delivery
stuff
again
next
week,
hopefully
so
yeah
I'd
love
to
chat
with
you
a
bit
more
about
it.
Then,
if
that's
good
or
just
see
what
you're
working
on
hey.
C
D
I'm
sorry
I
was
muted,
hey
folks,
sorry
for
joining
a
couple
minutes
late
are
we
gonna
have
a
limited
crew
today.
A
D
Oh,
so,
how
you
doing
Rob
good.
D
Guess
what
I
caught
up
on
notes
from
the
last
one
I'm
sorry
I,
missed
it?
I
was
on
vacation
the
first
time
in
a
while,
which
was
great,
but
nice
sounds
like
you're
all
making
some
good
progress.
A
D
A
Good
I
think
the
the
stream
interfer
stuff's
going
in
the
right
direction,
which
I'm
I'm
pretty
excited
about
I
think
there's
going
to
be
some
real
significant
improvements
coming
out.
Rob
and
I
are
sort
of
working
together.
Our
our
specs
have
become
aligned
such
that
we've
now
effectively
merged
them.
So
that's
that's
pretty
cool.
A
Absolutely
and
we've
got
yaakov
working
on
a
reasonably
similar
proposal
as
well
with
slightly
different
goals.
A
So
it's
it's
still
interesting,
because
we
can
still
play
them
off
against
each
other
and
see
you
know
Edge
towards
you
know,
Perfection,
as
it
were
always
good
to
have
competing
Solutions
I.
Think.
D
Yes,
yes,
I,
agree
well,
I
guess
we
should
maybe
give
a
few
minutes
to
see
if
we
can
get
Michael
to
get
through
this
agenda
that
he
had
put
up
on
the
board.
D
D
And
it
looks
like
it's
in
it.
Pretty
good
state.
D
Maybe
there's
just
an
ambiguity
or
something
that
he's
found
we're
talking
about.
A
D
I
think
I'd
seen
that
a
ping
came
in
but
didn't
have
a
chance
to
look
at
it
just
yet.
It's.
A
It's
just
a
little
bit
of
nonsense
in
the
spec
I
was
looking
at
the
case
that
we
use
for
things
like
camel
case
Pascal
case
Etc,
and
one
interesting
thing
for
me
is
that
all
of
the
fragment
names
are
in
camel
case
they're,
not
in
Pascal
case.
For
example,
I
was
wondering
if
you
had
a
particular
like
mental
model
behind
that
or
why
you
chose
that
particular
casing
convention.
D
C
D
Obviously,
the
the
convention
for
field
names
and
argument,
names
and
variable
names
is
all
camel
case.
Yeah
and
fragments
is
fragment.
Names
are
a
little
bit
in
an
in
between
space
there,
but
it
made
sense
to
me
to
kind
of
treat
them
more.
Similarly
to
a
field,
then
more
similarly
to
a
type.
C
D
Yeah
but
I
I'm
with
you
I've
seen
I've
seen
both
get
used
in
the
ecosystem
at
Large.
A
Yeah
I
was
just
doing
some.
You
know
consistency
stuff
and
seeing
whether
I
I
aligned
with
the
spec
in
what
I
was
doing,
and
it
was
the
the
one
difference
and
I
was
like
I
wonder
why
that
is
I.
Think
in
in
relay
like
fragments
almost
treated
like
Fields
like
you,
can
you
can
access
them
as
a
as
a
thing
right?
Some
of
the
time
I'm.
B
A
D
A
I
haven't
received
another
message
from
Michael:
I
did
say:
should
we
wait
which
he
has
not
yet
responded
to
so
I,
don't
think
he'd
be
too
bothered
if
we
push
it
to
the
next.
One
sounds
like,
even
if
he
makes
it,
he
might
be
a
little
bit
rushed
anyway.
D
Yeah
yeah
I'm
happy
to
hand
back
time
for
everybody.
If
he's
going
to
be
too
late
and
don't
want
to
rush
him,
you
can
let
him
know
that
we
can
just
talk
about
it
next
time
or
if
it's
something
that
it's
a
async
discussion,
we
could
always
have
an
async
description
around
it
and
then
build
up
more
context
for
the
discussion
at
Large.
D
Was
there
any
other
questions
on
the
casing
pieces
I
think
I
saw
you.
I
just
saw
your
message
that
you
mentioned
uppercase
bits
too,
because
we
will
sometimes
use
that
for
enum.
A
Yeah
the
enums
use
the
constant
case
and
yeah
fields
and
arguments,
as
you
say,
in
variable
names.
All
that
uses
the
camel
case.
It
was
literally
only
the
fragment
names
that
I
saw
that
were
kind
of
different
to
what
I
see,
not
just
in
my
own
code,
but
like
in
the
ecosystem
that
I
interact
with,
which
obviously
is
not
the
full
ecosystem.
A
It
I
started
thinking
about
it
because
someone
came
to
me
and
they
were
like
they
wanted
snake
case
for,
like
all
of
their
fields,
I
think
because
they're
consuming
it
from
a
different
language
and
they
were
like,
why
do
you
do
camel
cases
and
I
was
like
well
I?
Do
it
because
that's
what
the
spec
does
and
then
I
thought
I'll
have
a
look
at
everything
else
in
there.
D
Funnily
enough,
the
much
older
I
don't
know
what
Facebook's
code
base
looks
like
today.
It
may
very
well
use
a
healthy
amount
of
camel
casing,
since
that's
the
the
thing
that's
in
fashion
but
10
years
ago,
plus
code
base
used
a
lot
of
snake
case
and
since
the
first
since
the
sort
of
like
the
reason
for
graphql
getting
introduced
in
the
first
place,
was
to
be
as
much
of
a
natural
extension
from
that
code
base
into
a
query
language
as
possible.
D
In
and
when
like
doing
this
back
and
doing
the
first
version
of
that
thing,
where
I
was
like
I'm
gonna,
do
it
all
in
camel
case,
and
the
reason
was
because
camel
case
was
like
clearly
the
the
preferred
thing
for
at
least
the
JavaScript
community
and
probably
a
handful
of
other
communities
and
Nick
shock
was
just
like.
This
is
stupid,
and
this
is
going
to
confuse
a
bunch
of
people
internally,
because
they'll
have
to
translate
back
and
forth
I'm
like
yeah.
We
can.
We
can
leave
our
internal
one
snake
case
I.
C
B
D
Yeah,
that's
true:
we've
we've
effectively
evaded,
they
did
or
avoided
Uruguay
in
Hollywood.
Is
that
true?
Is
there
nothing
in
introspection
where
we
have.
A
Not
an
introspection,
I
think
that
definitely
is,
but
in
the
directive
arguments
I
don't
think
there
is
currently.