►
From YouTube: Magento GraphQL Community Meeting, 6 December 2018
Description
Agenda:
1) GraphQl-237: Multishipping coverage (@Vitalii Boiko)
2) GraphQl-258: Product Layered Navigation filters return duplicates (@vpodorozh)
3) GraphQl-248: Create customer account (@Stepan Furman)
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
B
B
B
C
C
A
B
The
idea
furnace
but
item
id
is
340
sound.
Let's
keep
this
product
oozing
multiple
addresses
I
have
a
customer
with
two
shipping
addresses
and
I'll
show
it
because
it's
gonna
take
more
time.
Just
believe
me
that
one
has
to
be
not
desk
as
ie4
and
another
have
is
real.
That's
cheaper,
24
trillion
products,
three
items
and
two
shipping
address
three
two
items.
So
then
I
gonna
take
it
from
this
customer.
B
B
C
B
B
Just
well
I
have
a
lot
of
issues
to
be
so
mentorship
in
model
plus
it
was
implemented
only
for
I
would
say
it
was
implemented
in
legacy
way
and
the
issue
it
wasn't
covered
by
any
REST
API,
so
I
need
to
do
it.
I
would
say
from
from
from
a
scratch,
so
to
use
multi
ship
in
motel.
First
of
all,
I
need
to
prepare
it
for
using
via
graph
QL.
This
means
that
I
need
to
create
customer
session
because
without
customer
session
it
doesn't
work.
B
Also
I
need
to
assign
a
customer
for
this
session,
but
pay
attention.
The
session
session
I
mean
it's
kind,
it's
kind
of
rapper,
it's
not
pure
session,
as
we
know
in
in
server-side.
It
just
is
just
a
container
so
and
then
also
I
assign
the
customer
to
session
and
I
assigned
a
quote
to
multi
shipping
model,
because
if
I,
don't
I,
if
I
didn't
do
this
miss
Shippen
model,
just
troll
what
effects
a
lot
of
exceptions.
B
B
C
B
B
B
D
Yeah,
can
we
can
we
summarize
the
what
I
guess
the
points
that
you
need
help
with
so
there's
there's
a
question
one,
whether
whether
it's
okay
to
divide
to
break
out
the
billing
address
suffered
from
the
shipping
addresses
array.
So
that's
a
clamping
second
question
you
had
was
something
about
setting
a
billing
address
when
the
shipping
has
been
said
already
yeah
in.
D
B
D
F
Nice,
thank
you,
okay,
so
the
bug
was
in
case
you're
running
this
graphical
query.
You
will
get
the
footers.
That
does
not
correspond
to
real
situation.
So
in
fact
you
want
to
get
the
products
tutored
by
category
and
you
want
to
get
the
filters
object.
Yeah
in
this
selection,
and
in
case
you
will
open
that
front
end.
You
will
see
this
filters
this
cocoa
filters,
but
in
fact
the
result
of
this
query
will
be
not
these
suitors,
but
much
more
filters
like
with
duplications
as
well,
much
more
filters.
F
Yes,
so
what
I
have
find
out?
First
of
all,
there
is
the
two
problems,
the
worst
two
problems.
The
first
problem
is
duplication
filters.
You
see
three
styles
with
style
filters,
but
in
fact,
in
fact
it's
not
a
problem.
It's
the
way
how
the
filters
who
drew
name
are
retrieved.
In
case
sampled
seems
simple.
F
Data
are
installed,
three
style
attributes,
product
attributes
are
added
and
all
of
them
have
the
same
label
style,
though
it's
like
miss
configuration
that
on
taboc
is
the
first
problem,
so
we
do
see
style
bottom
footer
with
the
label
style
and
reduced
e
style
bug,
style.
Bikes
attribute
with
the
same
label
style
so,
okay,
the
first
problem
is
not
a
problem.
It's
not
to
duplications,
it
is
a
different
attributes,
but
the
second
problem,
the
different
amount
of
filters
from
the
exact
amount
of
filters
and
I,
find
out
that
the
problem
is
simple.
F
F
For
future
screen,
so
in
fact
when
we
are
saying
okay,
I
want
to
get
products
with
a
filter
it
by
category
D,
28,
yeah,
magenta,
say:
okay,
guys,
I
appreciate
it,
but
I
would
like
to
return
the
filters
for
the
category
for
the
default
category
category
with
a
d2
for
about
yeah.
So
my
solution
is
as
simple
as
the
door.
F
F
Yeah,
though
it
was
the
first
part
of
this
of
the
solution
for
this
problem,
and
the
second
part
was
the
solution
for
this
problem.
It
was
temple
logic,
as
I
said,
that
is
used
in
a
PhD
mountain
plate
of
content
of
viewing
filters.
It's
like
in
case
there
is
no
items
suitable
Artemis
in
your
future.
Then
there
is
no
need
to
show
it,
though
there
is
a
simple
check.
F
D
F
In
front
of
you
see
on
the
one
of
this
styles,
because
only
one
of
this
styles
I
use
it
for
this
category,
category
28,
it's
like,
let
me
show
you
here-
is
a
category
28
yeah.
We
do
see
style
base
layer,
a
basic
conversation
stock.
It
is
a
remember
it's
a
bottom.
Yes,
it
is
a
tower
bottom.
A
trip.
Okay,
I,
see.
F
D
E
F
G
D
F
I
E
F
F
We
met
roller
yeah
and
pick
a
collection,
and
in
case
you
will
compare
it
with
the
this
category
on
front
end,
you
will
find
out
that
it
is
the
sample
just
yeah,
so
it
works.
But
in
case
just
just
let
me
return
to
the
your
question
in
case
we
will
put
the
check
ready
to
default
degree
default
category,
we'll
find
out
that
there
is
a
three
style
attributes:
yes,
style,
one
style,
two
style
three,
but
again
this
that's
just
because
there
is
a
label
with
the
name
style.
Okay,.
D
F
G
D
F
G
I,
don't
think
it
should
be
like
the
case,
but
let's
assume
that
we
have
to
start
attributes
such
as
valid
case,
yes
and
the
question
how
to
use
the
meat
filter.
Actually,
when
you
try
to
filter
the
result
that
should
have
done
today,
because
you
know
like
how
do
you
submit
the
filter
do
provide
named
as
the
filter
or
what
would
you
provide.
F
F
H
F
D
E
D
It's
been
a
while
for
us,
sorry
guys,
okay,
so
so
it's
good
it's
great
to
see
that
it
was
so
it's
fixed.
Now
to
where
at
least
the
query
for
category
reflects,
you
know
the
filters
that
come
back
or
the
same
as
what
you
see
on
front
end.
That's
that's
awesome
and
then
yeah,
it's
yeah.
It
looks
great
so
and
it
looks
like
yeah
that
we
had.
We
have
the
attribute
code,
which
actually
is
just
returns
in
a
different
field.
Actually.
F
H
H
H
A
A
C
C
A
I
H
G
H
Yeah,
so
everything
is
okay,
okay,
so
my
my
task
was
pretty
simple.
The
creative
basic
functionality
for
customer
registration,
who
the
graphical
so
I
have
added
is
the
new
mutation
and
with
the
customer
import
and
customer
output
yeah,
you
can
see
here
that
we
can
add
the
almost
holes
it
all
existing
all
existing.
H
You
attribute
that
we
need
for
procreating
and
means
here
the
crop,
ID
and
website,
because
you
know,
because
it
depends
on
you,
we
can't
mean
we
can't
manage
it
from
the
front
end,
because
it's
just
registration
from
the
front
end
by
the
customer.
So
we
don't
need
to
subgroup,
it
will
be
stated
like
default
cool.
H
So
here
is
the
resolver
and
they
also
faced
with
the
the
one
with
the
one
new
for
me
is
a
setup
context,
so
once
I
created
in
new
account,
so
usually
we
create
new
account
generated
token
token
and
set
it
to
the
to
the
feather
and
right
now.
I
have
to
just
create
a
new
customer
and
instantly
get
EEG
data
so
and
know
that
we
need
to
set
additionally
set
the
contact
here.
H
H
So
we
decided
to
be
do
whatever
we
decided
to
change,
to
create
another
Kulik
request
for
this
and
for
setting
the
values
for
four
different
stores,
because
this
functionality
is
just
only
for
enterprise
for
commerce,
for
commerce
agenda
so
and
I,
don't
have
converse
magenta,
so
yeah
and
and
I
already
started
to
do
some
function
at
the
functional
testing.
It's
not
called
right,
404
now
and
but
I
think
I
will
finish
soon.
H
H
G
H
E
G
What
I'm
saying
currently
this
functionality
is
used
from
admin
panel
only
when
Edwin
creates
customer
account
and
I
don't
remember.
Maybe
there
is
some
configuration
and
then
panel,
where
you
can
reconfigure
behavioral
storefront,
but
by
default
and
pretty
sure
that
you
are
required
to
enter
password
on
stop
okay,.
H
H
A
A
One
notice
Enterprise
Edition
provide
only
UI
for
management
of
customer
edibles,
but
in
scope
of
community
edition
we
can't
emulate
some
additional
custom
attributes.
We
had
some
test
features
and
we
will
postpone
this
functionality
and
separate
tasks
as
I
mentioned,
and
we
will
add,
possibility
to
provide
some
additional
validation
for
customer
choice
and
we
will
add
support
of
customer
attributes
and
separate
tickets,
and
we
don't
need
for
this
Enterprise
Edition,
because
Enterprise
Edition
on
the
few
iPods
it
can
emulate
this
Community
Edition.