►
From YouTube: Learning GraphQL - Types
Description
Introduction into GraphQL Types
A
Hello,
everybody.
Today
we
are
going
to
learn
how
to
create
new
fields
or
type
with
craft
Creole
in
github,
so
let's
first
just
go
to
graphically
L,
which
is
a
interactive
playground
or
sandbox,
where
I
can
just
run
your
queries
existing
in
in
the
project.
So
basically
it
was
just
clearing
for
something
if
I'm.
Basically,
there
is
queries
and
mutations
like
there's
a
crude
type,
Square
invitation.
But
if
we
are
green
for
query,
we
shall
don't
have
to
write
this
keyword.
Query
yeah!
So
many
queries.
A
Okay,
so
we
are
search,
for
example,
for
some
project
yeah,
and
we
need
to
pass
some
argument
here
like
to
basically
to
get
right
project
I'll
type,
the
MA,
the
ones
that
I
have
on
my
machine,
okay,
and
we
have
to
actually
write
what
you
want
to
get
in
the
response,
so
I'm
interested
to
like
to
read
the
description
of
the
project
and,
for
example,
Bastion
okay.
So
basically,
this
is
a
search.
This
is
what
we
want
to
get
yeah
so
I'm,
not
the
focus
again.
A
A
Yeah
some
information
here
as
well
all
right,
so
how
it's
gets
so
basically
ever
since
starts
with
this
query
type,
which
is
a
basic
root
type
in
graphical.
So
we
hope
you
can
find
it.
It's
application
types,
graphical
types
and
query
type.
Sorry,
alright,
and
in
this
query
type
we
actually
have
different
wheels
which
are
mounted
to
the
square
and
we
have
actually,
this
project
field
is
actually
what
you're
searching
for
project.
A
Okay
and
it
has
this
project
type
Markel
attack
alright,
and
it
has
this
resolver,
which
is
actually
the
object
which
help
us
to
find
write
project
like
to
first
like
map
this
query
to
our
data
that
we
have
in
the
database.
Let's
just
like,
take
a
quick
link
on
sisters
over
and
it's
quite
simple
and
actually
all
the
resolvers
like
there.
What
do
they
want
to
like?
What
will
they
have?
This
result
method
which
actually
like
do
all
the
stuff
it
has.
A
A
Module
we
can
see
that
is
prevented
too
namespace
and
group
preservers.
So
basically
you
can
query
this
different
objects.
Pi
is
full
possible.
So,
okay,
so
we
have
our
Zoomer.
We
have
logistic
go
straight
to
there's
project
app.
Okay
and
perfect
types
looks
exactly
like
Claro
type
and
it
has
its
own
set
of
fields
a
lot
of
them.
Where
is
our
description?
A
A
Boolean
tap
here,
okay,
so
no
true,
it's
means
that
it
can
be
like
it
can
be.
No
so
good.
There
is
probably
some
project
without
description
and
description
fields.
Okay,
you
can
see
there
is
no
resolver
for
this
fields.
It's
just
because
we
have
this
method
description
on
the
our
project,
so
we
basically
don't
have
to
like
tell
graphical,
have
to
find
this
description.
If
it's
already
exist
on
our
object
project
and
but
for
some
context,
we
don't
they
don't
have.
A
Don't
have
like
one-to-one
correspondence
in
project
object.
We
have
to
actually
here
past
the
block.
As
a
result,
all
we
actually
can
pass
it
as
a
separate
object
like
this
like
resolver.
So
let's
just
create
some
simple
field.
Just
add
something
sound
fail
you
to
the
project:
okay,
let's
just
get
default
label
for
this
project.