►
From YouTube: GraphQL Working Group (Secondary, EU) - 2023-03-16
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
B
B
A
B
Given
it's
meant
to
be
the
EU
meeting,
yeah,
oh
I
might
be
just
what
other
actually
groups
using
like
tissue,
59
or
otherwise,
either
using
UTC
or
wait
because
it's
it's
just
weird.
Everything
became
like
one
hour
earlier.
B
Actually
I,
it's
non-zero
chance
that,
like
some
people
who
who
Miss
with
me
actually
maybe
like,
then
you
said
I,
don't
know
what
time
zone
he's
in
so
like
I,
believe
it's
not
zero
chances
that
somebody
missing
some
of
this
meeting
just
because,
like
they
were
saving
think,
especially
since
it's
like
the
same
time
every
every
month,
except
like
with
one
or
two
weeks
when
it's
time
difference
between
us
and
Europe.
A
I'm
just
paying
Dennis,
he
may
not
be
aware.
B
Yeah
yeah
I
submitted
I
submitted
myself
to
agenda
no
thanks
for
reminding
me
yeah
well.
B
I
did
like
a
script
for
chat
kind
of
script,
for
graphql
JS
to
build
Canary
releases,
it's
kind
of
cool,
because
it's
like
conversation
one.
So
it
just
kind
of
comments
using
GitHub
or
xci
thing
as
like.
It
would
be
creative
if
we
just
have
like
issue
for
for
every
working
group
and
people
just
send
command
to
chat
to
some
like
both
to
it
themselves
and
what
would
be
what
would
say
like
so
much
time
and
confusion.
B
A
Okay,
Lee
sent
me
a
message
and
said:
he's
not
going
to
be
here
for
about
half
an
hour
as
far
as
I
see,
there
is
one
item
on
the
agenda
and
it's
mine,
which
I
am
happy
to
discuss.
If
you
want
to
discuss
that
now,
but
I'm
also
happy
to
plan
that
off
to
next
month's
primary
meeting.
A
Yeah
well
I
mean
essentially
okay.
Well,
let's,
let's
properly
go
into
the
meeting,
then
hello,
everyone
I
know
it's
just
the
pure
of
us,
but
we
need
to
follow
the
format,
so
we've
all
agreed
to
the
membership
agreement,
the
participation
guidelines,
the
contribution
guide
and
the
code
of
conduct.
B
Hi
I'm
Rob
hi
I'm,
one
fantastic.
A
I
guess
we
can
all
help
each
other
take
notes.
I'll
drop
a
link
to
the
Note
file
into
the
chat,
because
I
think
the
link
in
the
agenda
is
wrong
cool.
A
A
Okay,
then
yeah
I
was
at
the
last
one,
so
I
think
we
will
yeah
just
confirmed
Lee's
the
only
person
on
there,
so
I
assume
that
one
didn't
go
ahead,
yeah
in
which
case
we'll
skip
over
that
and
also
we'll
skip
over
the
previous
meetings,
action
items
and
just
jump
straight
into
it.
So
Express
graphql,
it's
still
receiving
issues
and
pull
requests
We've
effectively
suggested
that
the
graphql
HTTP
project
from
Dennis
is
now
the
primary
sorry
I'm
just
getting
a
message
from
Dennis.
A
Well,
we
just
started
the
agenda
item
for
talking
about
Express,
graphql
and
I
was
just
saying
that
your
implementation
now
is
the
the
reference
implementation,
since
it
implements
the
graphql
over
HTTP
spec,
but
that
the
old
Express
graphql
is
still
receiving
issues
and
pull
requests
comments,
and
things
like
that.
A
So
first
question
is:
is
it
actually
being
maintained?
Is
anyone
actually
like
pushing
out
new
releases
or
dealing
with
the
bugs
or
anything
like
that
in
it.
B
B
Good
all
good
yes,
so
we
made
decision
I,
think
it's
just
like
somebody
with
admin
rights,
just
just
like
post
everything.
Since
it's
a
totally
different
code
base,
it
does
make
sense
to
transfer
anything
leave.
People
might
we're
not
removing
repo
we're,
not
removing
forks,
so
we're
not
disrupting
anyone
in
a
sense,
yeah
and.
C
B
Just
like,
we
can
figure
out
the
steps
to
make
it
more
obvious,
like
calls
issues
for
commenting,
senses
deprecated
what
people,
even
if
it's
security
thing.
B
Wait
maybe
like
super
like
security
thing
can
be
a
problem,
but
in
reality
right
I'm
for
just
making
notorious
and
like
getting
duplication
notice
to
to
in
pen
package
and
like,
if
someone
volunteers
to
do
it,
it
would
be
great
if,
like
you
need
some
access
to
a
package,
I
can
run
a
command
right.
B
I,
don't
think
it's
even
worse
too,
like
put
effort
there,
since
we
have
a
bunch
of
other
stuff
that
deserve
attention.
C
C
B
Have
you
have
admin
right
rights,
so
you
can
call?
Yes,
yes
and
you
can
switch
it
to
like,
because
GitHub
have
with
like
weird
throws
GitHub
have
like
deprecation
mode.
It's
like
make
it
super
clear.
So
it's
like
say
this
trip
was
read
only
and
prevent
you
from
opening.
C
Yeah
archiving
yes,
but
yes,
I,
don't
think
I
can
do
that.
I
already
talked
about
that
and
I
think
I
don't
have
the
rights
to
Archive
any
repository,
but
once
I'm
I
have
taken
care
of
the
issues
in
PRS
I
can
just
ask
someone
to
close
it
up.
Yeah
you
Ivan
or
Lee,
or
whomever.
B
Yeah
and
same
with,
like
npm
package
I
can,
if
you
send,
like
you,
email
in
in
the
chat,
I,
think
since
we're
deprecating
this
with
package.
Anyway,
we
don't
need
the
formal
procedure
of
like
sharing
keys
or
anything.
If
you
promise
not
to
like
push
malicious
code,
and
just
just
yeah
yeah
I
will
add
you
in
in
pm,
pink
and
also
also,
if
you
have
time,
can
you
research?
Can
you
like
prison
PM
account?
B
Like
yeah
I,
don't
know
if
it's
like
possible
to
freeze
like
one
thing,
I'm
concerned
like
we
have
a
six
or
seven
people
have
an
heaven
like
access
to
this
package
and
in
case
why
somebody
will
be
hacked
and,
like
some,
some
version
pushed
and
some
people
automatically
update
like
if
it's
possible
to
to
yeah.
B
B
Email
also
so
I
just
you
know
like
yeah
read-only
mode
I,
don't
know
if
npm
have
it
I,
never
yeah.
So
I'm,
looking
at
maintainers
and
I.
A
At
the
moment,
it's
still
getting
like
well
over
half
a
million
downloads
a
week,
whereas
graphql
HTTP
is
only
getting
about
70
000,
so
I
think
we
should
wait
for
significantly
more
people
to
move
over
I
think
we
can
do
that
start
guiding
people
with
the
deprecation
message
on
npm
so
set
that
so
that
every
time
they
do
an
install
it
tells
them.
This
is
deprecated.
You
should
move.
A
Also
archiving
The
repository
I
think
is
a
good
idea,
because
that
can
be
undone
if
need
be,
but
it
sends
a
clear
message
commenting
on
the
issues
and
pull
requests
as
well,
also
wise,
I,
think
in
closing
those
down,
but
yeah
I
think
it's
a
little
bit
premature
to
actually
lock
the
the
npm
module.
If
that
is
even
a
possibility.
Oh.
B
We
can
break
if
not
the
possibility
you,
you
can
add
duplication
message
for
package
to
actually
actively
force
people
to
move
somewhere.
Actually,
I
cannot
add
your
email.
It's
like
require
username,
so
I
need
to
know
you
in
Pam,
username
I,
don't
know
if
you
can
search
it
now.
If,
if
okay
super.
B
One
cool
thing:
I
learned
you
can
deprecate
not
only
one
package
but
like
all
active
versions,
meaning
give
somebody
stuck
somewhere.
They
not
don't
need
to
update
to
the
white
test
Express
graph
here,
just
to
find
out
it's
like
deprecated,
which
is
yeah
so
just
like
Spotify
range
from
from
beginning
to
the
end
saying
everything
is
deprecated.
A
Cool
sounds
good
I'm
happy
with
that
is
everyone
else
happy
excellent.
A
Well.
That
brings
us
to
the
end
of
our
agenda.
For
today.
Does
anyone
want
to
discuss
anything
else.
A
Oh
good,
very
quick
meeting,
then
so
I'll
see
you
all
on
at
the
beginning
of
April
nice
to
see
you
all
again.