►
From YouTube: PWA Studio Community Meeting 21 February, 2020
Description
PWA Studio 5.0.1 patch contents and a demo for Category Sorting feature
A
Great
alright,
happy
Friday,
everybody
welcome
for
another
weekly
community,
sync
and
demo.
Today
we
have
a
couple
of
topics
if
you're
paying
attention
on
a
repo
or
what
we've
been
doing
on
our
side.
We
released
a
patch
just
yesterday,
so
we'll
kind
of
go
through
some
of
the
contents
of
that
patch.
Why
a
patch
was
necessary.
They've
taught
me
to
talk
about
a
couple
of
those
items
that
we
have
a
demo
from
Lars
on.
The
line
has
been
working
on
sort,
a
category
story
and
then
we'll
kind
of
open
it
up
to
anybody.
A
B
Alright,
so
yes
in
the
scope
of
this
patch
release
that
we
did
it
initially
was
a
big
chrome
bug
fixed
week.
I,
don't
think
anything
changed
with
the
actual
fix,
I
think
we
were
under
like
Safari
thing,
but
I
think
vastly
was
responsible
for
that.
So
this
bug
fixes
good
visibility,
hidden
rocks,
but
we
found
another
thing
that
we
wanted
to
slip
in.
There
is
more
just
about
like
best
practices
and
kind
of
like.
Let's
call
this
like
I
didn't
know,
that's
how
that
worked.
Tommy
corner.
C
B
We
are
heavy
users
of
Apollo
and
kind
of
couple
of
little
extensions
of
Apollo
that
we
use
our
in
memory.
Then
we
also
use
Apollo
cash
persist,
so
Lars
is
very
familiar
with
us.
He
created
a
PR
because
he
was
having
issues
with
this
fancy
Apollo
dev
tools
that
you
can
have,
and
this
gives
you
a
nice
access
to
Apollo's
in-memory
cache.
This
is
usually
something
that's
very
privileged
access
if
I
went
to
develop,
PWA
I
should
not.
D
B
Using
catch
persist
where
this
catch
gets
persistent
to
local
storage.
So
before,
if
you
didn't
even
have
this
Apollo
extension,
you
could
go
into
your
local
storage,
see
this
big
Apollo
cache
persist,
object
which
has
a
bunch
of
fun
stuff
in
it.
So
we
just
kind
of
write
it
in
5.0
we
started
making
heavy
use
of
Apollo
and
kind
of
just
you
want
to
make
sure
that
we
put
our
best
foot
forward
and
kind
of
make
everyone
aware
of
these
best
practices
that,
when
you
are.
D
B
Apollo,
in
the
way
we
are
with
these
two
different
extensions.
You
want
to
be
very
aware
of
the
fetch
policies
that
you're
doing,
though
there
were
a
few
areas
where
Apollo
was
just
kind
of
over
caching
and
there's
kind
of
this
edge
case
where
you're
on
a
public
computer.
Somebody
could
maybe
tap
into
this
cache
or
you've
brought
site
scripting
infiltrated
to
your
site.
They
could
maybe
access
this
cache.
B
So
you
should
just
be
very
aware
that,
like
any
mutations
that
you
have
in
here
that
have
kind
of
these
default,
cache
policies
may
show
up
in
here.
So
if
there's
anything
sensitive
that
you
don't
want
showing
up
in
this
cache,
you
just
need
to
use
a
no
cash
policy
and
it
won't
show
up
that.
Has
that
has
some
performance
implications
where
Apollo
is
going
to
hit
the
network
every
time
it
needs
that
data
it
won't
use,
is
kind
of
back
in
Redux
cache
to
kind
of
improve
performance
there,
but
that's
the
trade-off.
B
Don't
catch
anything
that
you
want
to
want
kind
of
exposed
to
any
other
public
people,
so
it's
probably
like
catalog
stuff,
catalog
stuff
is
fine,
but
when
it
comes
to
like
checkout
and
user
information,
you
want
to
make
sure
that
you're
setting
the
appropriate
cache
policy
but
I
think
mister
terranova
working
on
an
internal
blog
post,
maybe
that
it
become
like
a
public
customer-facing
blog
post
as
well.
Yeah.
E
E
B
E
B
So
here's
an
example:
this
is
a
redeads
action,
but
if
you
didn't
want
something
to
be
cached,
all
you
do
is
pets
s
edge
policy,
no
catch
and
then,
in
this
blog
post,
I
think
we're
still
firming
up.
What
are
a
suggested
solution
is
it
doesn't
affect
Vimeo
right
now,
but
there
is
a
weird
default
behavior
where,
when
it
does
cache
group
mutations,
like
sometimes
you
may
want
to
cache
the
mutation.
B
A
A
F
A
G
G
Third,
information
is
my
first
red
component
and
it's
my
first
thing:
what
I
did
an
open-source
project
with
react
and
yeah
I
learned
a
lot
and
it
showed
it
doesn't
not
so
much,
but
it
does
many
things
behind
because
it
fetching
the
data
of
the
category
page.
It
sends
the
correct
craft
query
to
the
server
and
really
render
the
category
page.
So
what
I
did
there
is
I
create
a
new
component,
a
category
and
I
accent.
The
category
root
component
there,
it's
I,
add
there
on
my
component
and
ricky
said,
though.
G
My
point
there,
what
I
did
wrong
or
I
didn't
understand
was,
is
how
I
can
put
a
click
handler
from
the
main
page
to
my
component,
because
what
I
need
is
a
shade
item
that
will
change
the
sorting
of
the
category
page.
For
that
reason,
I
have
registered
some
available.
The
sort
methods
like
best
match
is
sort
by
attribute
relevance
and
voting
from
high
relevance
down
to
low
relevance
and
with
this
property
you
can
extend
your
own
sorting
methods.
If
the
attribute
is
sortable
of
our
craft
gone,
it's
yeah.
G
C
B
Chime
in
as
well,
you
know,
I
worked
a
lot
back
and
forth
with
him
on
this
particular
PR.
You
know
had
a
lot
of
rounds
of
feedback
here
and
I
left.
You
know
dozens
of
comments
on
it
right,
and
this
is
one
of
those
cases
where
we
had
a
feature
that
we
needed
right.
That
was
small,
but
we
had
UX
feedback
in
the
beginning,
right
that
required
some
rework
and
he
incorporated
that
and
then
there
were
particulars.
As
you
all
know,
about
how
patterns
we
use
in
the
code
base.
B
Write
minor,
react:
optimizations
tricks
to
memoization
right,
like
there's
a
lot
of
small
things
to
know
about
how
exactly
we
write
code
in
this
particular
Probus
and
in
each
of
the
cases
Varzi
they're
just
incorporated
the
feedback
straight
away,
or
you
know,
figured
out
what
we
were
talking
about
and
I
figured
out
how
to
right
it,
and
so
that's
how
we
got
to
this
PR
work
being
approved.
You
know
being
shown
off
to
them.
A
Individual
conversations
were
having
I
know.
There
are
a
number
of
you
out
there
that
are
looking
to
contribute
and
looking
for
work
to
pick
up.
We
have
been
working
along
with
Jordan
a
community
maintainer
to
make
sure
that
we
define
a
good
process
for
making
sure
or
curating
an
amount
of
work
that
can
be
easily
picked
up
and
Tommy
who's
over
here.
Helping
us
now
is
our
community
liaison
right
make
sure
we
have
a
curated
list
of
work
that
anybody
in
the
community
that
wants
to
contribute
can
easily
pick
up.
A
We
have
a
footwork,
we
put
together
an
initial
view
of
a
board
and
we'll
start
working
against
and
we're
really
working
to
kind
of
improve
kind
of
the
outline
of
the
process
before
we
introduce
it
on
an
upcoming
call,
and
we
start
kind
of
adhering
to
that
process
and
kind
of
contribution,
guidelines,
and
things
like
that.
So
all
of
that
is
coming
it's
on
the
way
so
ahead
of
time,
we'd
say
thank
you
to
everyone
that
is
contributing.
We
welcome
any
kind
should
be
contribution,
any
form
that
we
get
it.
A
Thank
you
for
Lars
or
kind
of
a
work
on
sorting,
but
and
and
we're
on
a
daily
basis,
working
to
improve
kind
of
the
process
of
ensuring
we
can
improve
the
community
engagement
and
community
contributions.
So
a
lot
of
words
just
to
say
we
hear
you
we
are.
We
are
working
to
improve
the
process
and
thanks
all
for
the
repair,
everyone
for
sticking
around
and
being
so
interested
in
PWA
studio
and
wanting
to
help
out.