►
From YouTube: GSoC: Make your AsyncAPI document shorter with Optimizer - Khuda Dad Nomani, Individual Contributor
Description
AsyncAPI Conference 2021 - Day 1
16th November 2021
Want to cleanup your document to make sure there are no unused or duplicated components? AsyncAPI Optimizer is here to help.
A
Hello,
everyone-
this
is
foreign
contributors
and
also
one
of
the
two
members
of
facing
a
theory
initiative
people
starting
my
talk
about
towards
that
which
is
my
topic
for
today.
I
will
talk
about
a
little
bit
about
my
journey
because
this,
the
first
day
of
the
point
house,
is
dedicated
to
contributors.
A
Well,
I
started
my
journey
as
a
summer
of
good
students
going
through
the
organization's
list
and
then
sourcing.
If
you
have
been
through
the
list
of
ideas
that
you
could
open
with
prepared
in
that
period
of
time,
the
idea
of
even
trading
the
architecture
was
new
to
me
and
having
a
single
specification
form
and
also
tooling,
for
that
file
that
can
give
you
a
documentation,
also
refrigerate
portfolio
for
different
platform.
A
Of
course,
we
have
a
separate
presentation
for
lucas,
which
I
think
is
today
we
talk
more
about
how
to
become
a
testimony
and
how
to
strengthen
journey.
To
me
for
that
and
beside
that,
let's
get
into
it
and
let's
talk
about
optimizer
and
relatives
now.
What
is
optimus
optimizer
is
a
library
that
can
be
plugged
into
cli
tools
and
gui
tools
to
make
your
file
more
optimized,
but
in
other
words,
make
it
shorter.
A
How
exactly
it
works.
As
you
may
know,
we
have
the
component
section
in
our
specification
file
and
you
normally
use
it
when
you
want
to
use
component.
For
example,
when
you
have
messages
or
one
message
that
you
want
to
use
it
in
multiple
channels
or
places,
you
can
just
declare
it
in
the
component
section
and
then
you
use
it
in
preferences
or
if
you
have
a
schema
that
you
want
to
reuse
it.
A
You
can
just
put
it
in
the
component
section
and
then
you
can
reference
it
from
anywhere
inside
your
file,
so
how
this
library
work
is.
It
will
first
of
all
it
will
find
the
duplicated
components
in
your
file,
and
then
it
will
generate
a
report
for
you
to
tell
you
what
components
are
duplicated
and
where
they
are,
and
if
you
want
it
can
help
you
to
move
them
in
the
component
section
and
use
them
or
if
you
have
components
in
the
component
section
that
are
there,
but
you
are
not
using
them
anywhere.
A
A
A
So
I
expect
the
library
to
move
one
of
them
to
the
components
and
then
reuse
that
component
and
then
we
have
a
message
here
that
is
not
used
anywhere
in
our
it's
in
computer
specification
file.
I
expect
to
expect
the
library
to
find
it
and
remove
it.
Then
we
have
this
sent
ad
here
eskimo
and
here
instead
of
using
that
schema,
I'm
writing
the
full
form.
I
expect
the
library
to
find
it
and
then
is,
and
then
I
have
this
send
app
to
this
center.
A
A
A
I'm
I'm
going
to
run
this
project
as
you
can
see
I'm
getting
this
report
here.
It
has
a
three
point.
The
use
component,
as
you
can
see
it
identified
that
that
sent
ad
can
be
used.
It's
identified
that
there
is
an
on
a
message
called
an
unused
message.
It
can
be
removed
and,
as
you
can
see
here,
it
found
that
my
header
can
be
move
two
components
of
the
schemas.
Instead
of
writing
the
food
form.
A
Let's
talk
a
little
bit
about
the
vision
and
the
future
of
this
library.
As
you
may
know,
open
appear
specification
is
very
similar
to,
I
think
appear
specification,
so
it
can
easily
be
ported
for
that.
We
can
add
the
feature
to
support
of
an
api
specification
as
well
as
well
as
json
schema.
If
I
remember
correctly,
they
have
the
devs
part
instead
of
components
which
is
used
for
using
a
component
inside
the
json
schema
specification.