►
From YouTube: Magento PWA Backlog Grooming, 14 December 2018
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
This
is
the
last
holiday
edition
grooming,
we'll
have
of
the
the
year
2018
and
so
looking
forward
to
it,
making
some
good
progress
on
sorting
filtering
a
couple
items
here
from
the
community
on
curtain
checkout
and
possibly
some
some
new
ones
on
content
for
those
who
can
help
us
a
bit
during
the
holidays
here,
and
so
thank
you
again,
as
always
for
for
joining
us
and
you've
got
everything
here,
lined
up
in
Zen
hub
for
grooming,
based
on
some
things,
and
so
we're
just
talking
to
James
before
the
meeting
started.
You
know
yeah.
A
The
theme
for
today
is
really
to
pick
up
some
of
the
things
we
wanted
on
the
on
the
2.3
release,
but
you
know
had
some
had
some
some
roadblocks
I
think
in
terms
of
the
API
coverage
things
like
that
word,
they
might
be
roughed
out.
We
had
a
really
solid,
UX
and
design
for
things
like
sorting
and
filtering
bus,
but
just
because
of
some
of
those
dependencies
didn't
didn't
quite
make
the
cut.
So
the
good
thing
is
a
lot
of
it
is,
is
ready
to
go.
A
Certainly,
look
for
some
of
the
help
so
I'll
pick
that
up
and
drive
it
through,
but
here
that's
going
to
be
doing
some
of
these
things
that
we
know
would
be
part
of
any
any
reference
storefront,
but
ultimately
are
going
to
be
maybe
a
little
bit
a
little
bit
trickier
than
some
of
the
other
ones
we
had
before.
So
that's
why
we've
got
what
appears
to
be
a
pretty
full
house
today,
and
so
so
what
I've
done
is
brought
back
a
couple
of
these
items:
363
61,
which
is
sorting
and
filtering
respectively.
A
A
But
do
you
want
to
get
some
feedback
on
they
get
into
some
of
the
content
areas
so
had
a
good
suggestion
from
some
classy
llama
on
some
explorations
on
the
shop,
the
look
category
page
as
well
as
some
other
content
areas
that
can
potentially
be
done
in
parallel,
but
all
of
you
guys
hold
you
guys
all
accountable
to
us
Kiki
on
it,
so
that
we
can
do
this
outside
necessarily
creating
creating
any
additional
overhead
along
the
way.
So
any
questions
before
we
get
rolling.
A
All
right,
let's
do
this
so
number
360,
so
this
is.
This
is
one
that
we
originally
opened
back
in
October
and
the
idea
here
is
to
assist
to
bring
back
the
the
sorting
that
we
want
to
add
within
within
the
category
page
for
video-
and
you
know
sound
me
again,
put
together
a
you
know,
put
together
a
really
really
nice
prototype
for
the
in
envision
that
we
can't
really
walk
through,
but
essentially
bring
back
one
of
the
two
buttons
that
we
had,
that
we
pulled
out
of
2.3,
which
is
the
other
sort.
A
But
now
what
we're
going
to
do
here
is
pull
up
one
of
the
sliders
and
then
allow
for
shirt
by
sort
of
by
a
variety
of
criteria.
Does
the
shopper
you
want
to
be
able
to
at
the
filtered
sort
products
within
a
category,
so
you
can
maker
just
on
vinius,
but
we
probably
all
use
this
in
the
past
and
and
so
the
idea
here
is
this-
that
we
know
we
do
have
some
some
dependencies.
You
know
at
one
point
when
we
looked
at
this
and
look
beyond
that
repeat.
A
We
have
some
questions
on
things
like
server-side
render.
Some
questions
on
coverage
on
the
API
and
you
know
we
did
at
one
point
consider
some
some
discovery.
Some
discovery
relative
to
10.
This
10
must
be
covered
by
rap
duo.
Maybe
maybe
not
hopefully
do
we
need
to
fall
back
to
rest
and
you
know
is
there
an
iterative
way
to
look
at
it,
maybe
start
by
one
or
two
criteria
and
then
kind
of
go
on
to
do
the
other
criteria
as
well.
So
from
probably
can
UX
am
pretty
straightforward.
A
D
A
C
E
Yeah
so
yeah
some
some,
some
wonderful
folks
at
bargaining
did
a
pagination
PR
and
you
guys
can
feel
free
to
speak
to
it.
But
there
is
a
there's,
a
disconnect
between
the
pagination
that
the
user
performs
by
moving
between
pages
in
the
user,
experience
concept
and
the
underlying
pagination
or
like
cursing
through
collection,
that
the
graph
QL
API
supports,
which
is
right
now
still
a
little
bit
fuzzy
and
so
I'm
bargaining.
Please
take
up
arms
about
what
the
pagination
does
and
doesn't
do
that
you
want
to
that.
E
You
advocate
for
change
in,
but
the
underlying
methodology
for
paging
is
something
we
should
be
hooking
up
to
graph
Apollo's
systems
for
doing
that
which
are
great
ads.
Caching
and
that
doing
that,
all
the
proper
like
boilerplate
that
exhausts
a
page
set
and
prevents
infinite
looping
all
that
stuff.
So
we
know
that
there's
some
Delta
there
that
the
guys
at
bargaining.
What
do
you?
What
is
your
experience
with
the
paging?
It
yeah.
F
G
F
E
We
don't
need
to
dive
too
deeply
into
this,
but
basically
for
any
collection
like
the
products
collection,
which
is
probably
not
going
to
change
during
the
length
of
your
session.
You
don't
have
to
do
any
of
the
fancy
stuff
that
maybe
you
hear
whispers
about
about
how
graph
QL
iteration
ought
to
be
done
like
with
cursors
and
whatnot.
E
That's
something
that
makes
a
lot
of
sense
if
you're
dealing
with
like
something
super
live
Facebook
comments
where
it
may
change
as
you're
iterating,
but
for
a
product
selection
we
can
just
do
a
simple
type
of
pagination
that
involves
specifying
the
usual
pagination
parameters.
You
know
the
page
size
and
the
index
or
the
page
that
you're
on
whatever
and
that's
what
this
PR
does.
E
But
the
pagination
scheme
in
graph
QL
for
all
of
the
collections
in
Magento
I
think,
while
constant
I
think
that
it's
a
central,
centralized
interface,
we
haven't
actually
proven
that
out
super
hardcore,
so
I
think
we.
We
should
at
least
do
discovery
and
make
sure
that
the
pagination
and
the
way
that
you
kind
of
count
through
and
deal
with
collections
is
consistent
throughout
the
graph
QL
API.
Because,
if
experiences
any
judge,
there
may
be
weirdnesses
in
it
that
we
need
to
bring
up
with
draft
you'll
team
I.
Don't.
G
E
E
Cooper
you
want
to
go
on
I
feel
like
if
you're
paginating
through
a
tree,
you
would
be
doing
a
recursive
walk
in
this
case.
What
we're
getting
is
I
mean
for
the
pagination
peer
that
you
open
we're
getting
is
just
all
of
the
products
that
belong
to
a
category
which,
which
should
be
a
flat
collection
of
anything
that
belongs
to
this
or
any
subcategories.
So
I'm,
not
totally
sure
what
you
mean,
but
I
will
say
this.
We
could
get
deeply
into
technical
detail
here.
We
don't
need
to
I.
Just
wanted
to.
E
You
know:
ask
for
confirmation
from
somebody:
okay,
gotcha,
so
that's
that's
a
different
subject.
I
want
to
get
confirmation
from
somebody
that
it's
probably
wise
to
check
on
the
pagination
capabilities
of
graph
QL
collections,
especially
when
we
do
something
like
changing
the
size
of
the
collection
which
we
would
do
for
filtering.
Make
sure
that
the
page
information
that
comes
back
with
any
collection
is
correct
and
predictable
and
reliable.
I
think
that's
a
discovery
point
that
we
need
to
add
to
the
estimate
here.
A
Okay,
very
good.
Well,
as
you
can
see,
I'm
switching
gears
here,
I'm
gonna,
start
captions,
new
assumptions
and
so
I
would
say
or
that.
Certainly
that
is
a
task,
though
so
you
know
James
and
team
kind
of
keep
me
honest
on
what
does
what
this
looks
like
now,
so
I
think
we've
got
at
least
a
good
model
around
pagination
that
we
can
build
from,
but
other
other
than
that.
What
would
we
want
to
add
in
an
assumption?
A
E
Well,
the
pagination
thing
we've
just
surfaced
needs
to
be
listed
and
the
thing
that
we
already
did
know
that
is
probably
the
deepest
discovery
task
is
to
is
finding
out
what
the
graph
QL
API
in
the
current
edge
of
Magento
supports
in
terms
of
input
types
trying
to
think
of
a
way.
To
summarize,
this
just
say:
discovery
discovery
on
the.
E
Graph
QL
schema
to
support
variables
in
filtering,
sorting,
queries,
that's
what
we
would
call
it,
because
presently
it
doesn't
support
them
properly.
You
have
to
actually
edit
and
recompile
a
query
every
time
you
change
these
parameters
because
of
the
way
that
Magento's
graph
QL
builds
its
input
objects.
It
needs
to
be
a
proper
quote,
unquote,
input
type
and
last
we
checked
it
isn't.
But
this
is
why
we
would
love
to
have
like
a
Misha
or
someone
else
from
graph
QL
in
these
groomings.
E
E
Variable
support
we
can
go
into
a
demo
so
that
people
aren't
completely
mystified
about
what
we're
talking
about
if
you'd
like,
but
suffice
it
to
say.
If
you
have
a
working
instance
right
now,
then
you
can
launch
your
graph
QL
playground
and
go
into
that
get
category
query
to
see
how
it
pulls
back.
A
product
selection
and
you
can
look
in
the
documentation,
schema
tab
to
see
all
the
ways
that
you
might
be
able
to
filter
it
and
playing
around
with
variables.
You'll
find
that
it
doesn't
do
some
of
the
basic
stuff
we
really
need.
B
Also
have
a
request:
I,
don't
know
if
it's
this
big
there
issue
or
for
a
separate
one,
but
could
the
current
options
be
reflected
back
into
the
URL
as
well
playing
with
pagination
and
I,
see
that,
like
the
current
page,
isn't
indicated
in
the
URL,
so
ensuring
that
when
you
do,
that
for
sorting
would
be
great.
Thank.
E
You
Rowan
very
good
catch
and
that's
actually
something
I
think
deserves
to
be
opened
as
a
bug.
That's
kind
of
a
judgment
call
but
I.
Think
that
not
being
able
to
link
to
a
place
in
a
paged
collection
is
not
I
mean
I
did.
May
it
may
be
ok
to
go
out
for
MVP,
but
it's
it's
not
an
acceptable
like
state
to
be
in
so
we
definitely
need
pages
to
be
routed
and
filter
and
sort
states
to
be
routed.
That's
a
that's
a
hard
requirement.
This.
E
A
Boom,
so
this
one
specifically
that
I
toured
sorting
but
yeah
that
degree
week
I
think
we
can
set
up
something
in
addition
to
to
see
how
that
affects
things
like
pagination
as
well.
So
it's
a
larger
one,
sweet
cool
all
right,
just
checking
the
remaining
assumptions
and
tasks
here.
Most
of
the
assumptions
seem
to
be
in
play.
They
could
still
being
considered
server-side
that
they
talked
about
the
dependency
on
collection,
filtering
variables,
tasks,
dozens
doing
a
lot
of
discovery,
but
that's
okay,
right,
yeah,
the
primary
output.
A
A
E
A
You
guys
remember
from
the
demo
we
about
we've
moved
away
from
an
ideal,
starting
with
the
number
one.
We
are
we're
now
fully
confident,
so
we're
going
to
move
away
from
that
and
hopefully
be
breaking
these
down
at
the
bite
size.
Just
a
you
know
a
few
day
type
of
pieces
for
folks
to
pick
up
from
that,
and
so
we'll
skip
that
one
and
I'll
play.
That
is
that
their
news,
but
for
those
who
weren't
there
at
the
demo,
that's
that's
how
we
are
rolling.
It's
all
go
ahead
and
add
this
into
adolescent.
A
You
are
ready
to
start
and
we'll
end
up
date,
this
so
cool.
Thank
you,
everybody!
Thank
you.
Alright.
With
that
in
mind,
maybe
some
copying
pasting.
This
one's
gonna
be
a
little
bit
a
little
bit
more
complex,
but
but
really
builds
off
of
what
we
just
talked
about
for
for
sorting.
So
this
one
is
number
361.
This
is
still
during
for
category
so
based
on
what
we
just
talked
about.
What
sorting
against
Omni
has
been
done.
A
A
really
nice
job
talking
through
and
walking
us
through
the
other
prototype
for
this,
and
so
the
filter
criteria
again
size
price
brand
color
and
we've
seen
a
couple
different
permutations,
even
on
some
recent
pw8
solutions,
they're
out
there.
But
you
know,
there's
definitely
the
need
to
look
at
some
discovery.
Work
around
that
base
out
some
of
the
foundational
things
we've
just
talked
about
with
with
sorting
sorry
something
to
be
done,
probably
prep
before
this,
and
so
we
still
have
this
linked
as
a
dependency.
A
A
As
you
picked
up
from
pick
this
up
and
started,
defining
this
back
in
October,
very
straightforward
or
anyone
who's
built
in
the
past
is
a
shop
where
you
want
to
filter
products
within
a
category,
so
you
can
make
a
purchase.
You
should
be
based
programmatically,
based
on
sample
Vande
data,
which
is
part
of
this.
A
You
know
these
attributes,
as
you
seem
at
least
currently
in
the
sample
data,
include
things
like
fashion
material
file,
color
at
price.
The
assumptions
are
fairly
straightforward,
although
we
probably
want
to
copy
some
of
the
items,
or
at
least
reference,
the
ones
from
sorts
based
on
the
graph.
Well
he's
there,
but
that's
kind
of
it
so
I'm
gonna
make
some
of
these
came
to
surface
than
what
we
just
talked
about.
But
while
I
do
that,
are
there
any
questions
or
comments
on
the?
C
Within
a
category
like
the
touch
area,
for
that,
it's
kind
of
small,
because
the
the
height
on
the
action
filtering
the
corniest
in
Java,
it's
not
that
tall
yep,
so
I
do
foresee
changes
coming
to
that
fog
of
Bui.
But
apart
from
that,
this
is
sort
of
out
of
the
full
filtering
designs
that
we
showed
shoppers
a
while
ago.
This
is
the
one
that
kind
of
resonated
Rumble,
so
I
think
it's
a
safe
bet
for
now.
Apart
from
that,
one.
C
A
I'm
capturing
as
faithfully
as
there's
an
assumption
here,
so
there's
work
in
progress.
You
could
be
addressed
in
the
future.
I
think
yeah,
I,
agree,
I!
Think
as
you
play
around
with
ourselves.
They
find
that
there's
a
there's,
a
kink
or
two
from
above
until
we
actually
have
that
out
there.
You
know
I,
think
you
know
that
I
think
it's
a
really
good
first
step
and
it's
based
off
the
residential
research
I.
A
C
E
Faceting,
epic,
perhaps
is
the
word
that
faceting
is
an
old
school
word.
I,
guess
that
I
still
use
to
refer
to
this
whole
dimension
of
customizing,
a
collection
with
filters
and
sorts
etc
and
pages
to
to
be
what
you
want
to
look
at,
because
the
sorting
and
filtering
have
so
many
common
dependencies
and
common
questions
that
you
ask
to
the
graph
QL
team
that
you
know
you
could
copy
paste
it
for
now,
but
I
think
it
makes
sense
for
there
to
be
an
underlying
epic.
D
A
E
G
B
A
A
A
All
right,
actually
speaking
of
Adrienne
on
this-
and
this
is
actually
a
question
to
this
omnia
one
of
the
things
I've
seen
on
some
of
the
work
that
Adrienne's
done
and
oh
there's
the
idea
of
going
between
different
views.
This
view
versus
more
of
a
thumbnail
or
kind
of
grid
view,
and
so
I
know.
That's
not
so
we
have
even
envisioned
in
the
past,
but.
B
A
C
H
C
So
the
reason
I
took
it
out
from
the
earlier
design
is
a
they
were
trying
to
stem
and
and
keep
things
clean,
but
I
would
welcome
any
data
or
study
that
has
you
know
good
indicator
of
this.
That's
particularly
useful
on
mobile
and
I
would
say.
If
that
doesn't
exist,
then
I
don't
see
that
there's
justification
just
because
it's
something
that
we
can
do
up
on
desktop
I
can
definitely
be
ready.
D
A
To
our,
you
know
to
our
gorgeous
experience
here
we
are
on
Bennion,
so
you
know,
for
every
case
needs
to
be
made
where
I
do
think
that
the
capability
that
someone
would
want.
So
if
you
look
at
venya
as
the
purpose
of
a
reference
team
that
somebody
will
want
someone's
gonna
want
it
right,
but
if
the
purpose
is
really
a
demo
that
really
shows
a
clean.
You
know
you
know
a
cleaning
that
simple
approach
to
that's
another
consideration.
We
render
this
all
the
time
right
now,
maybe
maybe
just
maybe
Oh
mister.
A
C
D
C
A
How
about
this,
maybe
it
maybe
we
can
ask
those
questions
lightly
differently,
because
I
think
this
is
going
to
run
into
other
new
experiences
features
components.
Would
there
be
any
that
so
would
this
be
a
component
take
agnostic
from
venya
they're,
a
because
they're?
So
if
you
look
at
a
component
being
useful
independent
of
Enya,
is
this
one
consent?
Would
this
be
considered
a
component
think
so?
But
you
guys
be
honest
on
that:
the
terms
of
the
division
so.
H
A
E
Absolutely
implement
this
as
a
view
component
that
has
that
has
no
UI.
A
great
example
for
this
is
that
there's
a
popular
drop-down
library
and
react
by
endless
self-promoter
Kent
Dodds
called
downshift.
That
effectively
is
just
all
of
the
boring
plumbing
work
of
doing
a
great
audio
complete
drop
down,
but
it
lets
you
use,
render
functions
to
give
it
all
of
the
pretty
stuff
the
UI
and
that's
a
great
example
of
the
kind
of
react
component
work
that
I
think
people
don't
typically
associate
with
react.
E
Oh
this
is
just
a
conceptual
component,
but
that
it
turns
out
people
really
love
using
and
something
that
digests
all
of
the
graph
QL
plumbing,
and
you
know,
introspection
and
options
building
necessary
to
just
get
the
data
for
populating.
Here's
how
you
can
filter
menu
is
that's
it,
that's
a
very
great
candidate
for
paragraph
because
Peregrine's
is
you
know
it
already
contains
some
Magento
specific
stuff,
and
really
this
is
just
take
the
graph
QL
API
that
has
these
features
and
turned
it
into
a
drop-down
that
does
this
totally
a
great
component.
A
You
I
don't
think
we
need
to
do
a
little
bit
of
research
internally
on
this.
One
I
just
want
to
use
this
as
a
forum
to
kind
of
talk
through
that
possibility.
It
will
come
up.
It
will
be
a
feature
request.
It
was
something
more
complex,
but
I
think
I
just
want
to
pressure
test
the
audience
on
how
that
would
look,
since
we
were
kind
of
on
topic
relative
to
just
sort
of
get
sold
right
so
appreciate.
E
C
A
A
Thank
you,
everybody
all
right,
so
the
next
one.
This
is
actually
I,
believe
a
bar
Greenland.
So
this
one
yes,
so
this
is
a
edit
car
configural
product.
So
what
I
did
was
clone
a
suggestion
that
was
you
know
that
was
brought
forth
by
by
some
of
the
folks
in
bar
green.
So
now
that
we've
got
a
configurable
computable
cards,
I'm,
sorry
configurable
products.
You
know
we
also
would
now
want
to.
You
know,
bring
this
into
a
situation
where
we
get
of
that
cart
as
well.
So
this
is
a
bit.
You
know
this.
A
One
is
a
bit.
You
know,
you
know
early
the
early
and
ahead
of
you
acts
but
I
think
there's
a
an
opportunity
to
do
some
discovery.
Work
where
we
can.
You
know,
potentially
make
some
of
those
edits
based
on
what
we,
what
we
had
inside
of
product
details
to
begin
with,
for
that
one.
So
maybe
I'll
just
kick
this
off
to
the
folks
to
the
folks
in
five
here.
I
think
it's
a
good
idea,
it's
something
that
was.
G
Well,
you
know
it's
we're
not
exactly
UX
designers,
but
just
as
far
as
I
was
we
can
totally
reuse
a
lot
of
the
same
components
that
were
obviously
in
product
options
like
the
color,
selectors
and
stuff,
like
that.
So
it's
gonna
be
a
lot
of
reusing
and
then
basically
just
bring
in
that
item
ID
and
then
you
know
finding
a
way
to
to
this
a
little
bit
discovery
of
graph
qo.
Just
updating
the
the
cart
like
that
after
editing,
an
item
but
other
than
that
I
don't
really
have
any
info
on
the
design.
A
A
A
A
A
A
All
right
other
ones
here
this
one
is
believe
this
one
is
an
Adrian,
so
this
one
is
more
also
MAF
a
discovery
type
as
well,
and
so
again
this
one
isn't
necessarily
leading
leading
the
UX
by
any
means,
but
I
think
opens
up
a
pleasure.
I
am
a
dependency
ticket
for
for
Sami
to
kind
of
think
about
what
what
the
idea
around
total
subtotal
and
dependency
dependencies
might
be.
Might
look
like
relative
to
what's
happening
here
it
so
clearly.
This
is
something
that
happens
in
those
sites.
A
A
A
To
solve
for
this,
one
I
take
from
a
product
standpoint,
I
think
I
would
resent
definitely
should
should
have
a
solve
for
this
in
terms
of
in
terms
of
what
there
should
be
for
venya,
but
but
I
do
want
to
make
sure
that
Sammy
I
thought
as
the
time
to
kind
of
take
a
look
at
this.
In
parallel
to
the
suggestion.
So
yeah.
C
C
Since
the
screen
was
initially
designed
and
hasn't
changed
very
much
because
it's
gonna
be
not
that
implementation
on
it
is
ongoing.
So
yeah
I
also
have
a
chapter
Jimmy
here
and
I
love
to
do.
Ticket
and
I
know
that
there's
another
one
that
Brendan
commented
on
as
well
that
I
am
with
Jimmy,
so
I
would
respond
to
all
of
those
cool
that.
B
A
C
A
A
This
idea
around
some
of
the
CMS
concept,
writing
so
I
think
I.
Think
our
demand
in
others
way
you
know
well,
is
the
pastor
that
started
us
out
off
on
a
path
with
things
like
sliders
galleries,
others,
but
you
know
we're
kind
of
an
in-between
state
with
someone
more
interactive
content,
that's
out
there
and
so
there's
a
couple
of
things
that
are
in
flux
in
a
review.
A
A
B
C
Has
custom
images
that
have
a
light
gray
background
and
we,
the
carrots
that
indicated,
looks
much
better
in
that
one.
The
issue
with
Pena
major
is
that
or
images
that
they
all
I
think
mostly
have
a
white
background
and
so
I
don't
know
that
it's
it's
working
as
well,
but
double
minor.
A
minor
visual
men.
A
A
A
Included
in
that
beer,
so
I
believe
that
if
I
remember
correctly,
there
is
these
appear
to
fix
the
indicator,
but
this
one
is
more
about
having
this
actually
work.
Work
more
like
a
like
a
carousel
I.
Think
there's
two
two
pieces
of
that,
though,
because
my
question
would
be:
is
there
enough
here
for
for
someone
to
to
pick
up
and
get
started
on
that
I?
Don't
know,
I
know,
there's
some
dependencies
does
this.
You
know
this
diametrically
opposed
anything.
We
want
to
consider
per
component.
E
Think
I
think
so,
there's
a
lot
of
questions
but
hardly
anticipates
the
order
that
the
questions
will
need
asking.
Certainly
this
is
the
tip
of
the
iceberg
of
swipe
interactions
and
there's
a
number
of
different
touch.
Libraries
that
I
have
experimented
with
and
for
the
warnings
that
I
received
have
been
less
than
efficient
less
than
performance,
so
it's
big
and
we
at
least
know
that
there's
going
to
be
sort
of
a
touch
interactions
in
Peregrine's
story.
E
C
D
Much
I
mean
my
understanding.
We
have
have
a
component,
but
we
want
to
finish
it
did
I.
It
is
how
many
multiple
images
it's
a
project
for
switching
the
image
right
at
its
core.
Yes
right
and
so
I
believe
this
is
actually
already
responsive,
desktop
it.
It
pulls
those
thumbnails
out,
Google
yeah.
It
says
images
on
the
side
when
you
have
all
real
estate
section
shown
so.
A
We're
really
just
talking
about
wiring
doc,
right,
I,
think
so.
Yeah
I
mean
it
very,
very
least.
The
thing
wiring
it
up
would
be
step
one
being
able
to
effectively.
You
know
paginate,
somehow
a
lien
I
think
you
know
it
would
come
in
with
thinking
that
everything
is
equal,
but
I.
Think
if
there
are
there
situations,
we
need
to
break
this
down
between
click
and
touch.
I.
Think
that's
I,
think
that's
fair
game
through
so.
E
Yeah
and
I
didn't
mean
to
suggest
that
somehow
you
were
demanding
touch
of
swipe
interactions.
I
just
know
that
that's
going
to
be
sort
of
an
immediate
subject
of
concern
about
this.
This
is
the
so
far.
I
think
this
is
the
most
prominent
place
where
people
generally
expect
there
to
be
a
swipe
interaction,
but
that
doesn't
mean
that
it's
MVP
Jimi's
instinct
is
right
on
to
cover
that
as
a
decoration,
yeah.
D
A
A
A
H
A
F
H
A
That's
really
what
we
had
to
cover
today.
One
of
the
things
I
do
want
to
cover
probably
offline,
because
quite
a
few
people
aren't
recall,
but
I
do
want
to
start
thinking
about
some
really
easy
kind
of
quick
content
items
or
to
bring
over
from
basically
old
many
it's
a
new
venue.
Yet
so
for
those
who
those.
A
That
is
art,
luma,
Park
venya,
to
be
honest
from
an
MVP
standpoint,
is
probably
okay,
that's
form
as
a
reference
tour,
but
would
be
good
fodder
for
someone
who
is
looking
for
a
good
first
issue
to
start
bringing
in
contact
us
customer
service,
those
types
of
things
not
the
highest
priority.
But
if
you
look
at
parallel
and
with
so
many
people
joining
the
project,
it's
a
good
way
to
understand
our
process.
A
How
we
work,
how
to
make
some
immediate
contributions
and
then
in
parallel,
we'll
be
tackling
some
of
the
some
of
the
trickier
things
together
like
sorting
and
filtering,
and
we've
got
some
work
ahead
of
us
around
accounts.
And
if
you
look
at
the
the
road
map,
we
also
have
some
some
work
around
the
commerce
or
former
EEG
vision
with
wish
lists,
and
things
like
that
that
are
kind
of
next
next
in
order
from
a
UX
standpoint.
But
there's
there's
the
credibility
here.
A
That
I
think
makes
for
a
pretty
solid
place
over
content,
but
we
want
to
kind
of
pull
that
in
and
would
also
pressure
test
some
of
the
things
that
we
have
around
CMS
as
well.
So
I'll
do
some
of
these
offline
I
will
spare
you
guys
from
our
three
type
on
that
one,
but
I
do
want
to
get
a
couple
of
these
out
there,
and
then
there
are
some
teams
that
are
probably
looking
for
some
things
to
do.
A
F
E
E
We
share
hopefully
kind
of
a
mutual
understanding
about
where
we've
let
that
flex
a
little
in
order
to
get
feature
work
done,
but
you
know
the
the
same
attitude
that
led
to
a
react
component
with
no
UI
in
the
case
of
downshift,
this
sort
of
creative
desire
to
separate
the
cool
dev
facing
stuff
from
the
merchant
facing
skin
stuff,
like
that,
we
can
apply
that
attitude
unilaterally
over
everything
we've
made
in
vignette.
Okay.
What
part
of
this
is
just
venía
and
it's
look.
You
know
the
CSS
modules
we
are
importing
them
directly.
E
Is
there
a
way
to
get
them
in
here?
Just
applying
that
ruthless
architectural
eye
to
everything
we've
implemented
in
venía
I
think
will
lead
to
some
immediate
stories
or
suggestions
about
how
to
pull
things
out
and
begin
having
the
Peregrine's
concept
take
shape.
I.
Think
a
root
component
factories,
a
great
idea,
I,
think
having
a
Magento
route
handler
belong
to
Peregrine
and
the
implementations
of
the
actual
Magento
routes
in
Peregrine
be
something
that's
declarative.
E
I
I
know
that
these
are
all
kind
of
vague
concepts,
but
I
think
laying
them
out,
brainstorming
them
and
then
coming
up
with
the
ones
that
help
you
and
your
website.
First
of
all
will
get
some
stuff
onto
the
board
that
we
can
then
prioritize
for
your
guy's
sake.
I
mean
we
more
than
owe
it
to
you.
So
what
do?
E
E
D
If
everybody
wants
to
use
them,
you
know
if
it's,
if
it's
something
where
we
build
it
and
it's
technically
configurable
and
style,
but
it
it's
a
pain
to
use
the
API.
Or
you
know
you
can't
you
can't
really
customize
it
in
the
ways
you
want
people
don't
use
it.
All
it
is
is,
is
a
is
a
negative
contribution
right.
So
we
really,
we
really
want
to
get
the
Peregrine
components
right.
You
know
the
bar
is
going
to
be
higher
preparing
for
things
to.
D
There's
a
reason
why
we
only
have
a
handful
and
they're
so
far
away,
I'm,
really
tackling
women
we've
been
trying
to
get.
We
were
trying
to
get
something
that
really
suits
Benyus
needs,
but
we're
all
of
us
are
going
to
have
to
really
focus
on
the
API
and
or
have
to
pay
attention
to
links
that
one's
talking
about
what
what
the
trends
are
for
building
configurable
components
on
how
that's
going
to
go
in
2019
and
then
and
then
once
we
like.
They
pick
a
direction
to
run
and
then
we'll
start
running
here.
F
H
E
E
Let's
say
that
Magento
is
one
of
a
small
handful
of
adapters
for
a
general-purpose,
Peregrine
PWA
library.
Have
you
guys
used
eval,
a
plus
because
they're
your
locals,
you
know
I'm
talking
about
no,
no
okay.
Well,
Valley
Plus
is
a
PHP
local
handling
like
a
little
bit
like
node
version
manager
for
running
local
PHP
websites.
It
was
originally
built
for
laravel.
It
got
adapted
into
more
general-purpose
framework,
but
ballet
is
really
something
people
only
use
to
like
run
on
the
Gento
site
or
a
wordpress
site,
or
one
of
the
like
major
PHP
projects.
E
So
it
has
adapters
that
are
this
first
class
concept,
it'll
check
your
folder
and
say:
oh,
this
is
the
Magento
site.
I
know
how
to
handle
a
route
to
this
in
the
same
in
the
same
way,
I
think
Peregrine
is
a
quote-unquote
general-purpose
library,
that's
not
just
marketing
speak.
We
want
it
to
include
stuff
that
works
on
not
Magento,
but
there's
probably
gonna,
be
a
whole
lot
of
Magento
specific
stuff
in
there
that
we
would
just
say
bundle
up
into
a
hero.
Your
Magento
thing,
this
type
of
folder.