►
From YouTube: Magento PWA Demo, 5 November 2018 (Sprint 28)
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Alright,
folks,
let's
go
and
get
started
so
welcome
to
the
PWA
developer.
Sprint's
number
28,
as
usual,
has
got
a
pretty
action-packed
agenda
and
so
we're
gonna
start
things
off
with
mr.
Cal
commands
gonna
go
over
some
rest
API
updates
in
the
dev
box,
along
with
other
things,
I'm
sure,
so
we've
got
lots
to
share
Tommy's
going
to
go
through
a
offline
and
browser
fallback
experience,
but
she's
gonna
work
on
from
a
UX
perspective
and
then
switch
it
up
and
give
it
to
a
gifted
Jimmy
Jimmy's
been
working
hard
on
the
the
routing
updates.
A
B
B
We
changed
the
browser
from
wagger
to
redock,
as
you
can
see,
is
a
more
modern
three
panel
set
up
on
the
left
side
here.
You've
got
all
the
West
End
points,
they're
organized
by
the
initial
end,
point
of
directory
and
guest
card
and
integration
and
in
the
middle
you've
got
all
the
details
of
the
rest.
Endpoints
here
can
get
your
parameters
and.
B
It
is
broken
up
into
three
sections.
One
per
guest,
one
per
customer
and
one
for
admin
I-
did
that
because
the
admin
REST
API
endpoint,
which
has
which
is
pretty
complete,
takes
a
while
to
load
we'll
make
some
improvements
on
getting
it
rendered
quickly,
but
it
does
lazily
load
the
endpoints,
as
you
can
see,
it's
activated
until
it
loads
in
real
time,
and
we
are
looking
into
improvements
on
this.
But
we
think
it
is
a
lot
better
implementation.
A
Well,
there's
no
question
just
a
comment.
I
think
I
think
why
this
story
is
so
important.
We've
got
a
lot
of
questions
recently
around
API
coverage
for
certain
things,
right
and
so
I
think
it's
a
team
for
those
who
have
been
following
close
that
we've
made
a
conscious
decision
to
fall
back
to
rest
work
right
and
wrap
Oliver.
Is
it
get
available,
and
so
we
wanted
to
kind
of
give
this
the
same.
You
know
the
same
level
as
other
documentation,
providing
the
access
and
again
James
and
Jeff
and
team
of
that
such
a
nice
job.
A
On
this
recently,
we
wanted
to
just
make
this
note,
but
then
also
again
show
that
show
where
this
relates
to
the
rest
of
the
event
to
the
get
ready
documentation
so
again,
I
think
it's
a
lens
really
welcomed
the
feedback
we've
got
recently
and
again
for
those
who'll
see
the
recording
your
heads.
This
is
where
it
is
so
and
we
are
making
improvements
in.
C
C
On
that
just
really
quick,
wrist
yeah,
this
is
wrist
experience.
Great
I
would
love
to
get
something
similar
up
for
crafty.
Well,
I've
tried
to
work
with
our
DevOps
team
here
on
standing
up
like
a
server
that
we
can
expose
supposed
to
keep
my
documentation,
so
the
developers
can
access
it
without
having
their
own
instance
haven't
gotten
very
far
regard
yet
at
least
so
you.
A
Cool
very
good.
Thank
you.
Mr.
Calvin
lets
up
switch
gears
now
to
Sonya
she's
gonna
walk
through
some
offline
and
browser
fallback
experiences
just
to.
F
D
D
D
There
might
be
any
number
of
points
in
the
shopping
journeys
that
they
might
hit
there,
so
the
safest
thing
would
be
to
take
them
back
to
home
and
allow
them
to
decide
where
to
go.
The
other
one
is
when
javascript
is
disabled.
We
discussed
this
on
friday
and
this
scenario
is
probably
more
likely
to
occur
with
a
technical
user
that
has
disabled
javascript
in
which
gave
him
probably
know
how
to
recover.
But
in
the
scenario
that
somebody,
you
know
who
isn't
technical
and
probably
is
aware
how
to
do
it
run
database.
D
Then
we
sort
of
followed
the
sound
card
model
where
they
direct
people
to
sort
of
a
simple
tutorial
on
how
to
do
that,
so
it
just
the
hyperlink
that
says
enable
drugs
cooking
abroad
that
would
take
them
to
a
page
with
simple
instructions
on
how
to
do
that.
So
those
are
the
two
scenarios
we've
dealt
with.
A
Very
good,
I
also
to
comment
as
people
gather
questions
on
the
center.
This
is
a
fairly
straightforward
story,
but
I
think
it's
perfect
right
now.
I
think
the
other
other
context
on
this
one,
that's
also
is
important.
Is
this
also
helps
us?
You
know
attain
what
you
know.
What
APW
is
right
into
the
part
of
lighthouse
course
4p
doing
a
you
need
to
have
a
graceful
fallback
for
this,
and
so
no
better
graceful
fallback.
Then
I
think
with
what
Sam
you
provided
here
so
I
think
that's
I
think
that's
great
yeah.
D
F
The
idea
it's
closed.
If
you
don't
have
JavaScript
enabled
like
on
purpose
like
we
don't
we
don't
serve,
you
know
if
you
we
reserve
the
right,
but
yeah
I
mean
this
is
obviously
going
to
be
sort
of
a
basic
format
that
we
reused
in
various
situations
where
you
know
you
can't
do
a
full
display
yeah.
So
like
I,
like
the
initial
concept
of
logo,
plus
data
image
plus
explanation,
the
you
know
swap
the
close
time
with
the
hand-drawn
exclamation
point.
That's
final
I
mean
an
important
thing.
You
guys
are
in
charge
of
the
asset.
F
D
A
E
Okay,
so,
unfortunately,
this
demos
not
gonna,
be
as
slick
as
it
ought
to
be,
and
that's
because
the
data
on
my
local
is
not
matching
up
so
you're
not
going
to
see
actual
data
in
the
categories
as
I
flip
between
them,
but
that
will
change
soon.
So
the
main
change
that
we've
made
here
to
routing
is
a
restructuring
of
the
Magento
router
class.
E
In
a
way
that
allows
you
to
render
your
own
loading
view
or
error
view,
either
a
404
or
the
equivalent
of
a
500
when
Magento
route
handler
responds
that
it
doesn't
understand
your
route
or
that
it's
currently
loading
your
route.
So
the
new
structure
of
the
router
passes
route
props
to
a
react
context,
provider
and.
E
Then
you
can
use
a
component
here
called
page
coming
from
Paragon,
which
will
use
a
route
consumer
to
pull
that
context
and
render
the
Magento
route
handler,
which
will
which
is
the
same
thing.
That
already
looks
up
your
route
component
and
renders
it,
but
this
time,
while
it's
doing
that,
it
will
render
your
own
custom
loading
and
error
view
and
then
update
itself
accordingly,
when
once
it
finds
your
route
component
and
because
of
the
way
this
is
constructed,
you
can
actually
use
this
page
component
at
any
level
of
your
app.
E
F
E
E
E
E
C
E
E
C
E
F
Was
basically
gonna
say
that
that
we
we
built
the
navigation
fairly
early
when
there
were
some
pretty
big
missing
pieces
in
what
the
category
tree
response
was.
We
understand
that
Michel,
like
the
nature
of
the
category
tree
and
that's
exactly
what
we
need.
So
that's
that
direction.
We're
done
for
sure,
cool.
F
Have
my
tossed
in
you
know,
I
have
been
working
on
a
quite
a
bit
of
behind
the
scenes
stuff,
including
validation
against
the
cloud
and
most
of
that's
not
really
demo
bull
and
it's
appropriate
for
this
occasion,
although
we
can.
But
you
notice
that
there
are
pictures
on
the
homepage
category
title
that
I.
F
B
F
I
can
so
yes,
there
are-
and
this
is
due
to
there
is
a
mistake
not
in
the
grass
gol
API,
as
far
as
we
know,
but
just
a
missing
piece
and
the
venía
sample
data
that
doesn't
assign
an
image
to
a
category.
So
we've
actually
implemented
in
the
code
of
fallback
that
if
the
image
is
not
available
in
the
category
list
result,
then
the
cat
or
the
category
list
result
is
already
primed
to
pull
the
information
about
the
first
product
that
appears
in
the
category
and
natural
sort
order
and
just
grab
its
image.
F
So
it
doesn't
require
next
to
request.
That's
the
beauty
of
graph
QL
and
you
can.
You
can
now
see
that
there's
images
which
is
nice
couple
other
things.
Thank
you
very
much.
Jimmy
couple
of
other
things.
The
router
thing
is
huge
in
Italy.
It
allows
us
to
merge
in
a
bunch
of
really
valuable
contributions
and
ideas
from
people
like
like
Paul,
and
your
concept
of
custom,
loaders
and
404s,
which
isn't
now
long
in
the
tooth
pole
requests
that
we
can
address
again.
We're
really
excited
to
have
this
abstraction.
It's
you
know,
I,
have
a
data.
F
A
Well,
I,
like
my
zipper,
if
we're
building
on
this
one
I,
you
know
this
has
been
a
big
topic
in
the
community
threats
from
chain
and
others,
and
so
I
think
this
helps
them
tremendously
with
with
something
that's
gonna,
be
pretty
valuable
in
their
their
near-term
work
to
release
early
next
year
or
so
yeah
super
thankful
Bret.
Thank
you
so
much
yeah.
E
A
D
A
C
A
A
H
Okay,
so
the
search
had
a
couple,
pretty
big
obstacles,
one
of
them
being
that
all
the
graph
yellow
stuff
is
a
post
request
which
doesn't
play
that
nicely
with
the
service
workers
search
or
off
I'm.
Sorry,
Oh,
fine!
So
here
we
go.
Let's
just
show
what
this
is
first,
so
right
now
we're
casting
some
requests.
H
Let's
just
go
up
high
and
show
you
what
that
looks
like,
so
we
are
all
falling
now
loading
stuff
and
then,
if
we
go
to
a
page
which
hasn't
been
cached,
it'll
show
a
little
offline
thing,
very
cool
yeah.
So
the
way
it
works
I
had
to
for
the
URL
birth
of
quake,
since
is
a
graph
QL
in
plane
and
it's
in
pair
again
we
couldn't
use
a
call.
This
simple
cash
persist,
library,
that's
just
hooks
into
Apollo,
so
I'm
right
now
cashing
them
in
local
storage
right
now.
H
But
there
is
an
open
issue
in
the
graph
qlc
repository
for
changing
those
to
a
get
request,
so
that
should
be
pretty
simple
to
cache
with
work
box
once
that
gets
changed,
and
so
this
is
like
kind
of
like
a
simple
fix
here.
Just
putting
the
URL
result,
stuffing
a
local
storage
I
mean
so
since
that
you
are
resolved
stuff
is
in
local
storage.
We
put
in
the
pre
cache
all
of
the
components
and
then
in
viola
we
can
load
that
stuff
up
and
actually
load
this
and
then
I
call
it.
H
F
And
there
I
know
that
there
is
an
open
issue
in
the
graphene
to
allow
requests
with
get
so
I
mean.
Misha
can
probably
speak
more
to
how
that's
proceeding,
but
even
absent.
That
I
know
that
it's
harder
to
cache
post
requests
when
they
are
glass.
You
well,
you
know.
Potentially
we
can
add
some
grabs.
You
all
awareness
to
the
serviceworker
itself,
which
is
custom
code,
and
it's
not
presently
in
the
backlog.
H
I
know
the
one:
that's
the
big
one
is
the
URL
result.
Query
me
to
actually
cache,
because
that
will
actually
allow
us
to
live
it
up
or
actually
know
which
pages
is
what
kind
of
route
component
I
don't
know
that
up
and
then,
if
we
use
the
cache
resistant,
it's
like
a
really
easy
and
just
drop
in
thing,
and
then
it
just
loads
it
once
we
load
that
page
yeah
awesome.
G
Okay,
cool,
so
I've
just
got
the
basic
search
component.
Now
we
click
this
it'll
drop
down.
That'll
change,
color
to
indicate
that
we're
actually
doing
a
search,
who's,
throwing
backpack
or
something
and
we'll
do
a
gradual
call.
It's
on
the
searches
on
the
other
products
schema
and
if
we
click
each
item,
we
go
right
into
the
actual
item.
For
that.
G
A
Orie
emojis
I'm
with
you
I
can
definitely
see
how
this
might
murder
some
of
the
work
that
Jimmy
just
showed
right
in
terms
of
like
managing
the
worker
in
the
state
and
you've
got
the
core
there,
which
I
think
is
I.
Think
it's
great
and
kind
of
things
come
to
live.
I
think
really
really
helps
us
get
to
what
kind
of
one
of
the
last
outstanding
experiences
for
for
our
MVP
this
month,
which
is
that,
which
is
great,
that
we
couldn't
be
more
thankful.
A
H
E
E
F
C
F
See
Rico
makes
things
that
the
main
thing
that
still
remains
breath
the
cover
with
drought
QL
is
allowing
the
filter
queries
to
be
specified
as
vo
input
types
so
that
we
can
so
that
we
don't
have
to
write
a
new
query
for
every
like
type
of
filter
logic
that
we
do,
and
you
already
know
about
that.
One
right.
F
A
F
F
F
So
a
couple
things
you
should
be
aware
of.
First
of
all,
there
is
now
functionality
in
the
of
any
sort
of
initialization
that
when
you
first
install
or
when
you
first
run
a
bill,
that's
going
to
check
your
Magento
back-end
URL
and
tell
you
if
you
don't
have
one
and
then
it's
going
to
validate
that
all
of
the
graphical
queries
presence
in
your
project
are
valid
against
the
schema
of
the
attached
project.
F
And
if
you
don't
have
an
attached
project,
we
have
endodontist,
which
has
the
police
version
of
our
maintained
cloud
environment
already,
hard-coded
and
it'll
copy
that
in
so
we
have
an
environment,
validation,
script
and
it's
lets.
You
know
exactly
what
to
do
and
I
can't
demo
this
right
now
with
my
personal
environment
in
a
merge
state.
F
F
So
that's
nice
and
that's
all
kind
of
in
service
of
deployment
which,
as
you
may
or
may
not
have
noticed,
is
now
happening
all
the
time.
Jimmy
went
to
Magento
then
yeah.
Now
that
Sh
and
wouldn't
you
know
it
it's
there,
you
can
even
look
at
it
on
your
phone,
but
there's
also,
for
instance,
I
just
recently
opened
a
feature
request,
pull
request
without
switching
to
web
pack,
4,
which
is
nice
and
exciting.
Let's
see
if
it
deployed
successfully
for
every
pull
request.
F
The
bottom
of
the
pull
request
is
instead
of
check,
give
hugs
UI
changes
sort
of
on
the
regular
about
this.
So
you
know
if
it's
confusing
looking
that's
because
they're
still
figuring
it
out
this
is
this
branch
has
not
been
deployed.
Ignore
that
I.
Don't
know
why
I
said,
but
a
few
quick
show
all
checks
you'll
see
that
the
usual
step
is,
then
you
can
look
at
the
test
results
and
circle
see.
I
looks
like
we
passed.
F
F
That
says
it's
waiting
for
instantiation
now
this
is
pretty
slow
and
my
excuse
for
that
is
that,
while
we're
waiting
for
the
cloud
team
to
get
up
some
better
CI
deploy
I
just
connected
it
to
my
personal
account
that
I've
had
for
a
few
tears
for
this
totally
separate
cloud
aggregation
service
called
now.
It's
not
part
of
the
Magento
infrastructure,
it's
just
something.
F
I
did
so
we
could
have
deploys
and
it's
temporary
but
don't
like
to
have
and
the
initial
latency
is
because
it
is
creating
a
container
npm
installing
building
and
then
instantiating
and
staging
the
project.
You
can
actually
see
what
it's
doing.
If
you
go
to
the
code
base
and
look
in
packages
venía,
there
is
a.
F
Package,
JSON
that
has
whoops
I'm,
sorry
I'm,
actually
into
it
it's
at
the
root.
Forgive
me
there
is
a
now
JSON
file
and
that
presence
just
means
that
whenever
something
is
merged
to
roof,
you
get
alias
to
Magento,
Benia
and
presence
of
Magento
Vimeo
nada
SH,
and
it's
publicly
available
too,
and
that
actually
doesn't
mean
that
the
URL
is
publicly
available.
It
always
is.
It
means
that
you
get
an
interesting
little
peek
into
the
back
end
if
you
want
to
so.
F
If
you
want
to
look
at
these
specific
code,
that's
been
deployed,
you
can
even
on
your
phone.
You
can
also
look
at
it
on
the
desktop,
and
this
is
exactly
the
vacuum
code
that
was
deployed
to
that
particular
thing.
So
you
can
see
what
the
build
is
is
going
on
over
here
in
this.
Oh,
look
that
it's
right
and
that
build
is
done
with
scripts
prefixed
with
now.
F
F
This
is
my
pull
request
for
web
pack,
for
which
is
why
vendor
and
clients
are
so
much
smaller
and
it's
going
to
take
some
code
review,
but
it
sure
is
different
from
this
deployed
instance,
because
this
is
currently
linked
to
the
current
release
branch
so
for
any
full
request
that
you
open
at
sea
well
different
for
any
pull
request
that
you
open.
You
will
find
that
as
soon
as
it
opens.
F
Let's
take
a
look,
for
instance,
ad,
implement
order,
confirmation,
page
by
our
CMC
drove
who
is
waiting
for
our
review
on
it
that
all
checks
it
past
therefore,
is
pole.
Request
is
also
deployed
and
it's,
as
always,
is
that
it's
sort
of
going
to
instantiate
on
demand,
so
as
soon
as
somebody
navigates
they're
taking
that
to
instantiate.
F
So
obviously,
at
some
point
this
is
going
to
be
replaced
with
some
kind
of
a
gentle
cloud
or
some
yacht,
and
you
know,
none
of
us
here
in
the
community
is
listening
on
this
demo,
our
DevOps
people.
It's
not
our
responsibility.
We
know
we
are
in
progress
of
retaining
those
resources,
while
kind
of
being
sensitive
to
the
other
priorities
that
exist
for
Magento
2.3.
F
But
in
the
meantime
this
is
an
enabler
and
when
they
can
provide
us
with
something,
then
we'll
get
something
a
little
bit
faster
and
it's
a
little
bit
less
mysterious
and
attached
to
my
personal
credit
card,
which
don't
worry,
it
doesn't
cost
a
lot.
So
what
we're
gonna
wait
for
here
again
is
that
NPM
install
and
then
build
and
everything
that
we
were
talking
about,
and
this
is
a
totally
different
branch
and
now
it's
loading
and
if
his
PO
request
is
in
effect
here
and
we
should
be
able
to
get
a
dataset
share.