►
From YouTube: 2022-11-29: Release group pair programming
Description
Andrew Fontaine and Andrei Zubov from the Release team will do some front-end pair programming!
A
Okay,
this
is
the
release
team
front
end
paired
programming
streaming,
take
two.
So,
as
mentioned
last
time,
we
were
looking
at
doing
some
declarative
form
stuff
on
our
deploy.
Token
page
and
we've
managed
to
wrap
the
Scopes
into
a
nice
little
declarative
object
that
decides
kind
of
how
to
display
the
tokens
and
the
Scopes
added
to
how
to
display
like
what
Scopes
are
end
up
in
in
our
final
object,
but
it
might
be
fun
to
maybe
expand
on
this
for
the
rest
of
the
form.
A
A
A
B
Before
we
Venture
a
bit
further
into
this
path,
let's
also
just
Ponder
around
other
options
that
we
have
right.
So
currently
we
have
this
scopes
array
right
that
is
solely
responsible
for
scopes
right.
So
maybe
we
just
add
some
other
array
that
would
indicate
labels
that
we're
dealing
with,
for
example,.
C
A
A
C
A
A
A
C
A
A
C
A
A
C
A
A
A
A
A
A
C
A
B
A
B
A
C
A
A
C
A
A
Gl
Sprint
app
only
looked
for
things
like
that
were
camel
case
all
right
again,
but
if
you're
coming
from
Ruby,
they
obviously
prefer
snake
case
for
a
lot
of
stuff.
So
we
have
a
lot
of
like
historic
translations
that
have
these
snake
case
playful
placeholders,
instead
of
instead
of
camelcased
ones.
But
if
you
go
and
change
the
translation
or
the
the
placeholder
casing,
it
kind
of
avoids
the
the
translation
automatically.
So
somebody
has
to
go
back
and
and
check
it
and
make
sure
like
it.
A
A
A
Because-
and
this
makes
it
even
easier-
because
the
string
in
the
browser
here
has
the
this
gitlab
deploy
token
and
saying
kind
of
embedded
into
the
string,
we
can
use
geosprintf
in
our
V4
section.
So
what
we'll
do
is
go
back
to
the
editor
finder
V4
and
we
can
do
down
here.
We'll
do
template
description.
A
C
A
B
A
A
A
One
day
we'll
have
to
go,
maybe
we
can
do
like
an
exploration
of
how
the
beaker
Flags
front
end
code
kind
of
works,
because
that's
a
little
bit
fun
like
this
as
well.
There's
a
lot
of
due
to
the
like
nature
of
how
the
strategies
are
all
different.
They
gotta
be.
They
have
to
be
like
brought
in
in
various
ways.
A
C
C
A
A
A
A
A
A
C
A
A
B
A
C
A
A
A
A
B
A
A
B
A
C
A
A
B
B
A
C
B
B
C
A
A
A
A
A
A
A
C
A
C
A
A
A
A
B
I
don't
know
it,
it
looks
pretty
daunting
to
be
honest,
for
example,
just
imagine
the
person
that
just
lands
on
this
component
yeah
and
then
just
some
I,
don't
know
interaction
and
data
structures
just
to
render
three
more
fields,
I'm,
not
sure
if
it.
Basically,
if
the
use
case
is
complicated
enough
to
justify
this
part,
yeah.
B
B
A
Yeah,
that
is
true,
that's
true,
I
think
we
can.
We
can
supply
I,
think
there's
a
way
to
supply
slots
is
like,
but
then
we
get
into
like
we're
getting
away
from
kind
of
templated
components,
but
you
can
you
can
you
can
set
them
as
like
render
functions
and
stuff
yeah,
but
yeah
I
think
you
might
be
right,
and
this
might
be
just
a
little
bit.
It
got
a
little
unwieldy,
but
it
was
definitely
a
fun
exploration.
A
It's
strategy
parameters
yeah,
so
we
set
a
strategy
type
and
then
we
map
that
to
a
component
that
deals
with
the
parameters
for
that
strategy
type
right.
So,
if
you're
doing,
if
you're
doing
a
flexible
roll
out,
it
pulls
in
the
like
or
for
any
pretty
easy
one.
If
you're
doing
a
percent
based
rollout,
it
just
pulls
in
like
an
input
box
for
the
percent
and
then
all
of
that
still
funnels
up
very
nicely
into
the
into
the
thing.
A
But
that's
definitely
a
little
more
complicated
because
you
have
like
each
of
these
different
types
as
a
different
parameter
type.
And
then,
if
you
have
stuff
like
the
gitlab
user
list
is
kind
of
complicated
because
it
has
to
it's
complicated
because
it
has
to
go
out
to
the
API
and
fetch,
like
all
of
your
user
lists,
that
you
need
to
that.
You
need
to
be
able
to
like
get
and
do
autocomplete
searching
on
so.