►
From YouTube: Magento PWA Community Meeting, 1 February 2019
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
A
B
I,
can
we
have
some
really
really
interesting
stuff
that
we
have
just
merged
and
we
have
issued
it
as
one
of
our
point
release
candidates.
Now
it's
probably
worth
commenting
that
we
have
now
19
release
candidates,
not
normally
the
way
that
one
uses
at
least
candidate
tag
which
I
recognize.
But
we
are,
you
know
just
about
to
kick
off
a
real
major
release
after
several
delays
and
drawbacks,
all
of
which
were
in
the
service
of
getting
this
more
production.
B
Highlight
the
most
recent
batch
of
merges
to
our
release
branch
is
that
check
out
through
Braintree
is
completely
online
thanks
to
Andy
terranova,
some
great
work
by
him
and
I
can
go
through
and
demo
that
and
unless
Andy
you
want
to,
but
I
know
that
I'd
be
putting
on
the
spot
so
I'm
happy
to
do
it.
I
was.
C
B
I
want
to
let
you
do
it
and
give
you
some
time
so
that
I
wanted
to
call
that
out
first
off,
because
I
think
that's
really
the
most
momentous,
but
there
are
other
things,
probably
the
most
sort
of
user-facing
and
documentation.
Heavy
new
feature
that
has
landed
is
the
concept
of
portability
in
venía
components.
Now
you
may
have
heard
that
our
notion
of
extensibility
is
due
for
expansion.
B
We
have
to
add
as
much
power
and
configurability
to
our
extension
concept
that
Magento
has
in
order
to
satisfy
our
own
mission,
but
for
now
that's
not
entirely
complete
because
we're
trying
to
be
very
safe
and
not
create
extension
concepts
allow
partners
to
invest
a
lot
of
time
and
energy
and
creating
value
on
those
concepts
and
then
realize
that
they
don't
scale
and
have
to
roll
them
back
and
delete
them.
That's
what
a
startup
can
do,
and
we
can't
quite
do
it
that
way.
You
can
make
features
like
a
startup
can,
but
for
expense
ability.
B
Right
now
we
are
trying
to
stick
to
the
existing
concepts
of
extensibility
and
composability.
That
already
happen
in
the
JavaScript
ecosystem.
The
way
that
that
would
be
done
is
by
using
the
parts
of
PWA
studio
as
JavaScript
modules
that
you
import
through
dependency
management.
So
with
that
in
mind,
we
have
I'm,
just
gonna
go
ahead
and
go
Benny
consuming.
B
B
B
You
can
see
that
this
is,
though
it's
perhaps
not
displaying
really
beautifully
on
this
screen
at
this
resolution,
because
it's
just
a
POC,
you
can
see
that
there
is
a
product
detail
component,
that's
come,
that's
displaying
static
data
here
and
then
a
root
component.
That,
of
course,
is
having
a
day
to
fetch
error,
probably
because
there
is
an
issue
with
routed,
but
I
can
show
that
to
you
in
the
local
site,
just
one
seconds.
B
B
B
There
you
go
now,
you
can
see
in
the
local
store
that
I've
got
running,
that
isn't
subject
to
the
routing
bug
in
our
CI.
That
not
only
can
you
use
a
presentational
react
component
which
of
course
works
just
by
injecting
static
data
into
it,
but
you
can
also
embed
a
root
component
which
knows
how
to
fetch
the
data
on
its
own.
Now,
that's
important
to
note,
because
this
means
that
not
only
can
you
use
just
venya
widget
tree
like
the
gallery
and
the
you
know
category
detail
lists.
B
You
can
also
use
its
logic
in
its
workflow
as
separate
consumable
pieces,
of
course,
that
logic
and
workflow
needs
to
be
able
to
connect
to
input
output.
Otherwise
how
does
it
fetch
its
data?
So
the
way
we
solved
for
this
is
that
we
created
an
idea
called
many
drivers.
This
is
not
necessarily
a
new
idea.
It's
effectively
is
an
adapter
interface
that
gathers
all
of
the
needs
necessary
things
together,
but
what
we
did
is
try
to
implement
it
in
a
way
that
was
unobtrusive
and
simple
free
we're
not
doing
a
giant
dependency
injection
container.
B
B
B
This
that
actually
renders
those
images
on
the
side
here,
this
thumbnail
components
uses
the
resource,
URL
function,
and
it's
that
resource
URL
function
that
produces
the
URLs,
that
it
knows
how
to
load
from
vania
which
wait.
What
are
these
urls
simple,
urls
they're,
not
compressed
or
anything,
but
they
know
exactly
how
to
pull
them
with
the
media,
catalog
product,
prefix
and
everything
from
the
Magento
site.
That's
something
that
is
tightly
bound
to
the
implementation
of
the
Magento
site.
How
does
it
venía
do
that
and
maintain
its
connection
with
magenta?
B
Where
does
it
define
that
configuration
it
does
so
in
venya
upwards?
So,
if
you're
using
the
full
venía
site,
you
know
that
if
it
matches
you
know,
media
catalog,
etc
that
it's
going
to
redirect
to
the
proxy
and
the
proxy
is
going
to
just
target
the
back
in
URL,
simple
enough,
but
let's
say
you're
on
a
site
that
doesn't
have
this
up
word
file
and
can't
rely
on
the
back
end
behaving
that
way.
B
B
B
So
if
you
look,
for
instance,
at
I,
don't
know,
cart
trigger,
we
have
connect
or
in
category
tree
we
have
query
and
we
don't
import
query
from
react,
Apollo
and
more
directly,
because
the
query
component
expects
there
to
be
a
provider
at
the
top
of
the
context,
so
it
expects
to
be
running
inside
the
vineya
app
essentially
so,
rather
than
using.
This
react
Apollo
dependency,
as
we
once
did.
B
We
switch
it
to
this
source
drivers
file
and
then,
in
our
build
step,
we
transpile
it
so
that
the
string
for
you
to
override
is
venía
/
drivers,
which
there
is
some
documentation
for
that.
I
was
at
74,
no
is
the
menu.
The
pull
request
is
closed
now
and
working
on
documentation
for
it
thanks
in
advance
to
James
Calculon.
But
there
is
some.
B
That
explains
how
you
would
override
this
dependency
in
your
own
bill.
Let's
say:
webpack
you'd.
Do
it
like
this?
You
want
to
replace
this
Magento
of
any
a
drivers
dependency
with
my
replacement
drivers,
and
then
your
replacement
drivers
file
can
look
something
like
this:
that
exports
a
different
implementation
of
resource
URL,
maybe
a
different
implementation
of
link,
so
it
doesn't
need
react
router
to
be
there.
Otherwise,
the
link
component
will
complain
different
implementation
of
query.
So
you
just
pretend
that
your
queries
are
always
loading
effectively.
B
This
inversion
of
control
allows
you
to
import
venía
components
that
expect
a
certain
application
environment.
We
observe
and
then
inject
that
at
build
time.
So
you
you,
don't
treat
it
like
it's
a
new
or
different
type
of
import.
You
just
statically
import
it
like
anything
and
then
in
your
build
configuration.
You
are
adjusting
the
way
that
modules
are
resolved
so
that
it
brings
in
your
apps
dependencies,
and
in
doing
this
you
can
import
many
a
components
and
use
them
in
line
just
like
this.
B
So
in
this
implementation
of
this
example,
we
have
an
application
file
that
creates
a
couple
of
routes.
It
does
use,
react,
router
and
there's
a
presentational
component
option
and
I
showed
you
that
the
presentational
component
is
just
a
simple
set
up
that
imports
a
little
bit
of
hard
coded
product
data,
I,
threw
in
a
gist
and
then
renders
vania
product
detail
and
that's
a
simple
example:
the
container
component,
which
actually
incorporates
route
components
product.
B
It
doesn't
even
need
to
do
anything
because
the
app
renders
it
directly
and
all
that
it
needs
to
do
is
examine
the
URL.
Just
like
a
regular
product.
Detail
page
does
and
then
resolve
that
URL
into
a
product,
which
is
why
you
can
see
here
they
would
I
go
to
route
component
or
how
their
route
component
here
that
it's
just
that
URL
key
that
you're
used
to
seeing
in
Magento.
So
if
you
import
a
full-size
venía
component,
then
you
have
effectively
imported
the
entire
SEO
site
map
of
your
venía
site.
B
If
you
want
it
to
be
that
way,
just
in
the
products
to
me.
So
this
is
super
powerful
and
it
permits
you
to
import
venía
components,
usability
concept,
it's
already
well
understood,
and
my
dough
of
it
here
may
have
been
a
bit
scattered,
but
you
can
take
a
look
at
it
yourself,
both
in
Magento
research,
many
a
consumer
example
and
in
the
new
code
and
comments
that
have
been
merged
in
with
pull
requests
788.
B
So
that's
the
the
cool
part
for
extensibility
sakes,
and
if
you
were
paying
attention,
your
sharp
I
might
have
also
caught
that
there
was
a
width
parameter
and
some
of
those
image
requests.
Let's
talk
about
that
a
little
bit
if
you
go
to
venía,
PWA
calm
and
yes,
that's
what
it
is
now,
instead
of
Magento
of
neh,
you
might
notice
that
payloads
seem
a
little
bit
smaller,
especially
these
images.
B
That's
highly
optimized,
written
in
c,
usually
pretty
easy
to
install
and
get
running
on
any
platform
through
node,
and
it
provides
this
API
where
you
use
for
each
parameters
just
source
in
an
URL
from
another
domain
and
to
arbitrary
operations.
On
its
you
know,
change
its
format,
change
its
quality.
The
way
that
it's
currently
set
up
the
default
is
pretty
cool.
It
uses
the
brand
new
web
P
image
format
when
the
client
indicates
that
it
can,
and
otherwise
it
compresses,
JPEGs
and
PNG
is
really
well
optimized,
but
these
were
sort
of
yucky.
B
B
You
have
a
single
central
driver
file
and
that
driver
uses
make
your
file
from
our
utilities
directory
and
make
URL
is
what
does
all
of
the
venía
specific
URL
construction
to
turn
a
particular
URL
into
a
resized
one,
based
on
the
argued
width
parameter
now,
there's
more
to
do.
If
you
look
at
the
category
tile,
you
might
notice
that
that
width
parameter
that
we
argue
is.
B
Preview
image
size
and
that's
actually
presently
hard-coded
and
we
had
some
work
out
there
to
add
responsive
images
and
images
that
are
directed
using
the
source
set
attribute
in
the
picture
element
that
pull
request
is
still
outstanding.
And
if
you
look
in
the
polls
list
for
current
state
PWA
studio,
which
I
totally
know
how
to
navigate
to.
B
It
must
be.
Oh,
you
know
what
we
closed
it
didn't
we
didn't
we
so
I,
guess
that's
not
something
people
can
look
at
super
easily,
but
when
it
reopens
or
you
can
certainly
create
your
own,
it
would
be
great
if
we
could
replace
these
hard-coded
things
with
some
manner
of
responsive
image
element
that
detects
both
viewport
size
display
density
and
it
can
also
interoperate
with
the
style
using
some
of
the
responsive
image
techniques
that
I
won't
go
into.
Annette
I
won't
go
into
now,
but
there's
a
lot
of
great
resources
in
the
web.
B
We
were
thinking
about
creating
a
components
that
was
part
of
the
core
toolkit
that
lets
you
very
quickly
and
succinctly
insert
an
image
that
becomes
responsive
kind
of
based
on
the
style
sheet.
That's
that's!
What's
next,
it's
probably
not
going
to
arrive
in
the
current
release,
but
I've
already
taken
up
a
lot
of
time
and
again
these
two
things
well
fantastic
or
not.
B
A
C
C
Now
you
may
remember
previously
you
had
to
enter
these
things
in
order,
so
you
had
to
put
your
shipping
information,
followed
by
the
billing
information,
followed
by
the
shipping
method
and
we
would
kind
of
piecemeal,
send
those
things
back
to
the
MT
back
end
as
you
submitted
each
one
now.
We
instead
are
just
saving
those
things
to
local
storage
and
we
only
submit
to
the
back
end
when
you
click
the
confirm
order.
Button.
D
C
The
bottom
there
so
that's
a
little
bit
different,
the
local
storage
is
that
I
don't
actually
have
to
show
you
that.
But
so,
if
you
enter
these
things
and
then
obviously
you
know
end
your
session
and
come
back
later,
it
will
remember
them
so
I
can
enter
these
things
in
any
order.
Let's
see
what
else
is
interesting,
the
kit
there's
a
cancel
button
here,
which
will
just
close
the
check
out
portion.
C
Previously
it
closed
this
entire
drawer,
which
the
X
button
still
does
so
this
kind
of
does
that
there's
an
edit
kind
of
like
there's
a
bunch
of
like
CSS
stuff
to
you,
but
I'll
skip
over
that
stuff.
There's
an
edit
icon,
indicating
when
you
have
filled
out
one
of
these
sections
that
you
can
go
back
and
change
the
information
that's
in
there
and
then
the
interesting
part
which
I
demoed
once
before.
But
it
was
like
Andrew
said
a
couple
weeks
ago,
at
least:
is
the
the
Braintree
integration.
C
So
so
this
is
a
Braintree
supported,
widget
I!
Guess
there
is
some
documentation
around
valid
card
numbers
here
that
you
can
put
in
you
don't
want
to
put
in
here.
This
is
a
sandbox
Braintree
account,
so
it
has,
you
know
a
set
list
of
cards
that
you
can
put
in
there
that
it
will
accept.
So
this
is
kind
of
the
most
canonical
fake
card
number.
C
The
number
four
followed
by
a
whole
bunch
of
ones
any
date
in
the
future
will
do
here
for
the
expiration
date
and
then
any
three-digit
CVV,
and
that
will
go
off
to
Braintree
and
request.
What's
what
they
call
a
payment
nonce
and
then,
when
we
submit
this
thing,
we
submit
that
to
the
MT
back-end,
which
then
goes
to
Braintree
itself
and
says:
hey
I
got
this
payment.
C
You
know
that
stuff
and
then
you
can.
You
can
submit
this.
You
guys
have
all
seen
submit
actually
going
through
giving
your,
but
that
was
some
new
stuff
I'm
trying
to
remember
if
I
forgot
anything
major
there,
but
I
know
you
said
we
only
had
five
minutes.
So
maybe
that's,
maybe
that's
a
good
place
to
end
yeah.
Yeah
I
think
we're
gonna
get
rid
of
this
like
get
it
by
stuff
based
on
code
review
comments.
So
don't
take
too
much.
A
So
with
the
last
admitted
here,
I
guess
I
would
say
we
haven't
spent
a
lot
of
time
looking
at
what's
coming
up
in
the
backlog,
I
think
you
know
as
a
team.
We
we
admit
weeks
ago,
I
think
we
talked
about
how
the
team
was
going
through
the
process
of
transitioning
to
more
of
a
comp
on
workflow
right
and
as
a
part
of
that,
we
had
purposely
decided
to
limit
the
amount
of
work
that's
coming
in,
so
that
we
you
can
catch
up
on
existing
work.
A
That's
on
the
board
catch
up
on
existing
pr's
that
are
out
there
in
the
review
and
QA
column.
So
the
team
has
been
working
really
hard
on
that,
and
that's
that's
why
we
look
in
it
purposely
limited
I,
think
our
that
amount
of
backlog,
grooming
and
the
amount
of
new
work
that
word.
That
word
something
in
obviously,
in
the
next
couple
weeks,
we'll
start
to
see
that
transition
back
more
towards
items
in
the
backlog.
So
we'll
start
having
those
conversations
more
so
I
would
end
it
there
and
guess
they
say
stay
tuned.