►
From YouTube: Magento GraphQL Community Meeting, 5 July 2018
Description
GraphQL Community Project Wiki: https://github.com/magento/graphql-ce/wiki
Mind Map: https://www.mindmeister.com/1094880388?t=a5LVAQ71Vq
Backlog (with Zenhub): https://github.com/magento/graphql-ce#boards?repos=128075669&showPRs=false
Backlog (without Zenhub): https://github.com/magento/graphql-ce/issues
Zenhub Chrome Add-on: https://chrome.google.com/webstore/detail/zenhub-for-github/ogcgkffhplmphkaahpmffcafajaocjbd
A
Okay,
guys
I
think
we
can
start
so.
First,
a
little
update
from
my
side,
who
is
no
I,
am
Valeri
and
work.
Alchemy
engineering
team
but
generally
looks
like
a
hey,
see
a
lot
of
friends
of
not
surprised
so
start
this
week,
a
community
engineering
team
join
the
project,
and
so
we
expect
to
get
more
contribution
and
collaboration,
starting
from
now
wonderful
step,
I
create
a
pole
in
slack,
channel
and
I.
Think
I
simply
have
no
better
result.
Eight
guys
are
ready
to
start
contributor
right
now
and
so
to
you
guys
about
to
start
contribute.
A
Late
share
screen,
you
can
see
result
of
engine
and
I
am
going
to
communicate
with
all
of
these
eyes
directly
and
propose
to
him
first
tickets.
Also
by
the
way
it
will
be,
it
can
be
interesting,
stand
created
tonight,
some
topic
and
you
can't
read
about
state
of
got
really
hot
on
a
mutation,
so
on
also
update
heavy
had
contribution
day
at
molinsky
at
ethics
agency.
Thank
you
guys
and
during
contribution
day,
10
polar
quest
have
been
created
and
a
few
guys
from
ethics
will
demonstrate
result
of
more
interesting
over
quests
so
host.
B
Guys,
as
it
was
said,
last
week,
we
had
a
contribution
day
at
our
office,
where
we
had
a
chance
to
have
briefly
getting
started
with
Rafael
project
and
I
had
a
chance
to
create
triple
request
with
Alex
and
yeah.
Today,
I'm
gonna
show
you
all
them
and
gonna
show
you
one
working
example
of
that
cause.
The
rest
of
them
are
required.
Get
brown
changing,
so
I
didn't
want
to
take
your
time.
That's
why
I?
Let
me
share
my
screen.
Yeah.
B
Yeah
I
believe
so,
but
let's
see
yeah.
That
was
my
first
good
issue
to
take,
and
that
was
this.
This
issue
is
about
content
staging
feature
that
is
part
of
Magento
commerce,
so,
as
you
know,
that
featured
adjust
will
beat
the
system
and
it
changed
the
master
key
for
a
couple
of
entities
and
we
have
a
wrong
methods
that
rely
on
the
Bronk
master
key
since
the
contents,
tangent
is
neighborhood.
That's
why
this
put
bass
is
about
the
change
in
this
relation,
and
also
there
is
some
changes
to
the
related
IP
functional
test.
B
So
we
refactored
this
a
little
bit
and
that's
about
this
request.
So
that
was
my
first
issue
and
the
first
task
in
this
first
task
and
pull
request
in
this
project.
Also,
the
following
one
I
had
a
chance
to
take
one
more
task,
which
was
much
more
interesting
cuz.
It
required
the
whole
knowing
the
whole
workflow
of
adding
a
new
API
to
graph
QL.
B
So
in
this
pull
request,
we
enable
graph
QL
API
for
CMS
blocks,
so
that
was
the
first
interaction
of
this
API
and
in
that
we
enable
ability
to
you
fetch
content
of
couple
of
CMS
back
at
once
and
in
case
that
we
have
some
block.
The
dark
cannot
be
retrieved
for
some
reason.
Example,
there
are
removed
already
or
the
disabled,
so
in
that
case
we
returned
Part,
L
response
which
looks
like
that.
So
let
me
share
and
show
you
what
was
done
there.
B
B
B
In
church,
okay,
hi
and
yeah
I
believe
I
need
to
fix
the
Travis
built
over
there
and
also
probably
that's
it
for
the
first
interaction
interaction
yeah
and
for
the
next
and
the
final
ticket
that
was
nibbling
API
for
CMS
pages,
which
is
pretty
the
same
stuff.
So
basically,
we
will
use
this
when,
along
with
the
API
from
the
URL
resolver,
so
it
should
work
like
that.
B
B
We
also
have
the
only
first
interaction
and
the
following
one
I
believe
require
changes
to
the
page
content
to
have
a
rendered
content
and
also
changes
to
have
it
more
customizable
sense
to
value
for
bringing
this
to
us,
because
I
have
a
small
notice
from
Andrew,
which
is
going
also
fix,
and
also
some
issue
with
Travis
is
gonna
fix
as
well.
So
that's
pretty
it
from
this
demo.
Thank
you
very
much
for
listening
and
nice
to
meet
you
all
guys.
A
C
C
C
C
C
C
A
D
So
the
problem
is:
if
you
make
query
for
category,
you
need
to
take
some
data
from
category
and,
if
you
add
some
additional,
like
enlighten
fragments
here,
there
is
an
issue
so
you'll
get
a
fatal
error
instead
of
the
data.
I
will
show
why.
So,
actually,
if
we
remove
this
fragment,
everything
goes
fine.
But
if
you
add
like
inline
fragments
like
this
one
or
any
other
fragment
the
system
fails
to
process
this
request
and
as
we
can
see
here
in
some
places
of
the
category
resolver,
we
have
like
processing
fields
and
the
system.
D
The
system
awaits
the
field
note
among
the
nodes
and
the
system
tries
to
three
of
the
name
field
of
the
the
name
field
of
the
note
element,
and
if
there
is
some
element
which
doesn't
have
the
name
attribute
or
it's
not
a
field,
the
system
will
like
on
an
attempt
to
get.
This
value
will
have
like
undefined
property
error,
and
that's
why
we
need
to
check
if
the
node
element
is.
D
Is
not
an
inline
fragment,
so
we
have
the
inline
fragment
node
element
on
every
attempt
to
add
some
inline
fragment
to
this
query,
so
by
adding
some
additional
check.
So
we
don't
need
the
inline
fragment
data
on
this
stage.
On
this
stage
we
just
like
we
generates
a
collection,
so
this
data
will
be
taken
into
account
on
the
later
stages.
So
we
just
can't
bypass
this
data
by
just.
If
we
have
this
node
element
in
the
loop,
we
can
just
skip
it
and
go
further
and
by
by
adding
the
three
additional
checks.
D
We
have
resolved
this
issue,
and
so
you
don't
have
the
shuttle
error
anymore
and
you
have
the
correct
data
and
result,
and
the
second
is
the
second
pull
request
is
related
to
the
coverage
of
URL
rewrites
part
of
the
products,
so
them
the
original
task
task
was
to
add
information
about
the
URL
rewrites
for
products
list
that
we
retrieve
using
graph
QL.
So
the
main
attributes
that
should
be
present
in
the
response
is
the
request
URL.
So
it's
the
user-friendly
part
of
the
URL
and
the
part
set
values
of
the
target
URL.
D
So,
for
example,
if
we
have
here
product
and
this
product
belongs
to
some
category,
we
will
have
two
different
URL
rewrite
this
product
so
because
one
you're
right
contains
path
to
the
category
and
the
second
one
is
the
canonical
URL.
It
just
contains
the
product
ID
and
in
case
of
different
parameters
in
the
target
URL.
We
should
parse
them
and
like
return
every
one
of
them.
So,
as
you
can
see
in
case
of
just
canonical
URL,
we
have
Product
ID,
which
equals
five
and
in
case
of
the
URL
that
represents
a
product
in
the
category.
D
A
D
F
D
It's
a
point
of
discussion,
I
believe
and
as
for
impression,
it
was
great
because,
like
if
you
go
to
the
backlog-
and
it's
really
easy
to
pick
up
some
issue
and
start
working
on
the
issue
straight
away,
you
don't
need
to
guess
what
you
what
what
needs
to
be
done
in
within
the
scope
of
this
task.
So
everything
described
very
well.
You
have
user
stories,
you
have
all
additional
data,
you
have
steps
to
reproduce
and
by
just
having
some
briefly
information
about
the
framework,
you
can
just
jump
into
and
start
working
on
any
issue
like.
D
F
Sure
yeah
I
was
gonna,
introduce
myself
yeah,
my
name
is
Misha
I
know,
I
was
actually
out
during
the
week
that
you
guys
had
the
contribution
day
and
did
all
this
amazing
work.
So
I
I
came
back
and
I
was
kind
of
very
happily
surprised
and
shocked
at
how
much
you
guys
were
able
to
get
done.
So.
Thank
you
guys
very
much.
You
did
a
tremendous
amount
of
work
already
and
I'm
I'm
excited
to
have
this
many
brains
and
an
eyes
on
this
project,
because
this
is
this
is
going
to
be.
F
You
know
extremely
valuable
for
Magento
going
forward
and
this
is
going
to
be
the
base,
for
you
know
PWA,
but
not
not
just
that,
but
a
lot
of
other.
You
know
headless
projects
which
have
been
growing
in
number
increasingly
over
the
last
you
know,
and
in
the
last
few
months,
but
anyway
yeah
as
far
as
as
far
as
kind
of
direction
and
next
steps,
I'm
sure
you
guys
or
I'm,
assuming
that
you
guys
have
seen
the
backlog.
F
That's
that's
in
our
project.
So
what
I
wanted
to
share
real
quick?
Let
me
jump
on
the
screen
and
share
the
mind
map,
so
there's
a
there's,
a
link
on
the
wiki
to
to
the
mind
map
it's
kind
of
a
good
way
to
visualize.
You
know
direction
and
kind
of
organization
of
of
these
stories,
so
what
I
did
before
today
I
went
in
and
try
to
mark
all
the
PRS
that
we
have
kind
of
in
flight
that
have
not
been
you
know,
merged
or
finalized.
F
Yet
so
I
try
to
mark
them
with
this
kind
of
a
almost
completed
square
icon.
So
that's
that
will
use
that
I
think
for
kind
of
in
progress
issues.
Just
so
people
know
what
has
been
started
or
at
least
submitted
as
a
PR,
so
that
you
know
people
don't
pick
up
issues
that
are
already
in
progress
but
I
think
that's
it's
a
good
reflection.
It's
not
100%,
up-to-date
I
need
to
add
a
couple
more
items
on
here
that
I've
been
reporting.
F
Those
bugs
so
well
update
this,
but
as
far
as
kind
of
where
our
priorities
lie
in
the
future
is
we
want
to
focus
on
checkout
coverage
as
next
step.
So
that's
going
to
be
up
here.
Kind
of
top
right
corner
of
the
of
the
mind
map-
and
maybe
I-
can
make
this
bigger,
so
you
guys
can
see
better.
So
what
we
we
were
kind
of
thinking
is
that
we
could
start
with
basically
start
implementing
mutations
and
I
know.
F
Stan
had
had
posts
in
his
kind
of
experience
in
working
with
mutations
and
Alex
what
our
she's
also.
He
also
did
a
little
bit
of
changes,
I
think
to
the
framework
to
allow
for
mutations
in
it,
I
think
he's
just
finalizing
some
tests
to
kind
of
have
an
example
of
how
to
do
that.
But
we
thought
that
the
next
kind
of
few
logical
steps
would
be
to
start
working
on
items
like
this,
for
example,
manage
card
items
so
creating
an
object,
cart
object
and
you
know
being
able
to
manage
the
items
within.
F
G
And
I
always
enjoy
to
work
on
checkouts
and
then
working
on
the
total
collection,
the
tax
discount
and
he's
all
part.
So
I
Alex
just
proposed
me
to
work
on
the
first
card
and
that
that
is
related
to
creating
a
empty
card
for
either
guests
or
logged
in
user.
So
I'll
be
going
with
that
one.
But
before
we
I
had
meeting
with
Valeri
yesterday
and
we
went
through
how
the
munitions
are
working
in
graph
tool
in
Magento,
so
I
didn't
like
the
whole
idea,
but
I
need
that
with
the
help
of
Larry.
G
F
Okay,
that
sounds
good,
I
think
in
general
this
is
a
this
is
a
direction
that
can
probably
be
parallelized
meeting.
You
know,
I
I,
don't
think
this.
This
is
something
that
one
person
have
to
tackle.
The
whole
thing.
I
think
this
could
be
probably
handled
by
several
different
work
streams.
So,
and
you
can,
and
you
can
see,
there
is
a
couple
different
directions
where
we
could
take
it.
Things
like
adding
and
managing
payments,
adding
and
managing
address
information
for
customer
on
a
cart
all
these
issues.
F
You
know
all
these
things
will
need
to
be
done
somehow
before
we
can,
you
know
have
this
full-fledged
checkout
functionality,
so,
if
anyone's
interested
in
you
know
different
parts
of
this
flow
on
this
process
feel
free
to
jump
in
and
and
kind
of
take
on
these
issues
and
obviously
reach
out
to
me
or
Alex,
or
my
lady
too,
for
details,
if
you,
if
you
need
more,
sometimes
we
put
kind
of
stubs
or
placeholders
in
place
of
kind
of
scenarios
or
acceptance
criteria.
So
we
can.
We
can
certainly
clarify
things
when,
when
there's
questions.
G
So
will
we
be
resuming,
with
the
first
add,
to
cart
and
then
or
we
will
be
working
concurrently
like
on
and
at
the
same
time
we
will
be
working
on
the
shipping
module
or
the
payment
module,
plus
Add
to
Cart
and
discount
modules,
we'll
be
working
like
at
the
same
time
on
different
things.
Let
you
to
check
out
I.
F
Think
I
think
we
can-
or
at
least
we
can
attempt
to
unless
there's
a
unless
there's
a
strong
reason
why
we
shouldn't
do
that,
and
maybe
you
guys
can
tell
me
from
a
technical
perspective,
if
that's
the
case,
but
my
thought
was,
you
know,
multiple
people
can
be
kind
of
working
on
pieces
of
the
checkout
and
if
we,
you
know,
there's
there's
kind
of
a
breakdown
that
I
just
showed
you
of
different
different
components
of
the
checkout
flow.
So
I
was
thinking
that
different
people
can
can
pick
those
up
the
first
honestly,
the
first.
F
The
first
major
kind
of
decision
would
be
to
to
figure
out
what
the
cart
object
looks
like.
So
we
have
a
we
kind
of
a
proposal
out
there
and
the
ticket
that
I
just
showed
for
endpoints
and
schema.
That
alex
is
posted
and
we
want
to
kind
of
refine
those
and
make
sure
that
that's
you
know
we're
in
a
good
place
with
that,
and
so
we
will
be
looking
for
feedback
and
ways
to
improve
it.
I
think
roughly
it's
based
on
the
object.
What
the
object
looks
like
for
our
REST
API.
F
F
Awesome
so
I
think
that
was
all
from
from
my
side.
I
just
wanted
to
kind
of
nudge.
You
guys
in
the
direction
of
the
checkout
is
our
next
biggest
thing
to
tackle,
but
also
make
sure
to
add
the
few
bugs
that
came
up
in
our
issues
list
to
the
mind
map,
because
I
have
to
have
to
manually
keep
those
synchronized
so
I'll
make
sure
to
have
that
done.
A
Thank
You
Misha,
so
oops
legs,
it's
all
and
they's
missus
eight.
If
you
have
some
question
related
to
project,
if
you
would
like
to
strike
contribute,
please
build
me
Misha
or
Alex
directly
on
graphical
channels.
So
it
was
great
to
see
you
guys
and
I
believe
we
opened
achievements
and
so
see
you
next
week,
guys
yeah.