►
From YouTube: Backdrop Weekly - Oct 28th 2021
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
Oh,
are
we
live?
We're
live
welcome
to
the
weekly
dev
meeting
today
is
at
least
where
I
am.
It
is
october
28th
and
we're
just
coming
off
a
backdrop
live
and,
let's
start
out
with
our
usual.
Oh,
we
are
streaming
this
meeting.
So
if
you
dare
to
join
us
now,
keep
that
in
mind.
You
can
mute
and
block
yourself.
B
C
Hi
greg
coming
to
you
from
greece
just
excited
about
anything
related
to
bachelor,
but
be
here
to
help
any
way
I
can
and
I'll
pass
it
on
to
jen.
D
Hi
I'm
john
lampton
joining
from
oakland
california.
I
build
websites
with
backtrack
and
I'm
looking
forward
to
seeing
what
new
features
we
come
up
with.
Let's
see,
justin
hey
around.
D
So,
let's
see
before
we
get
into
today's
agenda
arena
was
here
in
the
last
meeting.
I
was
hoping
she
might
stick
around
long
enough
for
us
to
thank
her
for
contributing
layouts.
I
know
for
the
project
that
she
was
working
on.
She
needed
a
set
of
backdrop
layouts
that
had
like
the
collapsible
sidebars,
where
the
content
region
expanded
to
fill
the
space,
and
so
she
created
the
layouts
that
she
needed
for
her
site
is
working
on
contributing
them
back,
which
is
great.
D
In
the
few
weeks,
we've
had
one
new
release
of
a
contributed
project
and
it
was
pirate
filter
which
was
a
live
report
that
almost
got
done
during
spectrum
live,
but
we
wrapped
it
up
and
it's
got
a
release
out.
So
if
anyone
who
wants
their
website
to
be
translated
into
pirate
speak
that
is
now
available,
we
don't
have
any
issues
in
the
forum
this
week
because
last
week
was
backed
up
live,
so
we
didn't
create
a
forum
post
asking
if
anyone
had
anything
they
wanted
to
share.
D
D
I
don't
know
if
anyone
has
any
bug
fixes
they're
working
on,
but
for
the
last
three
weeks
now
I
think
we've
been
reviewing
a
list
of
features
that
had
been
voted
on
at
various
points
in
time.
D
I
think
maybe
there
was
one
official
poll
that
was
open
and
then
I
don't
know
if
it
stayed
open
over
time,
but
we
have
a
number
of
people
who
voted
for
specific
features,
and
we
recently
revisited
those
to
analyze
how
big
a
task
it
would
be
in
order
to
accomplish
and
how
much
impact
it
would
have
on
backdrop
if
that
feature
went
into
core,
and
so
now
that
we've
evaluated
all
of
that,
oh
there's
an
individual
issues.
D
So
I
don't
know
tim
you,
you
had
some
that
you
thought
you
wanted
to
talk
about.
I
don't
know
if
it's
worth
going
through
the
whole
list
or
if
we
should
just
focus
on
the
ones
that
we
think
would
be
right.
A
It's
just
a
chance
to
sort
of
see
if
we're
coalition
coalescing
around
any
particular
issues,
certainly
if
anybody
is
already
advocating
for
one,
I
think
they
should
mention
it,
and
maybe
we
should
just
remind
folks
that
one
of
the
ways
you
can
help
get
an
issue
into
core
is
by
advocating
for
it
in
these
meetings,
which
basically
means
just
helping
help,
keep
it
on
track.
You
don't
have
to
write
the
pr
to
solve
it.
A
You
just
need
to
help
keep
it
on
the
agenda,
maybe
update
the
issue
to
identify
what
the
next
steps
are
and
just
help
it
move
forward
in
that
way,
that
can
be
a
very
effective
tool
to
getting
an
issue
into
court
and
here's
a
great
if
you're
looking
for
something
to
advocate,
for
this
is
a
great
list
to
start
with.
D
So
I
have
taken
the
list
of
issues
that
we've
been
talking
about
over
the
last
few
months
and
or
a
few
weeks
and
dropped
it
into
a
spreadsheet.
So
we
can
like
sort
on
those
columns.
So
if
we
wanted
to
see
lowest
impact,
highest
impact
or
lowest
effort,
or
something
like
that,
it's
in
there,
so
I've
dropped
that
link
into
today's
agenda.
If
any
wants
to
see
that
and
I'll
drop
this
spreadsheet
into
the
backdrop-
agendas
folder
for
future
reference,
nice
tim-
do
you
want
to
go
first.
A
A
That
would
be
a
really
big
pr
one,
but
it's,
I
think
it
sounds
to
me
like
it's
sort
of
borderline,
whether
or
not
we
we
could
get
that
in
well,
I'm
guessing
for
sure
we
could
get
it
in
the
next
release,
but
that
it
would
be
a
large
lift
and
whether
or
not
that's
realistic
and
and
what
I'd
like
joseph
to
think
about
is
what
we
can
do
as
a
community
to
sort
of
help
make
that
possible.
If
it
is
like,
would
it
help
to
have
a
sprint
on
that
particular
topic?
A
Or
I
don't
know
you
know?
Is
there
some
way
we
can
help
push
that
across
that
or
just
one
of
the
things
I
think
you
said
recently
was
that
one
thing
that
would
help
is
just
people
using
it.
You
know
and
sort
of
hacking
on
it
and
reporting
problems,
and
maybe
we
could
just
really
hammer
on
that,
like
in
every
meetings.
A
You
know
just
what:
what
could
we
do
to
help
move
that
forward?
Anyways
I'm
liking
that
issue
I'm
also
liking.
This
note,
don't
let
me
turn
off
my
phone
now.
The
nodeless
pathless
nodes
is
another
one,
because
it's
fairly
low
work,
but
it's
high.
It's
high
impact
visibility-wise,
it's
just.
It
will
change
the
default
view
of
the
front
page
and
we
seem
to
have
a
lot
of
enthusiasm.
So
I
think
it's
super
realistic
that
I
mean
we
almost
could
have
got
that
into
the
last
release.
So
it's
super
easy.
A
It
should
be
totally
reasonable
if
we
can,
if
we
can
create
a
consensus
on
aspect,
you
know
things
like
what
to
call
things
and
what
to
prompt.
I
think
one
of
the
more
difficult
things
is
going
to
be
settling
on
what
the
content
should
look
like
on
the
front
page
anyways.
I
I
mean
if
we
got
those
two
things
in,
I
think
that
would
be
a
pretty
big
release.
Just
from
a
pr
point
of
view,
anybody
else.
D
I
second
the
hidden
path,
content
type
in
core.
There
was
something
that
resonated
with
me
a
little
bit
when
we,
I
think
it
was
when
steve
joined
that
issue.
He
said
that
he
didn't
understand
what
a
hidden
content
type
was
until
we
made
that
issue
and
that,
I
think,
is
not
surprising,
especially
for
people
coming
from
drupal.
I
think
getting
that
feature
in
will
be
really
great.
D
I'd
also
love
to
focus
on
some
of
the
user
experience
issues
around
cleaning
up
the
text
and
language
around
explaining
what
a
hidden
path
content
type
is,
especially
if
we're
going
to
start
promoting
it,
we
can
stop
calling
it
a
hidden
path,
content
type.
I
think
that
would
be
a
huge
step
in
the
right
direction,
so
yeah
that
I
think
I
think
also
minimal
amount
of
effort.
Maximum
impact
is
great
references
I
think
is
gonna
be
really
hard.
D
Joseph
is
not
as
can
worried
about
that
as
I
am,
and
I
think
joseph
people
offered
to
spend
some
time
on
it.
So
maybe
I'll,
let
you
talk
to
that.
If
you
think
that's
real.
B
Sure
yeah,
I
think
overall,
we're
actually
really
close,
but
so
I
think
we
could
get
a
like
a
minimum
viable
product
in
pretty
quickly.
The
thing
I
am
less
sure
about
is
the
some
of
the
compatibility
with
all
the
other
reference
modules.
B
I
think
the
big
one,
so
probably
the
big
ones,
are
the
upgrade
paths
and
to
allow
people
to
convert
from
other
reference
modules
and
then
also
the
let's
see
upgrade
path
tests
and
then
I
think,
having
more
field
formatters,
because
currently
we
only
have
one
well,
we
only
have
one
form
widget
and
I
think
we
only
have
one
or
two
field
formatters
and
so
having
those
work.
B
In
addition
to
having
what
was
it
back
references
some
of
the
reference
modules
support
back
references,
and
I
think
that
for
people
who
need
upgrading,
that
might
be
a
really
important
feature.
D
Yeah,
I
totally
agree
I
feel
like
for
the
sites
that
I
had
in
triple
seven
and
I'm
now
running
a
backdrop
with
references.
I
am
definitely
missing:
field,
four
matters
and
widget
options.
D
I
feel
like
I'm
delivering
sort
of
something
a
client
doesn't
want,
because
that's
what
I
have
or
I
have
to
invest
in
building
new
things
for
that,
and
I
think
that
for
people
who,
if
we
have
entity
reference
in
core
and
we
give
them
reference
and
reference,
doesn't
have
what
they
want-
they're
just
going
to
use
entity
reference
instead,
and
so
what's
the
point
of
having
reference
decor
they're
not
going
to
use
it
right.
So
I
would
love
to
spend
some
time
working
on
those
widgets
and
formatters
for
the
upgrade
path.
D
I've
started
on
a
submodule
called
reference
upgrade
ui,
or
something
like
that.
That
lists
all
of
the
current
field
types
that
people
have
that
are
reference
convertible,
so
like
taxonomy
terms,
user
references,
node
references
and
then
any
references
and
provides
a
button
to
run
the
update
hook
on
them.
I
think
that's
a
good
first
step.
I
think
one
thing
that
we
mentioned
about
will
be
really
great,
so
we
had
a
reverse
option,
which
is
in
the
what
was
it
cck
had
when
it
became
fields?
D
Way
we
could
get
a
sort
of
a
minimum
viable
product
in
without
the
upgrade
being
automatic
and
give
people
sort
of
more
options
for
what
they
want
to
do.
F
B
I
think,
oh
initially,
we
should
not
what
so
two
of
the
other
modules
that
provide
sort
of
referencing,
ish
behavior
would
be
taxonomy
and
then
the
file
entities,
and
I
think
we
should
not
worry
about
the
special
behavior
they
need
right
now.
We
should
just
kind
of
ignore
them
and
let
them
let
them
serve
their
special
purposes
and
then
work
on
integration
with
them
later.
D
I
think
that
makes
sense.
I
think
that
it
could
even
be
something
we
slot
for
backdrop,
two
where
it's
like,
when
you
move
to
two
they'll
be
converted
to
references,
but
for
now
you
can
have
a
reference
field
that
references
the
term
or
you
can
have
a
term
reference,
be
all
the
references
in
terms
and
that's
fine.
A
Well,
jose
if
you've
indicated
an
interest
and
willingness
to
work
on
this
project,
but
beyond
just
leaving
it
all
in
your
hands.
If
we
were
to
really
try
to
push
this,
what
what
can
we
other
people
do
I
mean?
Is
there?
Is
there
a
sub
task
that
we
could
break
out
and
say
I
feel
like
this
is
the
kind
of
thing
that
we
have
a
couple
of
people
in
our
community
that
if
you,
if
you
gave
a
really
specific
like
here,
we
need
x
done
to
get
references,
module
and
core.
A
B
Okay,
I
can't
think
of
anything
off
the
top
of
my
head,
but
if,
if
you
want
a
specific
feature
that
is
supported
by
some
reference
module
to
be
able
to
work
in
backdrop,
then
please
make
an
issue
about
it.
B
Another
just
another
issue
that
we
actually
don't
have
or
another
feature
we
don't
have
an
issue
for
at
the
moment
is
we've
added:
we've
added
support
for
sort
of
visibility,
conditions
based
on
author
or
content
type
or
like
references
that
are
hard
coded
and
we
could
add
those
as
well
like
visibility,
conditions
based
on
fields
on
reference
entities,
although
that's
might
not
be
a
minimum,
viable
product
feature.
A
Sort
of
do
a
demo
of
where
it's
at
you
know
to
look
at
it
in
one
of
these
meetings,
where
we
actually
sort
of
looked
at
it
and
talked
about
what
is
working
now
and
what
isn't,
and
so
that
people
who
aren't
haven't
tried.
It
could
have
a
better
sense
of
how
far
we
have
to
go.
Or
is
that
not
practical.
E
A
And
just
to
repeat
what
you
said
before,
I
think
is
that
the
the
you're
just
working
on
the
contrib
module
in
that
in
this
case
you
think
we
can
just
drop
that
into
core
there
is.
Is
there
no
like
glue
code
or
anything
that
needs
to
be
done?
I
mean,
can?
Is
it
literally
that
easy
to
just
drop
it
into
core?
It
is,
I
think,.
B
It's
reference
singular
and
it's
it's
stickied
at
the
top
of
the
github
contrib
project,.
A
D
I
know
that
the
core
issue
is
a
list
of
things,
changes
that
are
needed
to
core
in
order
to
support
reference
stuff,
and
I
think
most
of
the
blockers
have
been
taken,
care
of,
which
is
why
we
have
a
contrib
module,
but
there's
some
hacky
workarounds
and
they
can
trip
module.
That
would
be
cleaner
in
core.
So
it
might
be
worth
just
reviewing
those
and
seeing
what
we're
thinking
for.
B
Oh
there
is,
there
is
one
core
issue.
Actually
I
think
it's
adding
a
label
key
to
the
entity
info.
That
was
so
that
we
could
determine
what
field
on
the
entity
was
the
actual
label,
but
because
we've
switched
everything
to
using
classed
entities
and
our
default
entity
class
actually
requires
there
to
be
an
entity,
a
label
method,
and
we
can
just
use
that,
and
so
we
don't
have
to
change
the
entity
keys.
D
That's
great
was
there
also
something
about
making
sure
that
there
was
a
like
a
view
url,
because
I
feel
like
files
broke,
some
of
our
patterns.
B
C
Yep,
so
I
was
back
in
august.
I
was
kind
of
working
on
issue
1590,
which
is
basically
a
task,
not
a
feature,
but
it
was
theme
that
is
best
to
be
moved
to
a
minor
release
and
that's
the
consolidation
or
making
more
consistent,
the
more
or
less
things
we
are
using.
The
details
form
api
element
that
was
blocked
on
another
issue
that
got
fixed
and
it's
now
on
course.
So
I
could
in
theory,
start
working
on
that.
C
A
That's
your
favorite
to
work
on,
but
is
there
a
second
one
in
terms
of
encouraging
other
folks
to
work
out?
I
think.
C
Okay,
I
have
one
that
I
don't
know
it
seems
like
a
big
undertaking.
Again,
I
think
it
it's
one.
It
falls
in
the
category
of
what
joseph
said
that
maybe
someone
can
go
through
the
meta
issue
and
sort
of
like
weed
out
or
you
know,
clarify
the
technical
direction
or
what
needs
to
be
done,
and
that's
issue
779,
which
is
basically
the
field
ui
redesign.
C
We
already
have
some
some
child
issues
there.
We
just
need
to
know
which,
like
what
needs
to
get
done
first.
C
But
unless
we
get
it
started,
it's
not
gonna
ever
get
done
and
it
and
it's
one
that
will
have
a
high
impact,
as
mentioned
before.
The
only
thing
is
that
this
has
been
done
in
drupal.
We
just
to
get
it
right,
because
there's
certain
things
that
do
not
like
you
ux
wise,
do
not
work.
Ideally
in
drupal
we
should
get
it
right
and-
and
some
folks
had
very
like
really
great
ideas.
We
even
have
more
caps
on
how
it
should
work.
I
think
we
can
get
it
right.
C
C
So
it's
basically
converting
the
way
that
fields
are
being
added
now
is
sort
of
like
the
workflow
is
externalizing,
what
developers,
how
developers
would
go
about
it
and
we
want
to
make
it
more
user-friendly,
basically
getting
people
to
select
the
widget
first
and
then
the
data
type
that
they
will
be
storing
after.
C
Yeah,
it
could
be
high
effort
of
mid.
Yes,
as
a
starting
point.
We
should
clarify
what
what's
the
next
step
like.
Do
we
have
a
blocker?
B
C
I'm
not
sure
if
it
was
you,
but
it
was
mentioned
before
that
thing
about
the
mapping,
and
I
think
the
idea
was
there
that
we
should
figure
out
if
there's
a
way
to
allow
both
ways
like
either
selecting
either
either
doing
it
the
easy
way.
For
I
don't
know.
First
time,
drupal
slash
backdrop
users
to
do
it
by
selecting
the
widget
but
also
allow
the
current
way
of
you
know,
experienced
users
that
want
to
select
the
data
type
first.
B
D
But
people
are
creating
content,
don't
care
what
the
form
looks
like
they
only
care
what
the
content
looks
like
so
there's
like
are
we
building
websites
for
people
who
want
to
create
content?
Are
we
building
websites?
People
want
to
create
forms,
we're
building
like
yeah,
so
this
is
not
a.
This
is
not
a
simple
problem,
because
right.
E
D
If
we
build
websites
where
people
make
forms
which
are
doing
right
now,
we're
not
solving
the
usability
problem,
we're
just
solving
the
technical
problem
and
adding
an
option
to
choose
a
data
type
solves
more
of
a
technical
problem
for
more
of
a
technical
people,
but
we're
not
doesn't
make
the
usability
problem
any
better,
but
yeah.
I
think,
there's
a
this
is
a
really
complicated
problem,
because
field
fields
are
complicated,
and
so
I
don't
think
that
we
can
like
look
at.
C
Yeah,
basically,
the
the
goal
is
to
improve
the
workflow,
so
it
may
even
be
you
know
more
caps
of
the
workflow
in
problematic
areas,
sort
of
thing,
but
I
think
we
have
some
of
them
already
or
a
starting
point.
A
Point
of
order
jen,
can
I
can't
edit
the
spreadsheet.
Could
you
share
make
it
possible
for
me
to
edit
the
spreadsheet?
I
can
add
some
comments,
so
getting
some
advocates
for
these
issues
would
be
a
good
outcome.
A
Phil
joined
us
bill,
we're
just
talking
about
priorities
for
the
next
release
and
we
for
the
last
couple
of
weeks,
we've
been
going
through
a
list
of
previously
identified
possible
priorities
and
sort
of
rating
them
on
how
complicated
they
would
be
and
what
impact
they
would
have
and
right
now
we're
sort
of
trying
to
pick
a
couple
that
we
might
focus
on.
A
G
I
would
love
to
see
that
views
color,
icon
whatever
it
may
be,
at
least
just
the
back
end
code
change
to
where,
if
somebody
wants
to
change
colors
of
a
hidden
field
or
a
rewritten
field
in
views,
you
know
somebody
has
the
the
ability
to
do
that
easily
through
their
own
css,
and
then
we
can
figure
out
how
to
actually
style
it
for
the
general
general
masses.
Later,
that's
the
I
guess,
the
one
that
comes
to
mind
off
the
top
of
my
head
outside
of
that
now
I
don't
really
have
anything
in
particular.
D
D
A
D
G
There
should
be
two
two
issues,
one
for
the
hidden,
the
other
for
the
rewritten
one
is
for
the
hidden
5287
is
for
the
rewritten.
G
A
D
We
also
did
that
complete
rewrite
of
the
layout
listing
ui
too,
that
robert
was
advocating
for.
C
A
C
C
Then
sorry
I
missed,
which
thing
are
you?
Do
you
have
time?
Are
you
advocating
for
any
specific
issue
this
release
cycle?
I.
G
A
For
I'm
not
sure
where
we're
where
we're
going
next,
we
sort
of
had
this
discussion
to
be
finished.
With
the
discussion
about
well,
I
I'll
just
say
joseph.
I
would
encourage
you
to
think
you
know
again
along
the
lines
of
what
can
we
do
to
help
move
this
forward?
I
think
what
I'm
going
to
do
is
is
just
try
testing
the
module
like
in
a
plain
vanilla
site
and
seeing
if
I
can
get
a
better
sense
of
how
how
far
it
is
along.
A
D
B
One
thing
I
did
run
into
last
time:
we
discussed
this
issue.
We
brought
up.
I
well.
I
said
that
I
could
just
take
the
tests
from
the
other
reference
modules
and
convert
them
and
then
use
those
as
our
tests
to
begin
with,
but
I
ran
into
an
issue
where
most
of
the
other
reference
modules
don't
have
tests,
so
I
can't
do
that.
B
A
Well,
I
will,
I
think,
I'm
going
to
advocate
for
the
hidden
content
or
the
hidden
content
type
in
core,
just
because
I
wrote
the
pr
on
it
and
it's
something
I
can
actually
have
some
control
over,
and
I
will
try
to
just
sort
of
encourage
us
to
keep
pushing
this
reference
module
thing.
But
if
somebody
else
can
advocate
for
it,
that
would
be
great.
C
There's
a
few
things
that
were
mentioned
by
people
in
backdrop
live
that
were
not
big
features
but
pet
peeves
things
that
do
not
exactly
work
as
expected.
C
I
haven't
checked
the
queue
in
the
last
couple
of
days,
but
one
of
them
is
5246
and
diane
mentioned
that,
which
is
the
ability
to
clone
use,
displays
into
different
display
plugins,
and
between
the
last
time
the
detector
now
heard
filed
a
pull
request
and
I
think
lauren
nerds
something
in
there.
So
so
this
is
rtbc.
It's
ready
to
be
merged.
It's
not
a
feature
again.
It's
a
task.
C
G
C
If
you
see
it
as
a
crossbow,
it's
a
task,
but
if
you
see
it
as
a
new
feature
which
was
not
present
there
before,
then
it
needs
to
be
a
feature
and
it
will
need
to
go
in
121.0,
so
feel
free
to
change
that
yeah.
A
G
C
G
I
asked
the
question
greg.
Well,
actually
it
looks
like
uw
panda
just
commented
on
it.
C
Yeah
I
haven't
touched
that
in
a
year
and
a
half,
so
I
have
to
revisit
it
so
usually
when
I
raise
issues
like
that
is
either
I
come
across
an
issue
indeed.org
or
someone
mentions
it
and
I
add
it
as
a
to-do
list.
I'll
have
to
see
just
to
remember
what
triggered
this.
It
could
be
something
that
I
found
at
work
that
triggered
that.
Are
you
looking
at.
G
I
figured
I
I
want
to
bring
it
up
on
here
to
see,
if
maybe
folks,
who
have
a
little
bit
more
intimate
exposure
to
the
themes
and
how
that
api
was
created.
If
they've
got
any
thoughts
on
this.
C
D
E
A
G
Yeah
we
were
talking
about
all
the
the
sub
themes
that
can
literally
go
into
infinity
and
it
kind
of
hit
me
that
if
you've
got
a
sub
theme
of
the
sub
theme
it's
like-
and
I
have
a
user
that
I
only
want
them
to
edit-
that
particular
sub
theme.
I
don't
want
them
to
have
access
to
the
primary
theme
or
you
know
the
secondary
sub
theme.
Then
I
can
hide
those
from
the
ui
to
where
they
just
never
see
it.
G
So
I
didn't
think
it
existed.
I
think
it
was
bw
panda
that
actually
brought
it
up
that
he
goes
no
it's
in
the
api,
it's
there.
So
then
I
went
looked
at
the
documentation.
It's
like
there
is
no
documentation.
We
need
this
to
be
documented
because
it's
you
know.
Otherwise
nobody
even
knows
that
it's
a
thing
and
then
that's
when
it
led
me
into
what's
the
default
of
this
which
led
to
this
issue
so.
C
That
was
in
it's
a
document
that
I'm
familiar
with
because
it
mentions
the
conventions
for
the
name
that
it
should
be
capitalized
properly
and
that
and
so
on
and
so
forth
and
hidden
is
mentioned
there
I'll
try
to
find
it,
I'm
not
sure
if
we
ported
it
over
to
our
documentation
and
how
things
work.
So
I'm
sure
this
this
value
hidden
equals
is
valid
for
themes
and
I
think,
modules
as
well
yeah.
We
use
we
actually.
B
B
Layouts
profiles,
modules
themes
all
in
core
that
use
this,
that
we
use
in
tests
that
are
all
hidden.
C
G
A
I
just
found
something
on
docs.backdropcms.org
under
creating
modules,
there's
a
section
on
info
files
and
if
you
scroll
down
to
the
bottom
of
that
right
between
that
and
about
hooks,
it
talks
about
hidden
in
the
defaults
or
hidden
equals.
True.
E
A
G
C
Created
I've
put
a
link
in
the
chat
page
that
I
was
referring
to,
which
which
lists
all
the
properties
of
that
go
into
dot
info
files
and
for
d7,
because
the
the
respective
for
d8
and
beyond
this
called
writing.yaml
files.
So
there's
a
section
there
and
there's
a
bullet
point
for
hidden
which
explains.
C
G
Yeah,
I
I
feel
like
that.
Particular
one
probably
needs
to
specify
what
the
default
is.
Most
of
the
you
know,
looking
through
the
other
info
stuff,
it's
it's
kind
of
like
there
is
no
real
default,
but
that
one
it's
a
boolean.
Therefore,
it's
going
to
have
some
kind
of
a
default
I
feel
like.
We
need
to
specify
hey.
This
is
the
default
that
it's
missing
or
you
know
or
whatever
so.
C
D
Okay,
I
was
just
working
with
these
functions
on
the
recipes
ui
stuff,
so
I'll
see.
If
I
can.
D
Ahead
and
at
least
wrap
up
the
video.
Does
anyone
have
any
final
issues
they
want
to
share
or
things
they
want
to
talk
about.
B
B
Form
yeah
and
I
I
did
make
a
comment-
posting
a
potential
solution.
B
C
C
Yeah
thanks,
I
was
actually
trying
to
find
a
way
to
do
this
properly.
Yeah
cool.
My
my
problem
with
this
form
is
that
they
were
by
inspecting
form
and
form
state.
You
couldn't
tell
if
the
form
is
empty.
That's
that's
my
problem.
D
I
just
think
it
might
be.
It
might
be
better
to
switch
back
to
everything
working
now
and
then
in
a
follow-up.
We
should
figure
out
how
to
solve
the
issue
with
nothing
on
the
form,
and
we
might
even,
I
think,
there's
a
function
in
the
issue
where
we
checked
the
max
input.
Vars,
there's
some
way
that
you
can
count
like
the
number
of
element-
children
in
a
form.