►
From YouTube: PWA Community Meeting March 3, 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
All
right
so
welcome
everybody
to
another
pwh
studio
community
update.
We
didn't
have
one
last
week
because
of
the
internal
All
Hands,
so
we're
kind
of
picking
up
after
the
last
two
weeks,
I
think
in
terms
of
the
first
agenda
item,
demos,
I,
don't
know,
I
believe
every
stuff
to
Adrian
Adrian.
You
had
a
great
launch
this
week
with
into
bwa
or.
A
B
B
He
helped
me
a
lot
to
put
this
demo
up
on
a
server
and
make
it
go
live,
and
you
should
expect
some
cool
contributions
from
him
too,
in
the
future,
both
in
into
demo
and
hopefully
in
that,
if
it
applies
so
to
start
things
off,
as
you
can
see,
it's
very
different
from
Vania.
The
general
idea
was
to
develop
the
PWA
version
of
Magento
team
with
you
UX
and
front-end
patterns
that
we
found
to
be
really
good
throughout
our
experience
with
working
on
other
project
with
clients.
B
B
B
I
made
this
decision
because,
as
well
as
watches,
don't
have
the
full
API
support,
I
believe
for
four
colors.
You
can
only
get
the
title
all
or
the
label.
You
cannot
get
the
value
for
the
color
or
the
swatch
image
yeah.
Let
me
know
if
I'm
wrong,
but
at
night
the
best
decision
for
us
to
was
to
go
with
simple
dropdowns.
Of
course
we
have
the
Add
to
Cart
and
quantity
changers.
B
We
also
have
the
share
buttons
which
are
working,
and
we
have
a
working
gallery
and
Radek
district
description,
so
I'm,
adding
it
to
the
cart
and
another
change
on
venya
is
that
we
have
part
and
checkout
pages
which
are
more
similar
to
the
standard
magenta
one
and
magenta
two
page
structure.
So
for
now
a
shopping
cart
only
has
an
option
to
remove
the
product
and
continue
to
checkout.
B
B
Selecting
the
shipping
method
and
in
the
end
you
get
the
little
overview
and
your
placing
order.
Hopefully
it'll
go
true
and
that's
it.
It
can
create
the
account
which
is
same
as
on
venya.
So
that
is
it
it's
really.
It
has
been
really
fun
working
on
this
project,
I
really
like
the
tooling
and
how
easy
was
to
make
so
I'm
really
happy
with
the
freedom
and
customizations
that
we
can
make
in
terms
of
choosing
our
libraries
and
just
for
example,
venya
is,
is
using
informed
package
for
forms.
B
A
C
I
think
it's
great
work,
though
agent,
you
guys
have
done
a
fantastic
job.
I
know,
I've
said
it
to
you
guys
quite
a
bit
now
these
are
the
type
of
outcomes
that
we're
trying
to
drive
right,
and
you
know
pretty
much
what
we're
doing
many
of
you
I
components.
It's
not
just
a
new
theme.
It's
not
just
van
young,
it's
really
about
the
whole
experience
here,
and
so
what
you've
done?
You
kind
of
build
off
what
we've
created?
Extent
where
you
think
it
makes
sense.
C
I
have
pressure
tests,
the
things
that
make
that
there
really
are
important
to
you
and
you
know,
look
at
you
know
kind
of
incremental
contribution.
That's
part
of
that!
That's
exactly
what
we
want.
So
I
think
it
was
a
great
example
of
that
and
no
anxious
to
see
the
continued
development
to
yourself
and
you
are
along
the
way
for
that.
So
nice
work
I
mean
you
know
that
we
we
certainly
talk
about
that
quite
a
bit,
but
this
is
a.
This
is
a
great
example
of
how
that
can
work.
Thank.
B
B
Wanted
to
show
one
more
little
thing:
it's
not
really
the
double
a
studio
related,
but
also
cool
thing
that
we
also
wanted
to
wanted
to
make
sure
that
it's
great
it's
the
CSS
itself,
so
we
are
using,
as
I
said,
modern
CSS
approach
with
with
CSS
variables
and
call
a
calculation
fault
and
functions.
For
example,
we
have
variables.
B
D
This
is
James
like
Eric
I.
Don't
want
to
talk
for
too
long,
because
I've
done
that
enough.
But
I
wanted
to
add
to
his
congratulations
and
just
express
my
excitement
about
how
great
it
is
to
see
you
building
on
PWA
studio
and
showing
some
of
the
potential.
Even
is
you
had
to
do
extra
work
to
fork
it
because
we
still
have
a
lot
more
to
do
for
scaffolding
new
projects,
but
you
contributed
a
tremendous
amount
and
I
appreciate
it.
D
E
B
In
terms
of
CSS
you
so
whenever
I
made
small
incremental
changes
to
CSS,
it
updated
really
fast
and
I
was
really
happy
about
it.
But
once
I
added
the
composing
classes,
which
is
CSS
modules,
feature
I.
Think
if
start
was
a
call
page
reload,
but
it
wasn't
that
big
of
an
issue.
So
if
it's
interesting,
if
it's
possible
for
code
composing
to
not
trigger
the
whole
reload
because
I
know
it
needs,
the
web
pack
needs
to
add
the
whole
class
to
the
component.
So
maybe
that's
why
it
refreshes
the
whole
page.
D
Still,
thank
you
for
the
feedback.
It
is
true
that
once
the
CSS
modules
have
to
recompose
classes,
then
they
often
require
a
full
reload.
It's
something
that
you
can
fix
with
good
hot
module
reloading.
But
right
now
we
haven't
and
that's
a
point
for
improvement
and
I
had
I
guess:
I
have
one
other
question
which
is:
you
have
created
a
lot
more
CSS
variables
and
it
looks
like
you've
used
BEM
to
define
them.
Yes,
can
you
talk
a
little
bit
more
about
that
choice?
B
The
main
advantage
that
I've
noticed
is
that
I'm
much
better
at
memorizing
the
variables
because
I
just
go
typography
something-something
color,
something
something
vertical
spacing
horizontal
spacing
yeah.
It
really
just
gives
me
a
pattern
that
is
easy
to
memorize,
that
I
really
don't
have
to
go
back
and
check
if
the
editor
doesn't
complete.
It
or
author
suggests
it.
For
me.
B
B
B
I
actually
wrote
an
article
a
while
ago
on
how
to
name
CMS
blocks
in
magenta,
1
and
magenta
to
in
order
to
remember
them
easy
and
I
use
the
similar
syntax
to
them
and
since
then,
I
try
to
apply
it
in
as
many
cases
as
possible,
because
I
found
out
it's
really
easy
to
memorize
and
navigate
between
the
between
the
code.
So.
D
A
Okay,
so
next
I
believe
that
we
have
mr.
Kaufman
on
the
line.
James
has
worked
over
the
last
week
to
do
some
discovery
around
our
dev
Docs
and
work
to
determine.
Maybe
some
gaps
are
some
opportunities
for
future
Deb
doc.
Development
I
leave
you
in
his
in
his
ticket,
which
is
on
our
board
that
had
contained
that
discovery
effort.
There
were
some
polls
that
he
wanted
to
cover
with
the
team
with
with
the
community
and
receive
some
feedback
on.
So,
if
you're
on
the
line
James
take
it
away
all.
E
Basically,
I
proposed
some
topics
and
tutorials,
based
on
conversations
we've
seen
in
the
community
slack
channel
a
lot
of
its
shin
surprise,
you
it's
how
to
do
stuff
and
how
to
deploy
production
and
why
I
wanted
to
do
is
open
it
up
to
the
community
for
feedback.
This
will
give
me
a
chance
to
is
kind
of
shaped
the
the
sort
of
road
map
for
docs
on
you
know
what
you
want
to
see
us
create.
We've
got
some
feedback
already,
but
I'd
appreciate
additional
feedback.
F
A
We
have,
we
also
have
some
time
right
now,
so
if
anybody
on
the
line,
I
think
it
would
be
a
great
discussion
for
a
few
men
to
say,
if
there's
anybody
online
that
can
think
off
the
top
of
their
head
about
something
the
Deaf
Doc's
that
you
wish
was
there
or
that
is
applicable
to
this
topic
right.
We
want
that
feedback
right
now,.
B
B
G
D
Everything
you
see
is
a
demo
against
our
cloud,
except
that's
the
pro
instance
implementation,
which
includes
the
upward
PHP
demo,
still
not
publicly
available
for
scaling
reason
and
that's
very
important
to
us,
but
yeah
I
mean
bare
minds.
The
cloud
deployments
of
Magento
PWA,
studio
and
venía
are
currently
demonstrating
beautifully
the
fact
that
the
front-end
in
node.js
can
be
deployed
entirely
separately
from
the
backing.
Magento
instance.
That's
how
it
all
works
today
and
we're
looking
forward
to
also
having
a
demo,
alongside
of
deploying
them
all
in
the
same
dock
root
under
a
single
PHP
server.
G
D
Have
a
lot
of
additional
documentation
and
use
case
analysis
to
do
so.
I'm,
sorry
that
you
guys
are
having
trouble,
but
you
know
we
can
take
it
offline
first
of
all,
but
I
think
the
main
thing
to
understand
is
that's
the
type
relationship.
Sorry,
the
version
relationships
between
the
develop
branch
of
Magento,
the
release,
branch
of
Magento
and
the
current
branch
of
PWA
studio
are
still
under
some
of
its
kind
of
same
clarification,
work
and
our
core
team
is
actually
among
the
work
in
progress.
D
G
To
wire
what
we're
trying
to
wire
ATMs
to
it,
so
we
can
demo
that
since
it's
a
foundation,
a
p.m.
right,
all
the
rest
of
the
all
the
rest
of
the
things
that
graph
needs
to
support
as
well.
I
know
this
is
a
PW
a
meeting,
but
graph
has
kind
of
foundation
at
PWA.
That's
what's
driving
graph,
and
how
do
we
make
sure
all
the
things
that
we're
seeing
and
doing
here
can
be
immediately
leveraged
by
people
there?
You
know
if
they're
selling
it
and
using
the
cloud
to
sell
absolutely.
C
And
its
own
track,
so
yeah
Dave.
Let's
talk
about
that
offline.
The
graphical
team
actually
has
their
own
forum
very
similar
to
this.
To
kind
of
talk
through
things
and
I
think
we
were
overdue
for
some
enablement
with
some
upcoming
231
work.
Just
as
a
side
note,
you
know
if
you
were
to
look
at
the
board
today,
there's
a
lot
of
great
work
really,
as
we
bear
down
on
two
three
more
which
is
coming
out
in
the
next
couple
of
weeks
and
so
for
those
who
are
following
for
us.
C
G
G
How
do
we
get
all
of
air
and
crass
this
team
to
be
able
to
show
up
mark
why
slurs
team
to
be
able
to
show
it
get
everybody
excited
about
being
able
to
very
very
easily
take
all
this
fantastic
work
that
you
guys
are
doing
and
get
that
in
front
of
customers
that
that
you
know
are
in
front
of
revenue
streams
right,
yeah,
okay,
thanks
guys!
Sorry,
if
that's,
this
is
the
wrong
place.
You
and
James
tell
me
and
we'll
take
a
completely
sideways
you'll,
never
hear
it
again
on
this
call.
A
D
D
D
Change
everyone's
mind:
we
talked
about
making
sure
that
we're
going
to
do
responsible
semantic
versioning
for
pwace
to
do,
and
we
are
still
committed
to
that.
But
one
thing
that
we
have
come
to
understand
is
that
graph
QL
breaking
changes
are
something
that
can
happen
because
of
a
Magento
update.
Also,
they
can
happen
because
of
a
change
in
your
custom
attribute,
set
or
a
schema
change
brought
on
by
the
installation
of
an
extension,
because
those
things
are
particular
to
Magento
instances.
D
Then
we
have
to
consider
them
as
part
of
instance,
configuration
which
is
a
type
of
data,
and
so
making
a
breaking
change
for
any
graph.
Ql
schema
change
would
be
one
consistent
way
of
doing
it,
but
there's
no
way
to
because
it's
not
those
aren't
related
to
version,
so
instead
we
have
to
find
another
consistent
way
of
doing
it,
and
that
means
that
we
can't
break
versions
for
schema
changes
from
the
outside.
So
we're
not
going
to
break
versions
for
schema
changes
from
the
inside
either.
D
What
we're
gonna
do,
instead,
is
add,
tooling,
to
help
you
in
take
changes
from
the
Magento
backing
instances
schemas
and
what
what?
That
is
what
sorry,
what
the
backlog
shows
you
as
part
of
that
effort,
is
that
we
are
creating
some
additional
tooling,
which
you
may
have
already
experienced,
some
of
in
the
validation
of
queries
step
during
the
build
of
PWA
studio.
Today,
our
core
team
is
working
on
adding
some
intelligence
to
that
which
can
identify
for
you
what
likely
magento
configuration
changes
have
resulted
in
a
breaking
graph,
QL
change
to
the
schema.
D
It's
also
going
to
log
extensive
and
helpful
messages
about
which
files
have
breaking
changes
that
are
necessary
and
we
are
going
to
have
an
internal
log
which
the
tooling
will
use
to
help.
You
understand
what
likeliest,
if
it's,
a
breaking
change
to
the
Magento
version
or
incompatibility
there
or
an
issue
with
your
stores
configuration
so
right.
Now
we
have
a
story
in
progress
for
that
tooling
work
and,
additionally,
we
have
a
story
in
progress
that
we
factor
some
of
the
venía
queries,
so
they're
no
longer
tied
to
venía
sample
data.
D
If
you
have
right
now,
try
to
get
a
store
running
without
installing,
specifically
the
venía
custom
attributes,
and
you
have
seen
that
product
pages
fail
to
load
because
of
the
graph
QL
type
error,
then
you're
not
alone.
We've
all
seen
that
and
that's
because
the
graph
QL
queries
for
the
product
page
initially
relied
on
venía
sample
data,
specific
store
configuration,
that's
a
bug
for
us.
We
need
to
treat
venía
a
little
like
the
existing
staff
treats
luma
where
it
is
an
opinionated
styled
store.
D
Yet
it
is
also
meant
for
Y
in
a
large
number
of
configurations.
So
we
need
to
write
the
coach
B
as
soon
as
possible,
so
we're
making
that
change.
Last.
We
wanted
to
be
possible
for
you
to
consume
individual
components.
You
want
to
import
the
product
detail
page.
You
want
to
import
the
just
the
search
bar.
You
should
be
able
to
do
that,
and
not
only
import
just
the
presentational
component
itself,
but
but
also
the
the
container
component,
which
is
connected
directly
to
the
venía
drivers.
D
You
should
be
able
to
reuse
queries
as
encapsulated
parts
of
components,
but
if
those
queries
are
dependent
on
the
Magento
version
or
on
the
backing
instance,
then
we
want
to
make
sure
that
there
is
some
backwards
compatibility
layer,
install
and
that
layer
could
easily
add
an
abstraction
like
an
ORM
that
would
add
complexity
to
the
concepts
in
PWA
studio.
We
don't
want
to
do
that.
D
We
want
the
mappers
to
be
very
simple
and
very
functional,
so
we're
working
on
a
interface
and
a
standard
for
adding
mapping
functionality
a
component
so
that
it
can
be
compatible
with
more
than
one
version
of
the
graph
QL
schema.
So
with
those
three
efforts,
the
tooling
to
intake
schema
changes,
the
genera
sizing
of
the
venía
components
and
the
addition
of
a
mapping
layer
for
the
JavaScript
components
themselves
and
the
data
they
consume.
D
We
plan
to
release
with
two
three
one,
not
just
for
2001
animal
version
of
pwh
studio,
but
a
version
of
PW
a
studio
that
is
a
minor
release
that
adds
compatibility
systems
for
all
future
graph.
Ql
schema
changes,
and
we
of
course
accept
and
would
welcome
and
appreciate
any
more
contribution.
You
have
on
ideas
for
tooling
or
on
problems
you
confront
with
breaking
changes
to
the
graph
UL
schema
or
questions
you
have
about
that
roadmap.
D
A
The
holidays,
we
talked
about
how
the
team
was
transitioning
to
common
process
around
and
scrum,
because
of
that
also
has
some
transformation
of
our
award
and
our
workflows.
The
team
has
worked
really
really
hard
over
the
last
few
weeks
to
make
sure
that
we
got
control
over
our
work-in-progress
sort
of
working
our
way
through
all
of
our
tickets
on
reward,
which,
at
the
time
when
we
started
this
process,
was
something
like
sixty
issues
that
were
in
progress.
We
can
see
now
that
from
ready
to
start
to
review
in
QA
right
there's.
A
What
is
that
team
issues
so
great
great
progress
by
the
team
and
I
think
the
importance
of
that
is
that
it
allows
us.
It
gives
us
the
capacity
to
ingest
more
of
the
great
contribution
that
we're
getting
from
community
members.
So
I
would
say
they
here
that
we're
we're
looking
to
reintroduce
I
think
some
of
the
process
that
used
to
exist
when
we're
in
prescribed
in
terms
of
the
community,
grooming
or
community
tickets,
that
we
identify.
A
First,
in
Chelsea
on
it
so
we'll
look
to
in
the
next
in
the
next
couple
weeks
started
bringing
that
back.
So
we
can,
if
you're
a
community
member,
that's
something
for
how
do
I
contribute
to
this
project
or
where
can
I
contribute
and
I
would
say
first
off.
We
we
welcome
all
contribution
in
the
next
spring,
like
anything
right
now
that
isn't
ready
to
start
is,
of
course,
for
I.