►
From YouTube: GraphQL Vulnerabilities
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
Graph
QL
in
super
quick
fashion,
so
this
is
the
from
abilities
list
using
graph,
QL,
nice
and
simple
the
main
difference
between
the
graph
QL
one
and
the
rest.
One
is
this
bit
here
so,
instead
of
using
view
X
to
fetch
all
of
the
vulnerabilities
and
things,
this
is
where
we're
using
graph
QL.
So
we
don't
need
to
make
any.
A
Firing
actions
when
the
component
Lords
to
say
it
go
fetch
me
the
vulnerabilities
we
just
put
in
this
Apollo
block
here.
Let
me
say,
if
under
abilities,
I
want
this
one
Billy's
query,
which
is
just
this
bit
of
graph
QL
here
you
know
we
return
all
the
one
abilities
and
all
of
these
nodes
and
then
the
page
info
as
well
I'll
get
to
that
a
little
later
and
then
what
we're
doing.
A
A
So
on
the
first
Lord
we
go
and
fetch
the
first
10
vulnerabilities
and
then
ignore
this
kind
of
all
I'm
doing
is
saying:
Vanar
abilities
is
equal
to
the
nodes
on
project,
front
abilities,
nodes
and
then,
when
we
cower
first
result
set
initial
vulnerabilities,
lured
true,
so
that
we
know
when
a
release
of
loaded
and
then
set
page
in
for
in
a
similar
way
how
we
got
the
the
Dare
here.
So
this
is
just
the
Elvis
operator
to
say
response.
The
project
run
abilities
page
info.
A
Only
we
first
checked
the
page
import
to
see
if
there
is
a
next
page
and
then
we
said:
okay
get
this
vulnerabilities
query
and
just
fetch
some
more
vulnerabilities,
the
first
one.
We
want
to
fetch
sorry
for
her.
We
want
to
fetch
the
same
amount
as
last
time.
So
again
this
is
10
and
all
of
them
after
end
cursor,
which
is
the
sort
of
ID
for
the
last
phone
ability
we
fetched
previously.
A
A
This
is
basically
the
same,
the
only
difference
being
the
pagination,
because
pagination
doesn't
work
with
graph
QL
right
now,
so
I've
had
to
do
it.
This
way
it
was
using
an
observer.
So
basically,
every
time
this
appears
on
the
page,
the,
where
is
it
intersect,
gets
called
and
then
next
page
is
fired,
which
gets
us
more
vulnerabilities,
and
you
can
kind
of
see
that
here,
if
I
go
slow
enough
it
or
fast
enough.
Even
let
me
refresh
so
this
then
becomes
an
infinitely
scrolled
list,
because
pagination
is
totally
broken.