►
From YouTube: Incremental Delivery Working Group - 2023-08-07
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
A
C
A
I
think
only
three
more
days
my
wife
was
visiting
her
mother,
and
so
they
were
actually
I.
Think
three
weeks
here
and
I'm,
just
picking
them
up.
B
And
this
is
that's
apnea
Hill.
A
C
Good
yeah,
thanks
for
joining
yeah
yeah
I,
haven't
had
much
time
to
work
on
any
of
the
stuff
but
thought
that
we
would
start
could
these
meetings
started
up
again,
I
guess:
first
Angie
you
reached
out
to
me
about
making
these
meetings
more
formal,
like
the
working
group
agendas
and
transferring
the
repo
to
be
once.
B
B
I
have
a
vague
feeling
that
I
read
at
one
point
on
like
one
of
the
maintainers
boards
that
if
you
move
a
project,
it
doesn't
move
the
discussions,
but
that
might
have
been
an
old
thing
and
maybe
they
fixed
that
now
I
don't
know
I
meant
to
test
it,
but
I
haven't
got
around
to
it.
Yet.
C
B
Or
maybe
it
was
the
it
was
the
redirects
for
the
discussions.
I
think
was
the
issue
so.
C
Okay,
yeah
I,
guess
we
can
we
can
test
it.
So
do
you
want
to
take
care
of
that,
or
do
you
want
me
to
do
something.
B
C
Okay
and
and
then
I
mean
like
in
that
repo,
we'll
set
up
the
agenda
files
and
and
that
stuff.
B
Yeah,
absolutely
I've
got
a
template
for
all
that,
so
we
can
just
basically
copy
the
template
across.
A
So,
what's
what's
the
general
status
at
the
moment
of
the
do
we
have
the
spectacs
already.
C
Delayed
execution,
we
talked
about
it
at
the
main
working
group
meeting
and
I
I
feel
like
the
the
takeaway
there
was
that
in
the
spec
we
want,
we
want
it
to
be
flexible
enough.
That
implementations
can
do
either
and
we
want
to
keep
the
text
as
simple
as
we
can.
C
We
didn't
really
decide
one
way
or
another.
Definitely
the
text
shouldn't
do
early
execution
or
the
text
should
do
delayed
execution
I.
My
like
general
feeling
is
that
I
feel
like
that.
We
could.
C
A
C
A
And
then
I
could
also
send
you
feedback
on
or
help
a
bit
on
that
in
the
when
you
start
specifying
it.
C
Yeah
like
not
trying
to
separate
them
out
and
because
it's
separate
yeah
I,
don't
think
that's
changed.
C
C
So
that's
where
I
think
that
some
of
the
sticking
point
is
for
moving
forward
with
that.
So
that's
why
I
want
to
like
spend
some
time
going
through
it
and
maybe
trying
to
simplify
it.
I
haven't
done
it
yet.
I
haven't
like
reviewed
that
spec
PR.
Yet,
but
that's
that's
right.
He
has
both
a
graphql.js
implementation
and
the
effect
PR.
A
Pierre
reviewed
that
a
bit
like
this
is
because
you
say
you
haven't
read
through
it,
but
you
that
is
the
that's
basically
the
I.
Well,
it's
basically
specifying
the
idea
we
have
agreed
on.
A
Oh
sorry,
so
you
you
haven't
reviewed,
this
expect
the
audience,
but
it
should
in
general,
implement
the
general
idea
we
had
in
the
discussions
or.
A
A
B
Yeah
I
did
I,
did
a
cursory
look
over
it,
but
it
has
quite
a
few
patterns
that
we
don't
use
in
the
graphql
spec
at
the
time
that
I
I
reviewed,
which
I've
I've
discussed
with
Yakov
a
little
bit
since
then,
but
broadly
like
it
does
mutation,
and
then
it
has
to
sort
of
undo
side
effects
in
some
circumstances,
and
things
like
that
which
obviously
we
don't
have
anything
like
that
in
the
spec.
Currently,
the
the
approach
that
doesn't
do
early
execution
doesn't
need
any
of
that.
B
There
aren't
any
side
effects
that
need
to
be
undone,
because
everything
just
falls
out
of
the
algorithm
just
naturally,
so
it
just
uses
all
the
traditional
error
handling
that
the
algorithm
already
has.
B
So,
there's
that
he
is
now
because
he's
seen
my
I
I
did
an
implementation,
do
some
very
early
spec
edits
for
the
Deferred
execution
approach
and
one
of
the
issues
that
I
had
with
that
is
we
needed,
like
macros,
effectively
there's
bits
of
code
that
need
to
be
called
in
multiple
places
like
an
algorithm,
but
they
also
need
access
to
some
kind
of
shared
State
like
cash
or
a
queue
or
that
kind
of
thing.
B
So
I
I
built
up
some
macros,
which
again
is
a
new
technique
that
isn't
currently
in
use
in
the
spec.
So
at
some
point,
I
need
to
talk
with
Lee
and
see
if
there's
a
better
way
of
of
modeling.
That
approach,
but
I
think
that
what
yaakov
has
done
now
is
he's
tried
to
build
my
macro
system
into
his
PR,
which
is
interesting
so
that
might
get
around
some
of
the
issues
that
we're
seeing
demo
but
I'm
not
happy.
B
C
Yeah
and
yaakov
also
has
the
graphql
jspr
that
implements
the
new
response,
format
and
I
think
that
I
want
to
work
with
him
on
trying
to
get
that
merged,
because
we
still
have
like
the
old
response
format.
C
That's
what's
in
graphql.js
the
in
the
main
branch
right
now,
so
so
that
PR
also
does
early
execution,
but
I'm
not
like
too
concerned
about
early
versus
delayed
in
graphql.js
I
feel
like
if
we
do
or
like
whatever
we
do,
like
probably
someone's
gonna
want
the
other
one,
and
then
we
could
like
work
with
the
community
on
like
how
exactly
we're
gonna
we're
gonna.
Have
it
like
as
long
as
the
spec
allows,
both
and
we're
still
in
like
Alpha
versions.
C
A
A
Oh
yeah
I
still
also
think
that
so
probably
what
we
will
do
is
you
can
give
the
user
a
kind
of
tell
us
what
your
default
should
be
like
early
execution
or
the
date
execution,
and
then
you
can
opt
into
the
other
one
on
a
per
resolver
basis
like
annotated
Maybe,
because
they
they
could.
There
can
be
cases
like
I,
think
Benji
date
out,
one
with
postgres,
where
one
or
the
other
could
be
the
better
better
option.
So.
A
C
Congrats
yeah,
thank
you.
What
was
that.
A
A
C
C
Yeah
so
I'll
check
in
with
Yakov
I'll
see
about
moving
forward
the
graphql
JS
changes.
I
really
want
to
get
the
new
format
out
somewhere
that
people
can
start
using
it.
Yeah.
A
C
A
No,
no,
no,
we,
but
it's
not
not
that's
why
I
say
we
have
done
several
layers
like
first
is
I
put
it
in
hot
chocolate,
but
then
it's
the
graphical
ID
and
then
we
have
it
also
in
relay
and
I
have
looked
at
it
at
the
moment.
The
way
we
do
it
is
we
actually
support
every
iteration
or
the
proposal
that
we
have
even
the
the
first
one
with
the
labels
and
stuff.
A
That's
that's!
That's
what
we
have
now.
C
A
Published
before
the
like,
you
get
the
nobody
and
I
can
pass
on
to
there
to
you
I.
We
have
it
in
our
workflow
material.
It's
not
like.
We
have
it
everywhere,
but
I
can
give
you
a
link.
C
Because
once
we
get
the
new
response
format
in
graphql
JS,
then,
if
you're
using
graphql.js
you're
going
to
need
the
same
translation
layer
if
you're
using
it
with
relay.
C
Okay
sounds
good,
that's
that's!
All
I
really
have
for
now.
C
I
guess
Benji.
Let
me
know
when
you're
ready
for
me
to
transfer
the
repo
and
I
can
do
that
and
then
you
can
set
up
the
the
agenda
templates.
B
Yeah
I
think
you
can
just
go
straight
ahead
and
do
that
now.
I
did
test
it
whilst
we're
on
the
cool
and
everything
seems
to
work.
Fine
with
redirecting
I
even
moved
out
across
organizations,
and
it's
still
redirects
just
fine
so
should
be
good,
go
ahead,
transfer
it
to
graphql
and
then
we'll
we'll
get
that
get
all
the
agendas
copied
over
and
that
sort
of
stuff
and
yeah.
We
should
start
taking
notes
as
well.
What
we
do
for
the
main
graphql
working
group
now
is.
B
We
just
have
a
single
notes,
file
on
Google
Docs
that
we
keep
adding
to
so.
If
you
want
to
be
the
host
of
that,
it
would
be
perfectly
fine
or
I
can
do
so
up
to
you
and
then
we'll
add
that
to
the
agenda
and
just
use
that
going
forwards.
C
C
C
I'm
not
100
sure
yet,
but
I
am
gonna.
Try
to
make
it.
A
C
B
Don't
know
if
he
is,
he
said
he
was
gonna
he's
hoping
to,
but
I
haven't
heard
an
update
of
of
since
then,
because,
obviously,
there's
there's
complexities
but
yeah.
He
certainly
was
trying
to
get
the
wheels
in
motion
so
that
he
would
be
able
to.
A
Yeah
I
I
would
think
the
maybe
we
could
also
arrange
like
I,
don't
know
a
working
group
dinner
or
something
like
that.
A
Although,
like
you
have
to
be
really
careful
in
some
in
San
Francisco,
now
it's
like
a
lot
worse
and
if
you
go
into
the
city.