►
From YouTube: feature proposal
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
Hi
everyone
so
I
was
actually
I
was
going
to
write
this
in
slack,
but
then
I
realize
it
takes
too
long
to
verbalize
it
and
then
maybe
it's
not
effective
as
it's
not
as
effective
as
recording
a
video.
So
that's
why
I'm
I'm
here
while
working
on
sorry
while
working
on
this
issue,
so
it
is
to
improve
the
message
when
filtering
and
security
dashboard
lists,
no
vulnerabilities
results
so
right
now
the
current
state
it
always
if
the
user
selects
some
some
filters.
A
We
always
displace
this
image,
but
the
proposal
is
that
when
the
filters
are
selected,
we
display
this
error
message
and
then,
when
the
dashboard
is
not
configured,
we
display
this
one.
So
I
was
while
I
was
working
on
this
I
created
the
variable.
The
image
variable
did
the
path
is
generated
in
the
back
end,
then
it's
injected
into
the
front
end,
while
I
was
doing
that.
I
realized
that
we
were
passing
it
down
in
the
front
end
when
we
received
from
from
from
from
the
back
end,
we
injected
two
several
components.
A
A
Actually
here
there
should
be
another
layer.
Each
of
them
have
a
different
layer,
something
like
this,
which
loads
the
vulnerabilities,
so
they
make
their
that
so
they
have
the
query
specific
query:
they
load
the
vulnerabilities
and
then
this
is
the
presentational
component,
the
vulnerable
to
this
component,
which
displays
the
the
vulnerable
to
this.
So
in
order
to
pass
down
property
from
this
one
to
this
one,
we
have
to
inject
it
to
every.
A
So,
instead
I
I
thought
of
using
the
the
provide
and
inject
API
that
is
built-in,
with
with
view
which
basically
defines
the
the
properties
here,
it
would
provide
and
then
it
with
within
the
vulnerability
list,
we
can
say
inject
and
it
reads
directly
the
properties
that
are
defined
here.
This
is
this
is
very
helpful
in
my
opinion,
because
we
don't
have
to
go
through
all
these
levels
and
then
pollute
the
the
components
with
extra
injections
and
we
can
directly
reach
the
the
context
here.
The
only
downside
is
may
be
that
it's
not
explicit.
A
So
if
person,
if
the
developer
reads
the
file,
it
may
not
be
obvious
where
the
provide
comes
from,
but
I
think
if
we
consistently
use
the
same
pattern
then
provide
the
properties
here,
a
top
level.
I
think
it
should
be
easy
to
follow
so
yeah
I've
recorded
this
video
to
discuss
this
feature
because
I
don't
want
to
just
you
know,
introduce
a
new
pattern
of
working
and
then
say:
hey
guys.
This
is
what
I
did
so
yeah
I'm.
Looking
for
your
feedback,
I
will
post
this
video
to
slack
and
I.