►
From YouTube: PWA Studio Community Meeting 03 March, 2020
Description
Demos for Checkout: Payment Method, Checkout: Confirmation Page, CI: Webpagetest/Lighthouse, and partner demo from Digital Six
A
A
B
A
B
Hey
everyone
thanks
for
joining
I'll,
be
speaking
about
the
payment
information
section
in
check
out.
If
you
have
been
following
this,
this
is
the
cart
page,
I've
added
something
to
the
tide.
Once
we
click
proceed
to
checkout,
it
takes
us
to
the
checkout
page.
These
are
being
handled
in
different
tickets.
B
This
is
being
handled
by
Tommy
and
Andy.
Once
we
move
to
the
payment
section,
we
have
options
of
credit
card
and
paper
right
now.
People
as
is
not
added.
Yet
it's
not
part
of
the
scope,
but
we
do
have
to
record
this
is
powered
through
Braintree.
We
can
give
a
deep
one
number
that
Braintree
has
as
a
test
number
in
this
case.
I'll
just
get
some
random
numbers.
It
does
give
us
an
option
to
either
have
the
same
address
a
shipping
address,
or
we
can
give
our
own
billing
address.
B
In
this
case,
I'm,
giving
mine
and
also
the
payment
section,
does
have
coupon
code
gift
cards
and
gift
options
which
will
be
handled
in
their
own
tickets.
Right
now
we
are
only
doing
the
credit
card
section
and
the
edit
of
that
now
just
give
something
something,
and
once
we
click
review
order,
we
can
see
that
the
payment
information
has
been
added.
As
a
summary,
and
since
the
shipping
information
is
different
from
the
billing
information,
we
can
see
a
different
section
for
that.
There's
also
the
Edit
part.
B
B
B
You
can
see
that
the
information
has
changed,
but
now
the
billing
address
section
has
been
removed
because
it's
the
same
as
shipping
address
right
now.
This
is
the
guest
checkout
that
you
look
is
looking
at
we'll
be
working
on
the
authenticated
check
out
soon.
Once
this
is
done,
there
is
no
PR,
as
if
now
but
end
of
today,
I'll
be
creating
a
PR
along
with
the
tests.
You
guys
can
check
it
out.
C
B
B
Similarly,
we
can
add
I'm
not
completely
sure
of
how
we
can
do
that
using
extensions,
but
we
can
add
an
extension
point
here
where
we
can
invoke
a
new
radio
and
also
the
method,
payment
method
and
each
of
these
payment
methods
have
their
own
talents,
so
they
maintain
their
own
information
other
than
actually
telling
it
whether
if
it's
hidden
or
not,
ideally
speaking,
they
should
have
all
the
information
that
they
can
render.
So
we
don't
need
to
add
extension
points
anywhere
else.
D
Don't
have
anything
to
add
right
now,
I
would
say:
I
would
say
that
that's
just
gonna
muddy
the
water.
Let's
talk
about
this
in
terms
of
what
you
have
done
and
extensions
will
come
in
a
in
a
later
expose,
but
you
and
I
can
talk
offline,
so
you
can
talk
about
it,
but
I
would
rather
the
next
cut
discussions
about
extensions.
Come
from
folks
like
you
who
have
talked
with
me
and
done
it,
which
is
understandably
not
taken
place.
Yet
don't
worry
about
it.
Okay,.
A
Yeah
I
would
just
I
would
just
add.
On
top
of
that,
that
we
know
that
I
did
adding
additional
payment
provides.
A
payment
methods
is
something
that
everyone's
definitely
looking
for.
So
it's
something
that
we
have
in
the
backlog
as
a
follow
on,
as
indicated
by
the
fact
that
you
know
as
revanche
code
for
paypal,
it
says
coming
in
coming
later:
it's
something
that
we
have
in
the
backlog.
It's
something
that
we
can
definitely
open
up
community
contribution.
So
if
there's
you
know
interest
there
from
the
community,
so
then
we
can
definitely
talk
about.
A
G
I
really
no
never
mind
that.
Wasn't
it
alright,
you
guys
can
hear
me
right.
Yes,
okay,
so
I'm
working
on
or
I've
been
working
on
the
order,
confirmation
page,
which
is
the
page
that
you
it's
like
the
receipt
page
so
that
you
saw
on
the
mini
cart.
It's
it
it's
what
you're
shown
after
you
complete
checkout.
G
If
it
gets
merged,
it
may
not
actually
be
functional
entirely
until
all
of
the
other
steps
are
filled
out,
so
I
kind
of
have
to
do
some
like
fake
data
and
push
some
stuff
directly
to
graph
QL
to
make
it
work.
What
you're
seeing
here
is
the
is
like
the
in
progress,
checkout
workflow.
The
important
thing,
though,
is
after
you
or
to
see
the
to
see
the
order.
Confirmation
page
you
just
place
your
order
and
voila.
G
You
see
the
order
number
which
isn't
actually
getting
placed
yet
so
we're
rendering
nothing
or
running
no,
but
as
soon
as
we
start
placing
orders
this,
this
order
number
will
be
provided
and
then
the
the
shipping
info,
I
I,
had
filled
out
previously
through
some
other
methods.
The
shipping
rate
I
had
selected
as
well
as
the
items
in
your
cart
and
some
helper
text,
and
then
we
have
a
little
help.
Helpful
form
that
if
you
want
to
create
an
account
directly
here
on
the
on
the.
G
Order
confirmation
page
you
can
do
that.
This
is
almost
one
for
one,
with
the
create
account
view
that
you
see
when
you
go
here
with
a
few
changes.
I
think
we
removed
the
confirmed
password
and
this
helper
text
and
the
styling
is
a
little
bit
different,
but
otherwise
is
able
to
use
most
of
that
form
as
well
as
use
this
items
review
component.
So
the
way
this
works
is
is
kind
of
neat.
G
You
know
we
don't
want
to
work
right
now,
we've
been
using
Apollo
to
to
store
and
and
render
from
so
the
so
whenever
you
place
an
order
whenever,
whenever
you
add
an
item
to
your
cart
or
you
or
you
are
modifying
items
in
your
cart,
removing
stuff
that
that
data
is
served
from
the
cache.
Well,
you
make
a
network
request,
it's
cached
and
then
your
components
are
updated.
But
in
order
to
render
the
check
out
or
this
confirmation
page,
we
have
to
show
data
that
doesn't
exist
anymore,
because
the
the
card
has
already
been
submitted.
G
The
orders
been
submitted
and-
and
we
want
to
rightfully
wipe
that
out
from
local
storage
so
that,
if
you're
on,
if
you're
a
guest
user
on
the
library
computer
or
something
that
your
information
isn't
persisted
in
cache
for
another
user
to
come
and
grab
so
the
way
we
do.
This
is
right
when
you
click
that
check
out
right
when
you
click
that
place
order
button.
G
What
happens?
Is
we
make
a
quick
Network
call
for
the
current
status
of
the
order,
all
the
information
that
the
order
confirmation
page
needs
and
we
we
hold
that
in
local
store
in
like
local
State
react
you
state,
I,
think
or
Court
or
I'm,
or
no
no
I'm
using
I'm,
actually
using
use
query
but
I'm
using
a
network
only
so
that
doesn't
cache,
and
then
that
passes
the
data
to
the
order
confirmation
component
for
rendering.
G
So
when
you
refresh
it's
gone,
it
doesn't
exist
in
your
cache
at
all,
and
if
you
leave
the
computer
after
this,
it's
it's
it's
wiped.
It's
your
data,
safe
I,
guess
I
can
show
you
desktop
view
is
is
similar
to
the
to
the
cart
and
checkout
page.
We
have
like
a
main
content
and
the
sidebar
over
here
that
Scrolls
with
you
so
after
you
place
that
order
scroll
to
the
top,
and
you
just
see
or
check
out
your
order,
confirmation,
page
I'm,
trying
to
think
if
there's
anything
else,
that
I
should
call
out.
C
G
My
password
field
was
being
filled
because
I
have
LastPass
installed,
so
just
was
trying
to
be
helpful
but
yeah
this
data,
this
data
comes
from
like
an
initial
initial
value
object.
So,
just
like
we
get
the
rest
of
this
data
for
rendering
on
this
page.
We
also
pass
it
to
our
to
the
create
account
component
here
that
injects
the
initial
values
from
your
order
and
they're
editable
too.
So
you
know,
if
you
were
shipping
to
somebody
else,
I
don't
think
we
have
I,
don't
think
I
think
we
would
just
render
that
data
here.
C
G
A
H
C
E
E
So
I
have
kept
that
optional
and
if
you
see
something
like
the
ephemeral,
if
it
fails,
it
will
put
a
comment.
Something
like
this,
and
if
you
see
this
and
if
you
know
for
sure,
if
you
know
like
it's
not
related
to
your
code
changes,
you
can
just
ignore
it
at
the
end
as
part
of
QA
I'll
be
going
through
any
of
these
failures
and
I
will
be
out,
testing
them
and
then
I
will
love
post
a
comment
if
it's
actual
failure,
that's
it
from
my
side.
Any
questions.
E
G
B
A
All
right:
well,
thanks,
Deb!
Obviously,
if
you
have
any
questions
around,
you
know
this
new
CI
kind
of
build
process
feel
free
to
reach
out
to
Deb
there,
something
that's
obviously
I,
think
kind
of
needs.
Sorry,
my
wife
and
kid
are
just
having
like
a
play
party
in
the
kitchen
right
now:
I'm
totally
distracted
so
reach
out
to
Deb.
You
have.
If
you
have
questions
there
around
lighthouse
integration,
so
I
think
that's
it
for
our
internal
demos,
I'll
give
the
the
team-
maybe
a
second
here
to
chime
in.
A
All
right,
great,
so
Jordan
unfortunate
Jordan
had
an
internal
commitment
that
he
had
to
make.
So
he
couldn't
be
on
today's
call
for
community
corner,
but
he
did.
Let
me
know
that
we
would
have
you
on
here
and
the
team
from
digital
six
to
demo
us
on
the
PWA,
a
work
that
they
have
been
doing
on
their
end.
And
so
we're
excited
to
have
you
guys
here
and
I'll
turn
it
over
to
you
and
if
you're
on
the
call
still
yeah.
J
A
J
A
J
Good,
isn't
it
so?
We've
we've
built
a
used
via
PDF
PWA
studio
as
the
basis
for
this
site
and
we're
hoping
to
launch
in
three
four
weeks
time
and
we're
pretty
much
wrapped
up
everything
on
the
project,
except
for
a
couple
of
issues
that
we
found,
which
we
were
going
to
discuss
as
a
call
just
see
if
anyone's
got
any
ideas,
and
let
me
just
think,
there's
a
chat
up
as
well
as
the
yes,
okay
good.
J
So
even
we've
got
Tony,
McHale
and
Yoda
on
the
call
as
well
they're
the
the
guys
that
actually
worked
on
the
site,
so
I
might
just
quickly
run
through
just
an
Add
to
Cart
process
check
out
and
then
like.
It
was
guys
cake
over
so
well,
obviously,
selling
selling
whiskey
here
and
this
clients
on
the
gentle
one.
At
the
woman,
though,
they
were
used
to
Magento
they're,
very
much
looking
forward
to
getting
a
lovely,
fast
v8.
J
J
We've
built
custom
layout
view
for
the
dates
that
they're
the
new
whiskey's
arrived,
because
that's
one
of
their
appeals
and
I
think
we're
also
doing
pvp
and
euro
and
USD
storefronts.
So
that's
one
thing
that
we
haven't
got
working
yet
is
an
issue
where
you
can
add
the
car
or
if
you
then
change
the
store
you
then
you
get
we're
unable
that
the
talk
to
the
moment
and
it
won't
load
the
cart
anymore,
because
we're
trying
to
load
the
old
store
to
you
there
and
what
was
the
other.
J
The
only
other
issue
rap
against
this
server-side
rendering
and
our
hosting
company
doesn't
allow
docker
installs.
So
we
were
going
to
use
SEO
snap
and
we
can't,
because
we
don't
have
docker
so
we're
now.
Looking
at
alternative
options
there
or
potentially
detaching
SEO
snap
from
docker
and
I
think
it's
best
if
Tony
McCarroll
and
you'll
get
training
on
what
they
did
on
project
and
how
they
found
it.
K
K
L
Hi
I'm,
Michael
and
I've
been
working
on
this
project
with
joining
mainly
on
front-end,
and
we
have
basically
used
the
PW
studio
project
as
our
starter
project
and
we
have
made
of
customization
but
few
things
that
worked.
Well,
our
gradual
queries,
our
context
mini
serve
service
both
or
the
development
environment.
So
we
basically
need
it
just
just
few
adjustments
for
it
to
fit
our
needs,
and
these
things
worked
really
well,
but
we
we
have
found
some
issues
when
using
the
the
talent
hooks.
For
example,
we
I
think
we
had
sometimes
issues
that.
L
Or
sometimes
the
town
hooks
are
very
specific
for
the
component
and
just
a
small
small
change
in
in
the
component
requires
work
on
on
the
tongue
hook
to
be
done,
and
the
next
thing
we
found
complicated
was
testing,
sometimes
just
just
small
changes
on
the
UI
on
the
layout
cost.
The
the
test
fails,
so
I
was
thinking,
maybe
maybe
more
integrational
tests
would
help
in
this,
and
otherwise
us
us
even
mentioned
we're
working
on
on
the
server-side
rendering,
and
that's
probably
something
that
that's
something.
L
I
So
I
was
just
working
attempted
backends
on
this,
and
most
of
that
was
just
writing
the
graphical
things
that
didn't
exist.
Like
shipping
estimates,
custom,
attributes,
emails,
password,
resets
and
things
I
didn't
really
do
much
in
the
videos.
I've
just
Billy
ended
missing
functionality,
roof
that
was
always
fun.
A
Yeah,
so
let
me
jump
in
here
so
first
off
what
you
guys
have
done
here
is
great
I
mean
the
the
site
looks
great
I
know
you
guys
have
had
some
issues,
you've
had
to
work
through
and
we're
of
course,
happy
to
help.
You
know
thrown
resources
on
our
side
to
help
get
across
the
line,
but
what
you
guys
done
here
is
amazing.
This
site
is
awesome
and,
more
importantly,
it
speaks
geared
near
and
dear
to
my
heart,
because
I
love,
whisky.
D
Honestly,
if
they're,
like
promo
codes,
you
might
want
to
just
pass
those
around
I
have
I
have
a
sort
of
a
deep
dive
question.
That's
you
can
feel
free
to
answer
very
generally,
which
is
SEO.
Snap
wasn't
feasible
for
you,
because
of
docker
I
was
wondering
if
there
was
an
option
that
was
as
out
of
the
box
as
SEO
snap
for
doing
server-side.
Rendering
with
react
itself
react
HTML.
Is
that
something
that
your
stack
would
be
capable
of
doing
with
nodejs
somewhere
in
the
in
the
actual
web
tier.
J
Yeah
yeah,
the
the
limitation
is
just
we're
using
some
nasty
hosting
and
they
don't
like
docker,
because
their
hosting
setup
as
Microsoft
is
anyway.
So
we
can't
then
put
docker
on
to
the
micro
services
that
they've
got
set
up.
So
if
we
can
get
SEO
is
not
set
up
without
docker,
then
we
should
be
fine,
but
I,
don't
think
we'll
be
able
to.
D
L
D
Okay,
good
to
know,
I
know
that
it
would
take
a
lot
of
optimizations,
but
the
what's
what's
pertinent
to
me
is
how
easy
it
is
for
you
guys
to
set
up
your
production
stack
to
do.
You
know,
for
instance,
doctor
versus
to
do
no
js'
at
server-side,
and
so
that's
just
one
data
point
for
us
about
what
would
be
the
most
convenient
for
you.
So
thank
you.
A
Yeah
in
terms
of
the
I
think
you
guys,
you
have
a
couple
other
points
around.
You
know
some
issues
with
testing
some
issues
with
some
of
the
kind
of
missing
function,
I,
which
I
think
are
all
valid
things
that
we'd
love
to
deep
dive
into.
Given
the
the
nature
of
this
call
for
the
wider
community,
I'd
say:
let's
open
up
to
questions
from
the
internal
team.
A
Anybody
on
the
call
about
you
know
anything
that
particular
that
the
digital
16
ran
into
with
this
implementation
on
the
project
and
then
you-
and
we
can
definitely
set
up
time
after
this
meeting
and
after
this
call
to
deep
dive
into
those
issues,
specifically
with
your
team
in
ours,
and
we
can
help
you
kind
of
resolve
or
you
know,
find
a
solution
for
some
of
those
tops
of
SSR
and
testing
and
so
on
and
so
forth.
So
I'll
open.
F
I
did
have
so
I
know
you
listed.
One
of
your
issues
was
the
switching
between
like
locales
or
currencies.
I,
don't
know
what
exactly
that
was,
but
I
think
what
you
would
need
to
do.
There
is
like,
if
you're,
using
Apollo,
I,
think
Stephen
kind
of
indicated
this,
like
we
use
the
Apollo
cash
for
everything.
So
when
you
switch
between
those
different
views,
you
probably
need
to
blow
that
cash
away.
So
there's
something
called
like
reset
store.
I
think
that
will
like
wipe
that
cache
complete.
We
for
you
and
then
it'll
that'll
force
them.
A
F
We
use
Apollo
cash
persist,
which
persists
the
cash
to
local
storage,
and
we've
found
an
issue
with
reset
store.
We're
like
no
matter
how
many
times
you
reset
it.
Local
storage
restores
it.
That's
it
like
you
get
in
this
like
reset
restore
loop,
so
that
is
something
I
would
look
into,
but
be
mindful
of
that
caveat
with
the
Apollo
cache
persist.
J
F
Yeah
I'm
working
with
Chris
at
Brad
bender
for
like
ITN
stuff,
he's
added
having
the
same
problem
where,
when
you
switched
between
like
locales
like
translations,
the
same
thing
happens
where,
like
that,
you
still
have
everything
in
your
Apollo
cache.
It
doesn't
know
that
that
data
is
stale,
I
guess,
but
that
would
be
a
similar
solution
for
localization
to
you
need
to
wipe
the
cache
make
sure
it's
not
being
persisted
with
Apollo
cache
persist
and
then
all
your
queries
should
refresh
and
have
the
data
it
needs.
J
A
Last
update,
I
guess
for
our
side.
I
know
that
there's
been
some
talk
of
the
contribution
day.
That's
coming
up
this
weekend,
so
PW
ACA
was
kind
of
a
late
addition
to
the
to
the
agenda
for
the
caucus
people
we
are
going
to
participate.
I'll
turn
it
over
to
Tommy
here
a
little
bit
to
talk
about
kind
of
our
participation.
This
Saturday
for
those
that
are
interested.
F
There
we
go
now.
Can
you
hear
me?
Yes,
yes,
great,
ok,
so
yeah
as
Andrew
mentioned
global
contribution
day
came
out
of
nowhere.
I
guess
this
is
something
that
was
probably
going
to
be
paired
with
summit
and
with
the
IRL
cancellation
of
summit.
I
think
this
is
the
kind
of
compromise
for
still
having
like
a
big
hackathon
day
that
we
would
normally
have
in
person.
So
we
were
a
late
addition.
F
I,
don't
even
think
we're
on
the
website
right
now
as
a
project
that
you
can
focus
on,
but
do
not
worry,
maybe
I'll
refresh
and
we're
there
now.
No
we're
still
not
there,
but
we
are
a
project
that
you
can
contribute
to.
During
this
contribution
day,
we
will
have
internal
resources
staffed
throughout
the
day.
F
The
the
format
is
a
little
odd,
it's
24
hours
between
10
a.m.
Saturday
and
10
a.m.
Sunday,
so
there
may
be
a
couple
hours
there,
where
somebody
might
be
sleeping
or
changing
a
diaper
I
don't
know,
but
for
the
most
part,
we're
gonna
try
to
be
there.
Curating
work
helping
out
with
anything
that's
needed
so
such
as
this
awesome
PWA
that
we
did.
You
just
saw
you
guys
are
running
into
issues.
Maybe
if
you
can
form
that
into
like
something
that
can
be
contributed
to
core
we
can.
F
So
the
board
we
will
be
working
on
is
the
same
community
backlog
board
that
we
we
this
and
comp
does
all
we
haven't.
We
have
a
lot
of
stuff
in
review,
so
it
might
be
drastic
all
the
PR
we
need
to
get
merged.
We
have
a
FEMA
available
here
for
new
features,
so
this
is
really
kind
of
like
a
call
or
call
culture's.
F
F
If
you
have
a
question
for
one
of
us,
you
just
hop
in
and
say:
can
somebody
help
me
and
then
we
kind
of
like
pair
program
through
it
together
and
get
you
going,
make
sure
you're
not
blocked
on
anything
that
you're
working
on?
So
if
you're
interested,
don't
have
anything
goin
on
Saturday
or
just
have
like
a
question,
that's
been
bothering
here
or
anything
else
feel
free
to
come
hit
us
up.
We
should
be
there
for
those
24
hours.
A
Awesome
cool
thanks,
Tommy,
alright,
so
I
think
that
about
wraps
us
up
for
today.
So
we
had
a
number
of
good
demos
there
again.
The
contribution
date
is
Saturday.
If
you're
interested
participating,
you're
wondering
how
you
know,
there's.
Obviously
the
website
we'll
reach
out
to
Tommy
or
myself
on
a
slack
Channel,
and
then
we
look
forward
to
seeing
you
guys
all
next
week
and
in
the
community
slack
channel.
So
unless
anybody
has
anything
else
with
paws.