►
Description
This talk will cover what graphql is and why you should know it and how to get started using the apollo client in your application. It will talk about very basic concepts of graphql and if you are still awake we can touch on the advanced topics. We will be working through an application and slowly introduce concept commonly used in Graphql I will hopefully showcase how easy it is to get started and maybe it will be practical enough to get you started in integrating it in your applications today or tomorrow depending how practical it is for you when you read this description.
This talk was recorded at the Jozi.JS meetup group on 21 November 2019.
https://www.meetup.com/Jozi-JS/events/266202004/
Disclaimer: The opinions in this talk are those of the individual and do not necessarily represent those of this channel, the meetup group, or its sponsors.
A
Hi,
ladies
and
gentlemen,
so
thank
you
for
coming
and
joining
us
in
this
evening
and
waiting
for
all
our
technical
issues.
I
wanted
to
do
this
talk.
Craft
PL
is
pretty
old.
Now
I
could
spin
around
for
some
time,
but
I
recently
started
a
job
five
months
ago,
and
they
gave
me
a
list
of
technologies
of
things
that
I
needed
to
learn
and
graph.
Ql
was
one
of
them.
I
did
not
to
be
fair,
actually
like
to
look
at
the
technology
before
starting
the
job.
A
So
when
I
was
in
the
job,
there's
quite
a
lot
of
their
services
that
they
use
and
they
use
graph
QL,
so
fumbles
aren't
my
way
through,
but
decided
that
I
needed
to
take
some
time.
So
as
most
presenters
do,
if
you
want
to
learn
a
new
technology
prepare
to
talk
about
it.
So
that's
what
I'm
doing
my
name
is
Rudy,
and
this
is
what
I
do
so.
The
five
the
job
that
I
caught
five
months
ago
is
working.
A
There
genuinely
believe
that
generally
because
it's
like
false
but
like
they
believe
they
believe
in,
and
then
they
pour
their
hearts
into
the
work
that
they
do,
which
is
very
exciting
so
having
to
work,
for
that
is
pretty
pretty
pretty
cool
if
I'm
not
doing
that,
I'm
a
facilitator
assessment
or
losing
it's
an
organization
that
health
so
provides
young
people
with
digital
skills
so
that
they
can
do
some
digital
work
and
they
try
to
free
a
gap
between
unemployment's.
Well,
the
switch
the
gap
in
unemployment
in
South
Africa.
A
So
it's
pretty
awesome
if
I'm
not
doing
that.
I
run
an
organization
called
pink
eye
tea
with
amazing
humans
who
help
me
each
and
every
single
day
to
get
a
lot
of
women
into
software
development
and
I
understand
that
this
is
what
I
do
and
who
I
and
not
Who
I
am
so
therefore
interesting,
and
the
only
thing
that
I
discovered
upon
myself
just
this
weekend
is
that
I
love
cake
and
it's
like
just
like
every
other
person
who's
inside,
because
that
lights,
papa
and
Cody
writes
I.
A
Really
love
cake
is
in
like
traveling
at
a
petrol
station
with
the
Woolworth
kind
of
I
love
cake.
So
that
was
something
I
discovered
by
myself.
That
was
new
all
right,
so
what
is
got
cure
all
right,
sir
I
learned
the
technology
right.
Obviously,
you
want
to
find
definitions
about
what
it
is
and
what
people
consider
it
to
be
and
things
that
are
fun.
So
apologies.
My
presentations
are
not
as
structured
as
nica's.
One
and
I
have
been
doing
this
for
some
time
now
so
I'm.
A
Sorry,
first
thing
is
that
a
respondent
is
Facebook,
so
Facebook
has
quite
a
lot
of
systems.
I'm
sure
and
services
and
stuff
like
that,
and
so
they
decided
to
create
the
specification
called
graphic
Yasir.
My
specification
is
a
set
of
requirements
that
you
need
to
need
so
that
you
can
achieve
something
right
and
I
was
like.
Okay,
that's
cool,
but
it's
also
a
query
language,
so
I
mean
create
language,
I,
think
SQL,
and
things
like
that,
so
you
use
crew
is
to
achieve
these
sets
of
requirements.
A
A
It
talks
about
how
it
calls
an
API
from
the
accept
the
directions,
the
fields
and
subfields
of
that
API
to
find
out
information
and
like
resolve
the
fields
and
the
career
pot
is
the
query
language
or
the
QL
parts
of
the
query
language.
Alright,
so
that's
the
definition
of
a
graph
QL,
it's
and
I
hope
that
make
sense
all
right.
A
So
in
South
Africa
right,
we
have
been
working
with
soap
for
some
time,
so
anyone
who's
working,
the
bank
knows
that
soap
hasn't
died
yet,
and
we
have
yeah,
you
know
and
now
we're
moving
to
wrists
and
a
lot
of
our
services
use
wrists
and
be
pretty
excited
about
it,
but
we're
still
using
soap.
So
now,
we've
got
this
new
thing.
That's
coming
up
called
graph,
QR
and
I'm
like
how
are
we
trying
to?
A
Maybe
make
rests
obsolete,
I,
don't
think
so,
and
the
nicest
thing
about
materials
that
you
can
build
it
on
top
of
any
REST
API,
and
maybe
it
is
trying
to
replace
race
I,
don't
know,
but
with
the
show
of
hands
who
actually
has
worked
with
graph,
QL
and
and
okay.
So
you
guys
know
what
graph
QL
isn't
really
exciting
all
right
cool.
A
Now,
let's
take
an
example
right
we
have
a
post
in
Instagram,
I,
follow
Cosmopolitan
South,
Africa
and
they've
got
this
post
that
comes
from
this,
this
girl's
page
of
the
ebony,
no
ladies
or
woman's
page,
the
ebony
Falcon
right
and
that
comes
from
Twitter
and
then
at
the
bottom.
Here
we
can
see
some
likes.
Some
comments
be
very
familiar
with
Instagram.
All
right,
so
take
go
with
me
with
with
me
in
this
journey.
Right.
A
So
in
order
for
this
kind
of
picture
in
my
feet
to
show
up
on
Instagram,
multiple
things
need
to
be
contacted
the
service,
the
reddest
store.
What
is
this
some
third
API
and
other
services
that
they
might
have
to
make
it
possible?
This
is
really
daunting
for
some
of
our
applications.
Maybe
a
website
might
have
a
lot
of
like
network
and
bandwidth,
but
for
mobiles
data
is
not
cheap
rights
and
things
die
out.
A
So
the
idea
is
that
we
can
provide
one
endpoint
and
then
make
these
calls
and
request
and
then
bring
only
the
necessary
information
to
the
user,
and
this
is
what
graph
QL
tries
to
do
right.
So
a
rest
version
of
what
we
just
saw
to
make
that
Instagram
post
possible
right
is:
we've
got
on
our
desktop
and
our
mobile.
We
go
and
get
information
from
radius.
A
We
go
and
get
in
information
from
Postgres
and
some
other
API
and
like
API,
this
world
could
be
in
tints
like
it
could
be
other
services
on
top
of
other
services,
just
to
get
the
information
that
we
need
all
right.
This
is
a
graph
QL
version
of
it.
It
says
all
your
application,
so
your
desktop
and
your
mobile
will
only
have
one
endpoint
and
when
you
reach
that
and
in
that
endpoint
you
can
provide
a
certain
schema
of
the
data
that
you
want
every
single
time.
A
You
call
this
endpoint
all
right
graph,
QL
sits
somewhere
in
your
server
somewhere
and
then
does
all
these
calls
for
you
and
resolves
all
this
information
and
gives
it
back
to
you
when
you
request
it.
Does
that
make
sense
awesome
now
the
things
that
graph
QL
tries
to
achieve
or
tries
to
solve
is
the
concept
of
over
and
under
fetching
all
right.
A
So
with
our
risk
api's-
and
I
don't
know
how
many
of
you
guys
have
it-
has
this
experience
right-
you
have
a
REST
API
that
is
probably
developed
according
to
like
a
schema
that
is
in
the
back
back
in
somewhere,
and
it
just
gives
you
information
that
you
don't
necessarily
need
at
that
particular
time.
You
might
just
want
the
users
name,
but
not
necessarily
their
address,
or
things
like
that,
and
so
that's
all
the
fishing
part.
A
The
end
of
fetching
thing
is,
is
that
you
might
want
more
information,
but
this
wrist
API
only
provides
you
like
a
bit
of
the
information
that
you
require.
So
you
now
need
to
make
another
call
to
get
the
rest
of
the
information
and
things
like
that
so
because
in
graph
you'll,
you
can
like
structure
your
your
response.
So
what
you
want
from
this
endpoint,
you
can
tell
it
what
you
need
and
what
you
don't
need.
Alright,
it
tries
to
solve
the
n
plus
1
problem.
A
What
is
that
now
for
a
query
to
happen
like
that
post
that
we
just
did
right
the
comment
from
Instagram?
Let's
say
you
are
fetching
the
the
content
and
for
each
and
every
one
of
those
content,
these
comments,
and
in
those
comments,
these
names
of
users
all
right,
if
you
just
fetch
the
information
you
are
going
to
get
the
information
about
Cosmopolitan
as
a
user
in
Instagram
you're,
going
to
fetch
all
the
comments
that
is
required
for
the
like
that
are
part
of
this
post.
A
But
for
each
and
every
one
of
those
comments
you
need
to
go
to
a
fetch
to
get
the
information
about
the
user
who
posted
the
comment.
This
is
a
lot
of
trips
to
your
server
and
it's
pretty
much
expensive
and
you
don't
necessarily
want
to
do
that.
Facebook
camera
came
with
the
concept
of
data
loader,
and
this
is
basically
using
batching
and
caching
to
kind
of
help
you
in
making
your
request
so
batching.
A
It
goes
and
gets
all
the
information
that
you
need
for
your
services
right
and
tries
to
catch
this
information
for
you
so
the
next
time
you
want
to
make
a
similar
trip.
It
already
has
that
information
for
you
all
right.
It
has
charts
and
analytics
right,
and
why
do
you
need
to
have
this?
Is
that
sometimes
a
resolver,
for
example,
that
resolves
your
fills
in
in
the
query
language?
You
want
to
find
out
whether
some
things
are
taking
longer
shorter
and
try
to
help
or
like
mitigate
those
bottlenecks.
A
What
is
also
nice
is
that,
after
a
long
time,
if
ever
you'd
like
designed
something-
and
it's
no
longer
use,
it'll
tell
you
that
that
thing
is
not
used
anymore,
so
you
can
remove
it
without
having
any
issues
or
any
breakage
in
your
current
front-end
right
and
also
the
SDL
part,
which
is
the
schema
definition
language
right.
It
provides
you
a
contract
with
your
car
with
the
client
in
between
the
times
and
the
server.
A
So
all
the
front-end
developers
can
continue
with
their
work
without
having
to
worry
about
what's
happening
in
the
backend
and
when
the
backend
is
ready,
it's
just
plug
and
play.
So
that's
pretty
cool
all
right,
so
I
know
I
talk
a
lot
and
I'm
quite
tired.
So
if
you
guys
want
to
take
anything
out
of
this
talk,
it's
pretty
much
these
five
things
and
I'm
going
to
cover
graph
QL
from
a
very
high
level
right.
A
One
of
them
is
the
schema
all
right
that
we
talked
about,
which
is
the
concept
that
we're
going
to
walk
through
and
I'm,
going
to
explain
how
it
looks
like
a
resolver
right
number:
three,
it's
queries
mutations
and
subscriptions.
We
are
going
to
talk
about
each
and
every
one
of
them
in
detail
and
how
they
look
like,
but
just
look
at
this
and
I
can
memorize
it
capture
it
cat
the
schema
all
right.
I,
like
this
coat
as
I,
was
going
through.
A
Another
thing
that
I
forgot
to
mention
is
that
rest
is
not
a
bad
protocol
specification
right,
because
we
have
smart
developers
out
there,
and
a
lot
of
people
have
found
certain
ways
of
dealing
with
some
of
the
issues
that
I
mentioned,
which
is
overfitting
and
underfitting
right
Oh.
Like
other
issues
that
I
mentioned
like
we
have
OData.
If
you
really
really
want
to
use
a
query
language
that
you
can't
that
is
built
on
top
of
wrist,
we've
got
JSON
schema.
If
you
really
want
to
use
a
schema
for
your
REST
API.
A
So
it's
not
that
you
have
to
use
graph.
Ql
people
have
found
solutions
to
still
use
wrists
with
different
types
of
other
tools.
That's
it
on
top
of
wrist
right,
just
as
an
FYI
all
right
schema
tonight.
The
second
part
is
our
resolvers.
A
resolver
is
a
function
in
graph
QL
server
that
is
responsible
of
fetching
the
data
for
a
single
field.
This
is
very
important
right.
A
So
this
is
the
field
that
we
have
clothes
all
right,
and
this
is
our
resolver,
so
the
our
resolve
o
will
do
all
the
magic
that
it
needs
to
to
do.
Remember
graph
QL
needs
like
go
and
fetch
information
there
and
go
fetch
information
then
get
fresh
information
there
to
make
one
field
possible
right.
So
your
resolves
that,
basically
in
the
instructions
and
the
soldiers
that
you
send
in
to
go
and
get
that
information
for
you,
so
you
provide
your
functions.
Your
methods
and
everything
that
you
want
to
do
here
to
resolve.
A
Whatever
feel
that
is
being
queried.
Does
that
make
sense
all
right
queries
so
each
and
every
thing
that
you
have
to
do
that
you
use
like
that
it
has.
It
has
to
be
available
into
your
contract
or
your
schema,
so
this
is
a
definition
of
how
you
would
use.
You
will
define
a
query
inside
your
schema
type
query
and
whatever
the
query
is,
for
example,
here
we've
got,
quotes,
we're
gonna,
see
this
in
detail
and
quotes
actually
returns.
A
Array
of
quotes
and
code
is
just
an
object
that
bring
that
returns,
a
message
and
an
author
and
an
ID
all
right.
So
now
in
your
resolver,
you
go
to
that
query
and
say:
hey
cook.
This
is
the
cook
that
this
is
the
query
that
someone
is
going
to
use
and
they're
gonna
call
quotes
when
they
call
this
query
go
and
get
me
all
the
coats
and
coats
could
be
a
database
code
could
be
a
data
like
a
data,
store,
an
object
or
anything
that
you
want
it
to
be
alright.
A
And
how
do
you
use
this?
This
is
the
usage
yeah
yeah,
so
you
would
give
it
the
keyword,
which
is
query
and
what
you
want,
which
query
that
you
actually
want
to
query,
because
there
could
be
a
list
of
queries
and
then
in
there
you
provide
the
information
that
you
need.
So
the
fields
that
you
want
it
to
respond.
You
with
with
all
right
and
I'll,
give
you
an
example
as
well.
So
if
you
only
want
the
messages,
you
can
just
put
messages
and
it'll
return
messages
back.
A
If
you
want
messages
and
author,
then
you
can
provide
these
two
fields
and
it
will
give
those
fields
back
to
you
all
right.
The
third
thing
is
posting
mutations.
This
is
how
you
would
define
your
mutations
inside
your
schema,
so
type
mutation
and
whatever
the
mutation
is
yes
and
you
guessed
it
mutation,
it
changes
data.
So
if
you
want
to
add
anything
into
your
database
who
things
like
that,
you'll
use
this
you
can,
if
you
want
to
provide
some
fields.
You'll
provide
feels
like
this
and
give
it
type
it
uses.
A
A
The
last
thing
subscriptions
subscriptions
are
things
that
you
use
to
like
monitor.
If
any
event
has
happened,
and
when
that
event
happens,
you
want
to
know
about
it,
so
you
subscribe
to
it
against
there's
other
technologies
that
you
can
do
to
achieve
the
same
thing,
but
graph
QL
also
provides
this
for
you.
A
You
define
subscription
like
this,
the
type
which
is
subscription
and
as
and
we
know
that
it's
strictly
typed.
This
is
how
you
need
to
always
specify
your
schema
and
the
resolver.
This
is
how
subscription
resolver
would
look
like,
so
we've
got
subscription
and
pub/sub
is
a
published
subscription
factory
that
Apolo
provides
for
you
and
then
the
async
iterator
is
basically
a
function
that
asynchronously
listens
to
your
event.
You
events
whatever
event,
that
is
it.
That
is
that
it
is
alright,
so
yeah.
This
is
the
last
part
which
is
subscriptions
in
this
journey
of
figuring
out.
A
What
graph
QL
is
I
know
I
found
out
that
it
was
made
in
open-source
in
2015,
but
this
website
is
pretty
pretty
pretty
awesome.
The
reason
being
is
that
okay,
so
you'll
go
through
all
the
theory
before
you
get
to
this
part,
but
it
shows
you
what
kind
of
technologies
that
it
works
with
from
a
front-end
and
in
other
technologies
that
it
works
with
in
the
backend
and
there's
a
lot
of
information
like
in
gross
QL
and
node
alone.
There
is
like
graph
Jas
that
was
created
by
Facebook
Graph
yoga.
A
That
is
built
on
top
of
express
a
polo
which
is
the
one
that
we're
using,
and
the
reason
why
I
chose
a
polo
is
because
the
company
that
I
work
for
uses
it
so
I
needed
to
learn
these
technologies.
So
this
is
what
I'm
doing
and
yeah.
So
if
you
want
to
take
anything
out,
go
to
this
website,
pretty
awesome,
so
yeah,
let's
jump
into
our
demo,
I'm,
not
brave.
Like
me,
cuz
I'm,
not
gonna,
really
code
live
I'm,
not
gonna
test.
The
demo
gods
like
that.
A
That
better
Orson
okay,
so
myself
is
pretty
simple.
All
right,
you've
got
all
your
node
modules
are
in
store,
but
I'm
gonna
say:
first
pay
attention
to
our
package:
that's
Jason,
there's
pretty
much
two
dependencies
right.
Yes,
this
is
going
to
go
and
get
other
dependencies
and
you
know
module
which
I
can't
see
it.
But
this
is
are
the
two
things
that
are
important,
that
you
need
just
to
get
a
server
running
up
and
running
all
right.
A
A
polar
datasource
wrist
I
still
do
believe
that
I
can
do
this
with
requests
from
node.
Try
to
do
it
took
me
long
so
I
just
like
bailouts
and
then
a
polo
server
which
we're
gonna
go
and
talk
about
now.
Alright,
this
is
my
server
rights,
I
import,
all
the
clever
libraries
and
packages
that
I'm
gonna
use-
and
this
is
my
schema-
all
right
schema.
You
have
to
use
graph
QL,
which
comes
from
the
Apollo
server.
A
This
also
provided
a
lot
of
like
complexity
for
me
because
that
they
removed
graph
QL
from
a
polar
client,
and
now
you
needed
to
go
and
get
it
in
graph
text,
but
yeah
I'm,
just
like
alright.
So,
yes,
you
provide
graph
QL
and
provide
the
schema
inside
the
schema.
This
is
how
you
would
use
your
comments
instead
of
like
forward
slashes
or
like
forward
slash
and
star,
you
use
hash
tags,
and
this
is
my
first
time.
I've
got
a
time.
Cole
quotes
tonight
that
takes
in
oh,
that
has
an
ID
a
message
and
an
awesome.
A
My
I've
got
a
query.
The
career,
the
first
query,
is:
quotes
that
returns.
An
array
of
quotes
so
it'll
bring
back
this
like
an
array
of
these
alright
and
then
I've
got
best
quote,
which
is
a
third-party
library
that
I
imported
into
my
application.
So
I
can
show
you
how
you
can,
in
one
single
graph,
QL,
be
able
to
go,
get
information
from
a
different
source
and
get
information
from
another
different
source,
and
all
of
this
just
works
in
your
schema.
Alright,
so
that's
my
query.
A
A
What
API
brings
back
content
and
content
is
a
Content
Act,
which
is
an
object
that
object
takes
in
quotes
and
copyright,
because,
yes,
it's
not
mine
and
that
brings
in
an
array
of
random
quotes.
Random
quotes
is
an
object
that
takes
in
quotes
and
all
of
these
things-
and
this
is
how,
basically
you
build
your
structure.
So
if
ever
you
find
an
API
that
returns
this
gigantic
information,
this
is
how
you
would
define
it
in
your
schema.
A
Very
sense
anything
all
right
cool,
so
we've
got
a
scheme
on
lockdown,
that's
number
one,
all
right,
so
I've
got
a
UID
generator
here,
because
I
needed
to
generate
my
IDs
of
yes.
So
this
is
my
quote:
who
this
is
just
an
array
of
objects?
It
could
be
a
database,
it
could
be
anything
but
like
who's
got
the
time
and
then
the
second
thing
is
resolvers.
A
Resolvers
you've
got
your
query.
We've
seen
this
I
resolve
the
quotes,
which
basically
brings
back
this
data
array
object
that
you
see
over
here
and
then
the
best
quote,
which
is
going
to
go
into
best,
quotes
API
use
the
API
that
I've
got
over
here
and
then
return
back
some
information
all
right.
So
that's
the
second
query
that
I
have
in
my
subscriptions
I've
got
the
subscriber,
which
is
called
quote
edit.
A
Let's
go
to
my
subscription
here.
You
can
see
that
quote.
Edit
is
actually
the
thing
that
I
provided
into
my
schema
all
right
and
then
that
will
return
a
pops
up
a
async
iteration
that
uses
this.
So
this
is
just
a
label.
It
could
be
like
a
string
of
some
sort
which
here
it's
actually
a
string
but
yeah
you
can
pass
it
a
label
so
that
you
know
which
subscription
that
is
actually
being
generated,
and
then
my
mutation,
alright,
in
a
mutation
this.
This
is.
How
is
all
those
work?
A
What
is
this
queries
in
graph
QL
and
information,
which
provides
the
status
of
that
resolver
all
right,
so
right
here,
I'm
just
taking
in
arguments
whatever
arguments
which
would
be
message
and
author
and
returning
that
back
I'm
here
I'm
pushing
it
into
my
data
that
we
saw
at
the
top,
which
is
just
an
area
of
object,
and
here
I'm
calling
my
subscription
so
that
it
tells
me
that
hey
your
data
has
been
created,
all
right,
okay,
cool
so-
and
this
here
I
create
my
server.
So
a
polo
server.
A
You
provide
the
definition,
which
is
the
schema.
If
we
go
up
here,
it's
the
dude
over
there
and
then
your
resolvers
and
your
data
sources
I
need
my
data
sources
to
resolve.
My
third
API
all
right
and
here
I
just
launched
my
server.
So
if
you
see
in
my
terminal,
obviously
that
you're
not
gonna,
see
but
believe
me
when
I
say:
I
started
it
at
our
port
4000,
so
everybody
who's
at
the
back
and
and
if
we
go
here,
we
can
see
the
server
live
all
right.
A
So
let's
go
querying
remember
when
we
want
to
specify
our
view
from
the
front
end.
We
need
to
provide
the
keyword
which
is
query.
We
need
to
provide
whatever
query
that
we
want
what
we're
interested
in
in
this
case
quotes
and
I
want
you
to
return
messages.
So
this
is
going
to
return
an
array
of
messages
and
in
it,
it'll
have
message,
and
it
will
have
author
if
I'm
not
interested
in
the
also
I
can
just
remove
this
and
call
this
function
again,
and
it
will
only
return
messages
to
me.
A
A
Same
thing,
yep,
oh
there
we
go:
okay,
lovely
thanks
guys.
So
there
you
go,
you've
got
a
mutation,
so
you
provide
the
keyword
which
is
mutation,
and
then
you
create
a
quote
while
the
mutation
that
you
want,
which
is
create
codes
and
provide
the
information
that
is
required,
which
is
the
message
and
the
author,
which
are
both
types
string.
A
So
now
this
thing
I'm
going
to
listen
to
any
creation
of
of
my
quote
and
then
tell
me
that
okay,
hey
and
you
Curtis
Lee
create-
and
this
is
the
message
that
this
person
has
put
in
which
I
think
is
difficult.
Okay,
all
right!
So
I
created
this
nice
API
with
so
many
nice
colors,
for
you
guys
to
see,
and
now
we're
going
to
consume
our
graph
QL
in
our
client
side.
A
A
A
The
second
part
is
I
really
do
not
want
to
do
this
without
a
web
framework,
because
I
also
I'm
not
sure
if
it's
possible-
and
it
really
didn't-
want
the
headache
so
I,
just
like
I
don't
play
and
that's
my
excuse,
all
right
and
I
used
hooks
and
a
lot
of
people
do
functional
components
and
keeping
them
clean
and
don't
want
to
mix
state
with
component.
Yes,
I
understand
I,
believe
that
is
wise,
but
this
is
a
little
bit
clean
for
for
me
and
nonetheless,
and
there's
multiple
things
that
you
can
use.
A
If
you
don't
want
to
use
react
hooks
like
curries
and
tax
or
Apolo
provides
like
query
tags.
If
you
want
to
use
queries,
so
you
don't
necessarily
have
to
use
the
hook
that
they
have
and
if
you
don't
want
to
use
that,
there's
also
like
higher-order
components
that
you
can
use
any
BDD
couples
your
cough
qlr
request
and
you
can't
either.
So
that's
like
the
three
options
that
are
found,
or
maybe
there's
more
so
yeah.
This
is
how
you
would
define
your
schema
in
your
front-end.
A
So
now
we
in
the
front-end
out
my
brains
and
minds
eye
on
the
front
unit.
You
provide
the
the
quotes
that
you
need
of
what
the
query
that
you're
interested
in
in
this
case
its
quotes
and
the
information
that
you
want
back.
Alright,
if
you
call
use
query
again,
it's
a
hook
that
Apolo
provides
for
us.
It'll
give
you
this
information,
which
is
the
loading
information
which
is
a
boolean
value,
that
you
are
false.
So
when
it's
done
it's
false
and
then
it's
still
doing
its
true
and
then
an
error
message.
A
So
this
is
also
another
problem
with
graph
QL.
Is
that,
unlike
traditional
rest
api's,
it
does
not
return
like
statuses,
that
we
know
like
your
for
hundreds
and
whatever,
when
you
request
a
request
in
graph
you'll
give
you
a
to
100,
but
it
will
give
you
an
error
of
inside
of
it,
and
that
will
give
you
some
details
of
what
that
air
is,
and
maybe
that's
not
so
nice
but
like
yeah.
That's
an
option
all
right,
so
error.
A
So
obviously
my
favorite
one
is
like
work
hard
get
paid
by
KFC,
open
it
in
a
taxi,
so
that
everyone
can
smell
your
success
because
it's
so
great,
alright
and
if
someone
is
already
shopping
for
Christmas
for
me
right,
my
sizes
window
seats
in
plane,
ticket
sizes,
so
yeah,
alright,
so
we've
got
that
and
we've
got
our
query
and
we've
got
magic
happening
in
the
front
again.
If
you
want
to
do
or
add
something
right.
So
this
is
how
you
specify
your
mutation
in
to
your
front
end
again,
cute
the
query.
Keyword,
you
you!
A
This
is
just
basically
like
what
you
want
to
name
the
the
mutation
that
you
want
again.
This
is
a
QH
invitation
and
you
provided
the
field
that
you
need
so
in
this
case
a
string.
This
okay.
Let
me
just
go
yeah,
no
see
we've
closed
it.
Something
else
all
right
so
yeah
and
it
will
take
in
again
message
and
author,
and
this
is
what
you
pass
on
to
career
we've
already
seen
this
in
our
graphic.
You
are
right,
but
that's
basically
how
you
would
use
it
and
in
air
quotes
another
hook.
A
That
of
color
gives
us
which
is
used.
Mutation,
and
all
you
need
to
do
is
just
call
the
mutation
that
you
need.
It
will
give
you,
whatever
creation
quote
that
you
are
looking
for
in
this
case,
hey
go
in
Cole
creation,
query
with
the
data
all
right
here:
I
did
some
funky
stuff,
cuz
I
use
you
state
to
go
and
get
information
from
from
the
front
end,
and
this
is
basically
this
piece
that
you
see
at
the
top
yeah.
A
So
I
can
say
fun
times
again
and
in
here
go
Ruby
and
then
add
that
so
you
don't
see
anything
at
the
bottom.
But
if
I
refresh
my
screen,
you
now
see
fun
times,
Rudy
alright,
and
this
is
basically
done
here.
So
those
two.
What
is
this
text
boxes?
Are
here?
I
sit
message
from
new
states
and
I
said:
author
rights
in
those
fields
are
sit
and
then
I've
got
a
function.
A
That
I
call
called
add
new
coat
and
in
here
I
take
in
the
variables
that
I
need,
which
is
message
and
author
from
the
you
state,
and
then
that
calls
are
quotes
and
everything
happens.
Alright
and
yeah.
The
third
part
would
be
subscriptions
subscriptions
in
the
front
end
again
provide
the
keyword
subscription.
What
kind
of
subscription
I
want
and
the
information
that
will
be
returned
in
the
subscription
when
magic
has
happened
and
I
see
now
I've
got
a
console
log
that
it's
got
test.
So
let's
remove
that
and
then
yeah
in
there
you've
got
another.