►
From YouTube: PWA Community Update May 3rd, 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
Right
so
yet
today
we
have
a
few
updates.
Mr.
Selim,
you
said
you
want
to
go
last,
so
I
think
it
him.
So
we
have
some
updates
or
CI
CD,
which
I'm
assuming
we'll
wait.
For
last
we
have
the
URL
for
software
updates.
Mr.
calamy,
it
has
some
Docs
updates
and
then
Andy
I
think
you've
got
some
recent
merges
that
you
can
take
over
and
I
think
last
after
mr.
stone,
we'll
talk
about
the
Help
Wanted
tickets,
because
I
think
that
would
be
a
really
quick
conversation.
So
who
wants
to
go
first.
B
C
B
Of
create
account
page,
so
we
had
to
kind
of
input
components
basically
for
lack
of
a
better
term,
an
old
one
that
anyone
and
people
were
getting
confused
about
which
one
they
should
be
using.
So
this
PR
actually
removes
the
old
input
component
so
that
there's
no
confusion
on
which
one
we
should
be
using
that
the
one
we
should
be
using.
Is
this
text
input
component,
so
it
updates
every
where
we
were.
We
were
using
the
old
input
component.
B
It
also
removes
this
like
error,
display
component
and
I'll
demo,
this
stuff
in
just
a
minute,
so
you
can
see
where
it
is,
but
it
updates
the
sign-in
page,
the
create
account
page
and
the
forgot
password
page
just
to
match
their
mocks.
A
little
bit
closer
I
backed
off
a
little
bit
on
the
create
account
page
cuz,
there's
a
community
PR
at
number
35,
but
it
does
a
lot
of
that
work
already
so
I
didn't
put
it
in
this
PR
and
then
there's
a
slavery
factor
to
the
redux
user
slice.
B
So
this
is
what
is
out
there.
Currently,
this
is
before
the
change.
If
you
come
into
the
signing
and
I'm
gonna
purposefully
mess
this
up
the
sign
in
well,
it's
showing
my
new
stuff,
we
deployed
it.
It
wasn't
like
this
ten
minutes
ago.
Okay,
that's
the
new
step
before
you
would
get
this
big
ugly,
like
error
message,
looking
thing
that
would
give
you
a
whole
server
stack
trace,
which
we
don't
want
to
do
anymore,
so
it
just
gives
you
this
kind
of
nice
friendly
message
here
that
your
stuff
was
incorrect.
B
B
E
I
think
we
need
to
discuss
the
way
that
we
do
form
field
validation.
This
time
is
completely
different
than
that.
I
think
we
need
to
discuss
if
this
is
a
this
needs
to
be
attached
to
a
field
in
the
form
or
if
it
needs
to
be
a
toast,
because
if
this
is
different
than
circles
of
those,
so
yes
I
mean
we
I'd
like
to
default
to
one
or
the
other
I
think.
If
that's
fine.
B
We're
out
of
these
fields,
then
it's
gonna
have
to
put
something
in
there.
Oh,
this
was
a
bug.
So
if
you,
if
you
put
something
in
here-
and
you
click
forgot
password-
they
forgot
password
it
seeds.
This
field
in
here
that
wasn't
working
previously,
so
I
fix
that
problem.
It
also
actually
does
that,
on
the
create
account
form,
it'll
see
this
email
field.
Here
you
can
see.
Some
of
these
fields
are
now
marked
as
required,
which
is
cool
and
there's
a
subscribe
checkbox
that
wasn't
there
before
but
was
in
the
mock.
So
that
looks.
E
B
B
So
there's
a
before
when
you
had
sign
in
there
was
kind
of
this
weird
delay
as
I
was
making
the
call,
and
you
would
just
sit
and
look
at
the
page
that
wasn't
doing
anything
for
a
while,
so
I
just
put
a
little
spinner
in
there
while
you
were
signing
in
you
can
also
notice
down
at
the
bottom
after
I
sign
in
down
at
the
bottom.
Here.
There's
like
I
forgot
what
it's
called
user
information
component
I.
B
Think
where
it'll
show,
like
your
name
and
all
that
kind
of
stuff,
so
you
notice,
when
you
sign
in
it
kind
of,
has
a
little
bit
loading
first
and
then
it'll
pop
in
and
that's
the
best
due
to
the
the
refactor
here
at
the
store.
So
we
were
going
to
get.
We
sign
the
person
in
and
then
we
got
all
of
the
details
and
then
we
came
back,
which
was
a
little
inconsistent,
we're
doing
like
card
actions,
for
instance.
B
E
F
E
B
H
So
there's
a
minor
bug
that
popped
up
related
to
EMV
configuration
I,
believe
if
you
left
out
a
trailing
slash
in
your
magenta
back
in
URL.
Everything
just
aired
out.
Nothing
worked
so
to
remedy
this.
Instead
of
doing
like
EMV
validation
on
that
value,
we
thought
it'd
be
valuable
to
add
a
URL
resolver
to
upwards,
so
upward
can
handle
building
URLs
for.
I
C
H
In
a
more
kind
of
composable
way,
so
the
first
step
of
adding
anything
to
upward
is
to
update
the
specs.
So
this
is
the
spec
for
the
URL
resolver
you'll
see
that
it
follows
this:
what
WG
spec
compliant
URLs
dealio?
That
seems
to
be
what
the
yes
URL
object
follows
as
well,
so
that
was
kind
of
just
easy
on
the
upper
JSI
to
just
follow
that
spec.
But
you'll
see
it's
very
straightforward.
It
accepts
a
bunch
of
parameters
that
will
build
a
URL
like
base
URL
ash.
H
It
also
accepts
relative
URLs
if
you
pass
false
to
the
base
URL,
so
you
don't
absolutely
and
relative
URLs
and
then
the
implementation
side
of
this.
There
were
very
few
places
in
the
upward
configuration
of
Benia
that
we're
using
URLs,
but
the
two
places
that
were
we
went
ahead
and
updated
and
you'll
see,
instead
of
using
like
mustache
templates,
to
build
a
graph
QL
pinpoint
by
appending
forward
slash
grab
QL
to
whatever
your
back
end.
Url
was
you
can
now
compose
it
with
the
base
URL
and
provide
the
path
name
of
gravity.
H
H
J
K
K
K
C
G
No,
no
I
understand
that
you
explain
kind
of
the
best
practices.
Reason
for
that.
I
think
that
the
caveat
should
be
that,
because
of
this
change,
you're
no
longer
going
to
be
able
to
see
the
detailed
test
results,
output
from
poll
requests,
so,
as
a
community
member,
we
hate
depriving
you
or
removing
your
access
to
something,
but
it's
for
security
purposes,
so
feel
free
to
talk
to
us
about
how
we
might
maintain
some
kind
of
help
system
for
you
guys
to
set
up
your
own
continuous
integration
environments
for
your
own
PRS.
G
H
Worth
noting,
like
danger,
still
alerts
you
to
any
errors.
So
it's
not
like
you
just
get
like
a
black
box.
Something
went
wrong.
We
can't
expect
your
PR,
like
you
still
get
information
about
things
like
that.
But
if
you
wanted
more
detailed
reports,
you
kind
of
have
to
rerun
those
those
tests
closely,
which
is.
C
C
Okay,
so
for
my
update
as
this
PR
or
adding
an
explainer
to
the
venue
upward
specification
file,
it's
still
under
review,
but
we're
hoping
to
get
it
merged
pretty
soon.
What
it
is
is
basically
that's
a
bunch
of
comments
to
the
specification.
Posix
try
to
explain
what
each
piece
does
so
yeah.
If
you
have
it
kind
of
helps
to
demystify
what
this
file
is,
and
you
know
what
it's
telling
the
upwards
server
to
do.
C
G
G
I
think
one
thing
that
we
should
add
to
this,
which
this
wasn't
part
of
your
of
your
story
but
I,
think
we
need
to
reorder
the
declarations,
because
I
think
that's
part
of
what
confuses
people
upward
and
lazily
evaluated.
So
that's
something
we
we
need
to
change,
but
we're
still
going
to
merge
this
anyway
and
do
this
as
as
an
additional
request.
Yeah.
G
A
A
So,
as
we've
kind
of
we
talked
about
a
few
months
ago,
the
team
was
trans.
The
chain
has
recently
transformed
or
recently
transitioned
into
a
Kanban
workflow.
Because
of
that
you
know
we
spend
a
lot
of
time
on
the
last
few
months,
really
cleaning
up
our
board
looking
at
our
processes
and
I.
Think
due
to
that,
we
have
not
been
as
clear
I
think
with
community
members
on
where
we
would
like
contribution
or
where
they
prioritize
their
effort.
A
If
you,
if
you
looking
to
contribute
so
over
the
last
few
weeks,
we
didn't
try
to
move
back
to
that
and
be
more
clear
around
the
tickets
that
we
actually
need
help
on
and
if
you're
a
community
member
has
been
involved
in
project
for
the
last
year.
You
know
that
we
were
actively
using
Help
Wanted
tags
to
try
to
label
those
tickets
and
so
we're
trying
to
reincorporate
that
back
into
our
process.
A
Now,
if
you
look
at
our
board
or
if
you
look
at
the
issues
list
in
the
PWA
studio
project,
right
you'll
see
now
that
they're
our
Help
Wanted
tickets,
where
we're
actively
soliciting
for
community
contribution.
Of
course,
you
can
contribute
things
outside
of
those
parameters
right,
but
if
you're
looking
to
help
off
the
team
and
you're
looking
for
a
ticket
clerk,
we
need
we
need
that
help
right,
feel
free
to
come.
Take
a
look
at
the
board,
look
at
the
issues
list
and
look
for
that,
help
on
it
tag
right
now.
A
A
G
If
you
know
enough
people
like
it
here,
we
go
guys
see
this
screen.
K
B
G
Npm
install'
is
now
running.
This
command
also
works
with
yarn
and,
as
you
might
be
able
to
see,
it's
actually
just
a
nice
interactive
interface
on
top
of
a
command
line
interface
that
we've
created
for
build
pack.
So
all
that
this
does
is
assemble
that
command,
which
you
could
then
run
for
your
own
automation
purposes.
Making
this
as
an
extensible
feature
as
we
could.
J
G
G
It
defines
its
own
drivers,
but
currently
it's
just
a
stub
that
imports
them
from
venya
to
feinstone
store
so
that
you
have
a
file
to
put
your
stuff
in,
but
all
that
stuff
is
from
venía,
at
least
at
the
beginning
same
with
the
index
CSS
file,
here's
where
you
could
begin
customizing
your
project,
that's
based
on
venía
here's!
The
web
pack
configuration
it's
gotten
a
lot
simpler,
based
in
the
build
pack
configuration
and,
of
course
you
can
modify
it.
If
you
need
to
here's
how
this
project
works
right
out
of
the
box.
I
That's
very
cool:
that's
there's
a
huge
step
for
exactly
what
went
in.