►
From YouTube: Video Demo of License Compliance watcher implementation
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
I'm
going
to
elaborate
on
why
I
went
with
the
watch,
our
approach,
so
I,
guess
by
first
describing
the
problem
that
we
have
so
we
have
these
two
tabs
detected
and
project
is
essentially
the
list
of
detected
licenses
in
a
project
resulting
from
a
license
scan.
This
is
one
endpoint
policies.
Tab
is
a
separate
endpoint
for
the
management
of
the
license
policies.
A
Now,
if
there
is
a
license
policy
for
a
particular
license
that
are
set
to
denied
and
its
detected
in
the
project,
we
want
to
have
this
policy
violation
label
show
up
as
well
as
this
morning
banner
now
the
challenges
as
a
users
modifying
this
if
they
go
and
toggle
this
right
and
mighty
license
to
allow
updating
the
state.
So
now
we
have
that
banner
disappear
and
we
see
that
that
label
is
gone
now,
see
two
separate
endpoints
and
the
store
and
the
actions
and
mutations
that
run.
A
This
part
of
the
application
are
a
separate
view:
X
module
the
license
management
of
us
module
now.
I
know
there
are
ways
to
access
from
the
view,
arts,
module
route
getters
in
route
state,
but
I
didn't
know
how
we
could
use
that
in
this
context,
because
the
license
management
module
has
no
awareness
of
what's
available
for
this
license
compliance
application
at
a
higher
level.
A
So
that's
why
I
had
opted
for
this
watcher,
which
essentially
is
registered
at
the
creation
of
the
route
application
and
destroyed
when
I
guess
the
component
is
destroyed,
so
there's
cleanup
and
teardown
if
it's
to
avoid
memory
leaks,
but
essentially
all
we're
doing
is
watching
on
the
license.
Management
is
saving
State.