►
From YouTube: PWA Studio Community Sync 11 Sep, 2020
Description
Demos: Updated developer docs (Shopping Cart and Routing tutorial), My Account (Order History), and My Account (Wishlists/Favorites)
A
C
C
C
This
is
I've
also
included
links
to
useful
files
like
the
the
queries
just
just
so,
you
can
see
what
you
know.
The
graphql
looks
like
on
some
of
these,
these
talons
that
that
are
calling
these
mutations
and
queries.
There's
also
links
to
the
source
code
to
get
a
better
idea
of.
What's
going
on
inside
each
of
these
files,
that's
it
for
the
reference
documentation.
Are
there
any
questions
on
that.
C
No
questions
all
right,
so
the
other
update
is
our
routing
tutorial
has
been
updated
to
use
next
extensibility
framework.
This
is
the
pr
and
what
the
significant
thing
about
this
is.
You
know:
we've
removed
an
entire
section
where
you
have
to
override
the
routes
component,
and
you
know
all
the
all
the
different
components
that
you
would
normally
have
to
pull
from
from
venia
and
instead
you
just
have
to
create
an
intercept
file
and
you
can
find
that
updated
tutorial
over
here
add
a
static
route.
C
So
basically
what
what
the
tutorial
looks
like
now
is
you
create
a
green
page
module
create
an
intercept
file
and
then
you
register
the
intercept
file,
and
that
looks
something
like
this
oops.
It
looks
something
like
this.
You,
you
got
your
module
here
and
local
intercept
here
yeah.
I
guess
I
should
have
built
this
earlier,
but
that's
basically
what
what
that
looks
like
any
questions
on
that
tutorial.
A
Back
to
you
andrew
awesome,
thanks
jim
thank
you
yeah,
so
we've,
obviously
jimmy
has
been
doing
a
lot
of
really
great
work
on
dev
docs,
updating
a
lot
of
the
content,
especially
with
regards
to
some
of
the
newer
concepts
like
extensibility
and
they're,
really
working
to
get
some
some
of
that
tutorial
content
out
there.
So
I
definitely
appreciate
any
of
the
feedback
from
the
community.
A
If
there
are
topics
that
you
don't
see
that
you
want
to
see
in
there
reach
out
to
us-
and
let
us
know
james
is
always
on
top
of
that.
So
thanks
again
for
all
your
hard
work
and
for
that
demo,
james.
So
up
next
we
have
we
have
tommy
who
is
going
to
show
us
some
of
the
work
he's
been
doing
for
the
the
new.
My
account
actually.
D
D
So
let
me
first
do
the
demo
and
then
I
can
talk
about
some
fun
stuff.
That's
going
on
behind
the
scenes,
so
I'm
gonna
assume
everybody
can
see
what
I'm
doing
so,
I'm
just
going
to
log
in
just
in
case
you
haven't
you're,
not
a
regular
watcher
of
the
community.
Sync.
We
have
this
new
kind
of
once
you
log
in.
We
have
a
new
section
here
when
you're
on
desktop
mode.
It's
replicated
over
here
as
well.
So,
let's
see
what
should
I
do?
D
We
have
this
brand
new
kind
of
the
only
thing
that
is
completed
is
this
collapsed
view,
so
you'll
see
if
I
expand
this,
it's
kind
of
gonna
say:
oh
there's
still
some
work
to
be
done,
but
this
is
just
a
pretty
simple
kind
of
class
view
of
all
your
order.
History,
I'm
giving
you
just
high
level
details
about
what
you
ordered
a
cool
little
like
collapsed
image.
Gallery
then
kind
of
this
progress
bar
to
let
you
know
where
it
is
in
the
kind
of
delivery
fulfillment
process.
D
So
I
think,
there's
kind
of
like
a
when
it's
first
placed,
I
think
it
says,
processing
when
it's
invoiced.
It
goes
ready
to
ship
when
it's
shipped
it
goes
shipped
and
then
delivered.
Is
your
final
state
it's!
This
is
easily
customizable
if
there
are
additional
steps
that
fit
into
kind
of
your
fulfillment
process,
so
definitely
something
that
can
be
adjusted
and
then,
like
anything
that
we
do.
This
is
all
completely
responsive.
D
So
you'll
see
there
once
you
hit
a
specific
breakpoint,
it
kind
of
breaks
down
nicely
for
mobile
devices
and
you'll
see,
hopefully
that's
coming
through
on
the
blue
jeans.
Okay,
that
when
you
go
kind
of
all
the
way
as
small
as
you
can
go,
it
still
looks
nice
and
you
still
get
all
of
that
content
that
you
would
expect
to
see
so
that
I'm
gonna
talk
about
behind
the
scenes
for
order.
History
really
quick
and
then
we'll
go
on
to
wishlist.
D
D
Like
a
very
high
level
order,
history,
graphql
endpoint,
but
they
ended
up
redoing
it
and
it's
coming
in
two
four
one:
since
ours
support
matrix,
supports
240
and
241.
We
can't
exactly
release
this
feature
just
yet,
but
we
didn't
want
to
hold
up
development.
So
one
of
the
cool
things
that
I
was
able
to
do,
I
was
actually
able
to
develop
against
a
241
beta
backend.
So
I
did
all
of
this
against
live
data,
but
then
to
kind
of
merge
this
in
and
feel
like.
It's
not
something.
That's
going
to
break
everybody's
instance.
D
This
is
the
super
powerful
apollo
directive
that
says
return
client
data.
So
this
is
the
exact
query
that
you
would
use
for.
A
live
backend
and
all
you
have
to
do
is
remove
this
client
directive
and
then
this
thing
is
wired
up
and
working,
just
as
just
as
you
see
it
now,
but
with
live
data,
so
really
cool
that
we're
able
to
like
complete
these
features
ahead
of
graphql,
even
though
the
coverage
is
coming
in
241,
which
should
be
out
here
in
the
next
month,
or
so.
I
think
early
october
is
the
release
on
that.
D
So
it's
really
neat
that
we're
able
to
complete
these
features
and
then,
as
soon
as
that,
graphql
coverage
is
released.
We're
just
going
to
come
in
here
and
remove
this
client
tag,
and
then
we
can
close.
This
feature
out
is
actually
completed
and
then
you'll
see
here
in
the
meantime,
we're
kind
of
just
mocking
that
response,
but
it
was
nice
having
a
real
back
end
because
I
really
just
pulled
the
actual
response
that
I
got
from
some
of
my
live
live
systems,
some
pretty
cool
stuff
there.
D
D
So
there's
an
issue
with
this
image
gallery
where,
with
a
with
a
variant
sku,
I
can't
go
out
and
like
fetch
images
for
it,
so
I
think
there's
an
issue
with
like
configurable
products
and
displaying
images
but
they're,
aware
of
that
and
before
we
toggle
this
feature
on,
they
should
have
it
solved
so
that
that
should
be
not
a
problem
by
the
time.
This
goes
live,
live.
D
So
there
is
a
kind
of
a
full
view,
so
this
is
the
collapse
view.
This
is
kind
of
just
a
little
piece
of
what's
available.
I
think
that
we
also
have
pagination
coming.
I
know
that's
very
top
of
mind
for
everybody
in
the
community
that
we
don't
want
to
grab
everything
from
the
back
end,
especially
if
you
have
like
a
thousand
orders.
So
pagination
is
coming
as
well
and
then
in
this
full
view,
I
think
it's
I
think,
ravan's
working
on
it
right
now.
D
He
might
be
able
to
provide
more
detail,
but
I
think
it's
gonna
have
like
invoice
details.
I
think
you
can
download
invoices.
I
don't
think
there's
gonna
be
like
a
dedicated
order
view.
It's
all
gonna
be
like
in
this
little
accordion
kind
of
thing,
but
you
should
be
able
to
get
all
of
that
information
here.
So
the
idea
is
kind
of
like
it's
kind
of
like
a
collapsed
list
and
then,
when
you
want
to
see
more
detail,
you
expand
it
and
you
can
see
all
that
detail.
F
A
Yeah
chris
had
made
the
comment
and
chris
it's
a
good
comment
and
something
something
we'll
definitely
evaluate
on
on
the
ux
side
that
it
might
be.
You
know
once
more.
In
the
expanded
view,
it
could
be
a
lot
of
data,
especially
if
we
start
looking
at
multiple
invoices
or
multiple
shipments
per
order,
both
good
points
so
we'll
have
to
take
that
into
account.
A
We
we
talked
about
that
some
in
the
design
phase
of,
if
you
know,
worried
about
the
bloat
of
the
the
expanded
table
as
the
as
the
data
kind
of
gets
a
little
bit
larger
in
there.
So
we'll
definitely
go
back
and
take
a
look
at
that
and
something
that
will
of
course
have
to
iterate
over
time.
But
I
think
in
terms
of
just
what
we're
trying
to
get
out
here
in
this
first
pass.
We
felt
good
about
with
with
the
design
on
the
on
the
table,
but
good
points.
D
D
D
You
have
the
ability
to
add
these
items
to
your
cart
as
you'll
see
it
just
ding
that
counter
there,
not
a
lot
of
fanfare
for
adding
to
the
cart.
There's
some
discussion
around
whether
if
like,
if
I
add
an
item
from
my
wish
list
to
my
cart,
should
be
removed
from
my
wish
list.
But
there's
going
to
be
action
items
in
here
for
moving
items,
copying
items
to
other
wish
lists
and
deleting
items
so
right
now,
it's
a
manual
thing,
but
it's
up
for
discussion.
D
If
that's
gonna
continue
to
operate
that
way,
and
then
I
always
love
doing
the
kind
of
responsive
things,
so
this
is
neat
where
it
it
kind
of.
Has
it
uses
kind
of
the
the
image
as
a
basis
for
how
many
kind
of
products
it'll
be
able
to
fit
into
here
before
it
starts
overflowing
to
the
next
row,
so
you'll
see
that
it
kind
of
like
will
continue
to
grow
like
it's
like
here.
I
can
fit
four
here.
D
It's
like
three
here,
it's
two
and
then
that's
kind
of
like
as
as
small
as
we're
gonna
go
and
then,
if
you
go
down
like
super
small
to
like
a
iphone
se,
it
still
breaks
down
really
nicely
to
like
a
two
by
two
kind
of
grid.
I
we
do
have
pagination
coming
for
this
as
well,
but
that
was
also
feedback
for
the
graphql
team.
D
I
think
there's
a
lot
of
graphql
in
points
where
they
just
kind
of
did
not
include
pagination
functionality,
so
this
is
one
of
the
endpoints
where
currently
pagination.
Well,
actually,
this
is
coming
in
242.
So
this
is
mock
data,
so
we
can
build
pagination
and
even
if
graphql
doesn't
have
it
right
now,
so
that
may
just
happen,
but
for
right
now
it's
just
going
to
display
all
of
the
items
in
that
wishlist
and
and
kind
of
just
break
out
into
multiple
rows.
I
think
the
assumption
is
wish
list.
D
Maybe
won't
grow
to
be
that
large,
but
if,
if
that
does
become
something
where
like
a
wish
list
will
have
hundreds
of
items,
maybe
like
a
wedding
registry
or
something
like
that,
could
have
a
ton
of
items
yeah,
you
might
want
to
have
like
some
pagination
there,
some
kind
of
different
ui.
So
it's
not
just
an
entire
page
of
wishlist,
so
you
can
easily
paginate
through
that.
But
this
is
the
progress
so
far.
This
is
what
we're
calling
the
main
view.
There's
different
stories,
you'll
see
here
to
be
handled
by
another
story.
D
This
one
also
to
be
handled
by
another
story.
So
just
the
progress.
So
far
again,
this
is
coming
in
242,
so
this
data
is
mocked,
but
we're
coding
it
against
the
approved
architecture
for
these
endpoints.
So
it
should
be
very
similar
to
order
history
that
once
this
endpoint
is
finally
released,
we
just
remove
a
client
tag
and
this
thing
is
off
to
the
races,
so
not
much
here,
just
some
really
cool
responsive
stuff,
but
nothing
else
really
to
too
crazy.
A
Yeah
we
have.
We
have
a
question
from
chris
that
I
can't
recall
in
our
in
our
requirements
how
we
implemented
but
clicking
on
the
dress
or
clicking
on
the
product
image.
Will
it
go
to
the
pdp,
and
I
can't
remember
if
we,
if
we
decided
that
it
would
or
if
that
action
would
have
to
occur
after
you
add
it
to
cart.
D
D
You
can't
navigate
directly
to
a
configured
product,
so
that
is
something
we'd
have
to
do
to
support
that,
but
once
that
was
in
place,
then
yeah
we
could
yeah.
So
we
would
need
to
persist
these
color
and
size
selections
to
the
url,
and
then
we
could
link
to
those.
Those
directly
could
probably
say
the
same.
For
like
cart
like
I
guess,
if
you're
in
the
cart
and.
D
B
B
D
D
A
Awesome
well
thanks,
tommy
again
yeah.
My
account
is
definitely
coming
along
in
terms
of
our
our
progress
there.
Just
a
quick
update
on
on
the
rest
of
the
work
that
we're
doing.
We
still
have
a
lot
of
effort
and
a
lot
of
movement
on
internationalization
and
localized
content,
so
obsessive
al's
team
is
is
working
diligently
to
get
that
done.
We
we
do
have
an
upcoming
release.
A
I
can't
even
remember
my
release
version
numbers
right
now
with
the
with
the
next
magento
core
release
right,
so
that's
coming
up.
We
will
you'll
see
in
that
release
that
we
have
a
lot
of
the
things
that
we've
kind
of
demoed
or
gone
over
recently
that
weren't
in
7.0
things
like
the
apollo
upgrade
mini
cart.
A
So
that's
kind
of
the
plan
there
you'll
you'll,
hear
more
from
us
get
more
detail
on
that
as
we
get
closer
to
the
release,
but
just
a
heads
up
that
that
is
coming.
The
other
thing
I
guess
I
covered
it,
so
my
account
internationalization
that's
happening
and
then
I
guess
we'll
go
to
lars
or
tommy
any
updates
on
community
corner
any
updates
on
any
progress
of
what
the
community
is
working
on
with
in
terms
of
contribution.
E
D
Otherwise,
we'll
kind
of
run
through
that
for
them,
and
then
yeah
we've
made
an
effort
to
try
to
make
public
some
of
the
items
in
like
our
internal
backlog
and
bringing
them
to
github
just
to
kind
of
bring
bring
over
some
some
things
that
don't
shake
out
as
priorities
to
us.
Just
because
we
have
a
ton
of
features
that
we
have
to
complete,
but
things
that
are
still
important
enough,
that
we
want
the
community
if
they
are
able
to
to
assist
with
some
of
those
bugs.
D
So
we've
been
moving
a
lot
of
bugs
over
and
hui
has
jumped
on
those
like
immediately.
I
think
there's
like
four
pr's
of
theirs
up
right
now
that
we
we
are
processing,
so
we're
going
to
continue
working
through
that
we're
going
to
continue
trying
to
funnel
a
lot
of
fun
stuff
into
that
prioritized
column.
And
then
I
think
we
have
some
move
it
with
extensibility.
That
should
be
coming
soon
as
well.
C
You
can
click
on
that
to
get
a
breakdown
of
where
we're
getting
these
numbers
from
you
can
get.
You
know
an
idea
of
you
know
how
how
much
the
community
is
contributing
to
the
project.
I
thought
that
would
that
was
interesting
for
people
who
are
interested
in
that
kind
of
data.
You
know,
keep
track
of.
You
know
points
and
all
that
so
nice,
that's.
D
C
A
All
right
so
yeah,
so
if
you're,
if
you're
interested
in
getting
on
that
leaderboard,
if
you're
interested
in
working
with
us
on
any
of
the
kind
of
open
items
that
tommy
spoke
to
just
reach
out
to
us,
let
us
know
you
know
reach
out
through
github
or
reach
out
through
slack.
Of
course,
you
know
we're
not.
We
hear
the
feedback
from
the
community
that
you
know.
I
think
that
developers
want
to
work
on
more
than
bugs
to
be
fair.
I
think
there
are
some
really
exciting.
A
There's
some
exciting
work
within
the
books.
There
are
front
end
components
that
that
we
open
bugs
against
there's
front-end
work
as
well
as
some
of
the
kind
of
back-end
or
more
developer-focused
work,
but
also
you
know
if
you're
really
interested
in
a
specific,
a
work
stream
that
we
have
going
on,
whether
it's
internationalization,
whether
it's
my
account
or
any
of
our
upcoming
features.
A
I
just
reach
out
and
we're
happy
to
try
to
find
a
way
to
to
you
know,
pull
in
interested
parties
and
provide
them
some
some
work
which,
of
course,
we're
happy
to
receive
as
well.
So
I
think
that's
it
for
in
terms
of
community
updates.
I
think
last
thing
that
I
have
on
my
side,
so
this
will
be
the
last
community
sink
that
I'm
on
for
the
next
few
months.
A
I
don't
know
you
know
it'll
get
crazy
on
the
call,
but
you
know
the
the
community
stinks
will
continue,
we'll
make
sure
that
we
that
we
figure
out
how
to
make
sure
that
all
the
blue
jeans
links
and
all
the
the
kind
of
logistics
are
in
place
to
handle
this
cut
over.
But
then
I
will
see
you
guys
going
into
again,
I
guess
going
into
next
year.