►
Description
In this session we pair up on finishing up gl-form-fields.
00:00 - Intro
03:15 - Discussing purpose of gl-form-fields
05:50 - Discussing what to do with shared validators and mappers
13:50 - Commenting about appropriate usage
25:15 - Writing a validator factory and tests
46:11 - Discuss persisting extension configuration in VSCode Web IDE
A
A
Where
is
jail
form
Fields
here
it
is
all
right.
Andrew
was
awesome
last
time
and
really
pushed
this
pretty
far.
Apparently
I
have
pending
comments
on
this
all
right.
We
gotta
just
wrap
this
up.
So
let
me
check
out
this
branch
and
let
me
look
at
the
diff
and
see
where
we're
at
so.
Let
me
get
all
set
up.
B
A
A
A
A
A
B
A
A
A
A
A
A
C
D
Yeah
I
think
there's
there's
two
things.
First,
there's
the
the
lint
rule
that
you're
going
to
create
to
basically
prevent
anyone
using
the
form
tag
or
the
input
tag
in
any
any
view
component
and
and
the
the
warning
that
it
gives
you
is
to
use
GL
form
filter
instead
and
then
it's
yeah
finding
a
way
to
to
encourage
oh
I've
done
this
and
I
think
other
people
are
going
to
want
to
do
this.
So,
let's,
let's
try
and
move
it
into
GitHub,
UI
and
I.
Don't
know
the
the
sort
of
I.
D
D
What
were
you
thinking
to?
Let
you
move,
you
know
to
not
block
you
essentially
but
education's,
a
big
one
right.
We
need
to
make
sure
people
know
about
this
and
find
a
way
to
not
just
tell
everyone
now,
but
somehow
you
know
ensure
that
there's
there's
more
of
a
regular
kind
of
oh,
don't
forget
about
this
or.
B
C
I
think
this
is
where
this
is
where
I
start
to
disagree,
though,
because
I
think
putting
putting
having
a
collection
of
validators
and
mappers
in
gitlab
UI,
because
I
think
that
the
responsibility
of
gitlab
UI
is
to
be
a
UI
component.
Library
and
data
validation
is
not
necessarily
the
name
of
the
game
here.
A
C
D
D
D
D
A
A
A
A
C
A
A
C
A
A
A
A
A
A
C
A
A
A
B
D
D
I
think
we
realized
that,
if
we're
building
the
form
then
there's
no
way
of
of
us
validate,
you
know
the
the
user
using
gel
form
fields
to
generate
the
form
needs
a
way
to
validate
the
form
if,
if
we're
automatically
building
the
form
for
them,
so
we
couldn't
really
do
one
without
the
other.
Is
that
fair
to
say.
C
D
Or
we
did
try
it
right
and
expect,
but
just
exposing
the
model,
but
then
you
had
to
was:
was
it
that
every
time
the
model
changed
any
field
you
had
to
revalidate
every
field,
whereas
asking
the
validators
in
allowed
you
to
to
specifically
list
on
on
each
field.
I
think
that
was
why
you
went
down
that
road
I.
B
As
it
has
been
to
validated
and
to
so
I
think
well,
I
used
to
use
a
a
library
called
for
react,
use,
form
and,
and
it's
a
is
a
validator
only
and
I
kind
of
like
it.
The
way
that
is
the
couple
one
from
the
other,
because
sometimes
you
need
to
build
a
very
fine-tuned
kind
of
UI
that
these
phone
Builder
may
not
be
able
to.
A
Yeah,
that's
one
of
the
risks,
I
think
with
the
scope
of
what's
Happening
Here
and
may
not
fit
certain
use.
Cases
which
isn't
great
and
yeah
we
do
want
to
be
able
to
validation
is
a
thing.
We
that's
I,
think
the
key
use
case
that
we
don't
see
happening
consistently
and
takes
like
a
50
line,
form
view
component,
and
it's
now
like
a
200
line.
View
component
and
and
the
main
application
validation,
though,
is
a.
What
were
you
gonna,
say.
B
A
So
we
can
so
like
the
fields
is
all
Fields
is
all
reactive,
so
you
could
based
on
and
that's
a
really
that's
a
really
interesting
question,
but
out
of
the
box,
you
totally
could
do
that
because
my
Fields
could
be
a
computed
based
on
whatever
my
values
are
and
if
something's
checked
is
like
oh
yeah,
here
we
go
is
a
field.
That's
goes
into
this
object,
and
so
it's
interesting
and
it's
doable
I
haven't
seen
how
that
plays
out
so
to
some
extent
we're
this
solves.
A
I'm
not
sure
where
we're
at
there
but
I
think
it's
something
we're
wanting
to
try
out
because
it's
better
than
where
a
lot
of
our
forums
are
currently
at
where
either
we've
implemented,
validation
incorrectly
or
if
you
completely
ignored
it,
because
it's
so
beefy
and
this
is
trying
to
simplify
a
lot
of
those
use
cases.
But
it's
possible.
It
doesn't
handle
the
other
cases,
but
the
fields
is
dynamic.
So
we
can
react
to
State
and
add
and
remove
and
change
fields.
D
So,
just
just
casting
back
as
well,
whilst
I
appreciate
and
agree
that
creating
the
films
isn't
really
a
problem,
it
just
felt
very,
very
wet
is
wet,
acceptable
or
not
dry.
You
know
everywhere.
I
looked
in
a
code
base,
we
had.
Oh,
you
basically
copy
and
paste
right.
You
copy
and
paste
this,
this
five
lines
of
code,
that's
kind
of
like
give
form-filled
Set
input
and
then
for
everyone.
You
change
the
the
description.
You
change,
the
the
V
model
binding
you
change.
It
was
just
a
really
repetitive
pattern.
D
A
Well,
yeah
and
like
like
there's
many
forms
we
create
where
we
don't
do.
This
whole
form
group
thing
where
we
don't
have
labels
that
map
to
each
other
like,
and
this
is
wanting
to
make
all
of
the
form
creation
standard,
because
there's
even
places
where
we
deviate
from
there,
because,
but
you
see
here
that
even
creating
these
form
inputs
require
it's
all
coupled
to
validation.
That's
the
interesting
thing
is
validation
is
a
cross-cutting
concern
with
the
inputs
and
submissions
of
forms,
and
so
even
from
submitting
this
thing
is
yeah.
B
A
A
C
B
A
C
C
A
C
A
A
A
B
A
A
A
A
C
B
C
B
A
B
C
A
C
C
B
A
A
A
D
A
C
C
D
A
D
A
C
D
A
C
A
B
A
C
A
A
I
know,
but
not
even
that,
but
also
just
like
even
from
the
front
end
of
like
we're
so
used
to
you
know
view
is
a
great
framework,
and
so
we
we
write
view
code
all
the
time
and,
like
view
tells
you,
when
something's
not
correct,
but
I,
don't
think
we
realize
how
much
we
repeat
ourselves,
which
is
like.
Yes,
you
don't
want
to
over
abstract,
but
we
repeat
ourselves
at
scale
at
this
point
like
we
have
every
spot.
You
know
what
I'm
saying
and.
A
B
A
A
A
A
C
B
A
C
A
C
A
Not
a
compliment,
maybe
it's
like
a
you're
gonna,
create
a
board
just
for
you,
because
you
gotta
organize
your
stuff.
I
created
this
board
I'm
just
joking.
Now
we
want
to
enable
the
extension
Marketplace
in
the
vs
code,
web
ID,
vs
code
extensions
are
and
vs
code
configuration
all
of
that
is
stored
in
indexeddb.
A
However,
we
do
this
aggressive
signing
out
whenever
you
sign
out
of
gitlab,
we
do
we
clear
out
all
client
side,
data
and
I
was
very
confused
at
like
how
in
the
world
is
it
doing
this,
but
we
passed
this
header
to
clear
site
data
to
clear
star
everything,
including
session
storage
and
cookies,
and
everything.
The
reason
behind
this
is
this
was
our
very
large
Band-Aid
fix
to.
A
Local
storage
containing
potentially
some
some
sensitive
things,
so
it's
not
like
okay
I
can't
totally
touch
this
because
that's
going
to
introduce
other
issues
but
using
vs
code
extensions,
which
is
really
nice,
isn't
like
this.
Is
it's
a
bit
of
work
to
set
up
your
extensions
and
it's
equivalent
to
data
loss
if
I've
set
these
up
and
configured
them
and
then,
when
I
sign
out
they're
gone,
you
know
what
I'm
saying.
A
A
The
other
idea
is
just
building
our
own,
like
sinker,
for
a
specific
index,
DB
fields
that
we
need,
because
we
that's
also
that's
an
unsolved
problem
for
other
issues
across
the
application
as
well.
So
like
we
have
the
frequently
visited
projects
and
stuff
like
that
that
depend
on
a
level
of
local
storage,
like
our
like
the
banner
and
other
things.
All
this
a
lot
of.
A
A
C
A
C
A
Right
that
should
be
fine,
and
hopefully
we
can
be
a
little
picky
picky
too,
about
what's
synced
and,
what's
not
so
like,
but
also,
hopefully
too,
is
like
I
I.
One
thing
I
need
to
do
to
investigate
thanks
for
asking
about
it,
because
any
talking
out
helps
I
need
to
investigate
how,
in
the
background
this
setting
Sinker
works.
A
C
B
A
A
C
A
D
A
C
This
isn't
gonna
be
we
could
we
could
do
like
a.
We
could
do
something
like
this
is
probably
like
too
technical,
but
we
could
do
something
fun
where
we
like.
You
can
make
a
user
project
that
has
a
bunch
of
settings
and
a
project
and
then
like
merge
them
yeah
somehow,
and
then
we
don't
have
to.
We
don't
have
to
worry
about,
but
then
you
have
to,
but
then
users
have
to
like.
A
C
B
B
A
A
Like
yeah,
let's
make
sure
we
clean
those
up,
so
that's
why
a
lot
of
me
was
leaning
originally
towards
doing
something
custom
because
it
was
like
I.
I
only
want
to
save
this
bit.
I,
don't
really
care
about
saving
all
the
data
that
vs
code
tracks,
but
I
think
that
I
gotta
look
up
what
the
settings
sync
does
and
I
think
it
I
think
it's
a
viable
option:
I
just
gotta,
investigate
it,
but
then,
if
it,
if
this
doesn't
work
out,
I
am
probably
going
to
look
into
okay.
A
What's
an
iterative
step
towards
that
works
for
our
immediate
web
ID
use
case,
but
that
also
could
be
used
because
already
so
throughout
gitlab,
no
local
storage,
Things
Are
permanent,
which
is
kind
of
lame
and
I,
see
this
I
I
run
into
this
first
minor
frustration,
a
lot
of
like
wait.
Why
is
this
not
ordered
by
updated
at
I?
Always
have
it
ordered
by
that
and
like
yeah
yeah
yeah
I.