►
From YouTube: Grafana Community Call 2021-09-16
A
And
the
agenda
is
go
through.
Why
we're
showing
this
and
then
go
looking
back
at
the
the
segment
component?
That
is
very
often
used
in
query
builders,
and
that
is
also
basically
what's
going
to
be
the
focus
for
this
presentation.
There
are
more
changes
coming
to
queer
builders,
but
we're
starting
small.
A
A
We
want
community
input
on
it,
as
I
said
before,
we
can
take
small
steps
and
look
at
some
of
the
components
that
are
a
bit
problematic
and
then
hopefully
make
bigger
changes
in
the
future,
so
just
to
show
what
I'm
talking
about
it's
the
area
here
in
panel
edit,
which
is
the
query
builder,
where
you
can
see,
we
create
the
queries
using
this
other
ui,
rather
than
I
was
typing.
The
code.
A
Yes,
so
here
you
can
see
the
segment
components,
so
this
goes
back
to
the
early
days
of
grafana.
So
when
grafana
basically
was
kibana
for
graphite-
and
this
query
builder
was
built
and
it's
quite
logical-
you
just
build
like
adding
segments
in
a
row
and
picking
options
and
in
the
end
you
will
get
your
metric
and
it
will
basically
translate
directly
over
to
code
looking
almost
identical.
A
Constructions
where
you
had
like
a
key
and
a
value-
and
you
also
had
these
more
like
functions
and
all
different
kind
of
things
being
made
with
this
component,
and
that
is
basically
where
we
are
at
today.
So
we
do
a
mix
with
this
component
and
with
regular
inputs
when
we
build
the
query
builders,
so
the
problems
we
need
to
solve.
A
A
In
some
data
sources.
This
is
also
white
instead
of
blue,
and
so
that
is
one
of
the
issues
we're
going
to
solve
and
another
one
is
how
these
behave,
because
you
can't
really
see
it
on
them:
the
expected
behavior
so,
for
instance,
some
of
them
you
can
actually
edit
inside
of
them
some
of
them.
When
you
click
a
part
of
it,
you
open
the
drop
down
and
some
when
you
click
the
whole
thing
you
open
a
drop
down
and
when
you're
going
to
remove
it.
A
Suddenly
click
on
the
area
of
it
and
then
you
can
get
the
toolkit
to
remove
it
and
others
have
this
removed
in
the
actual
drop
down
and
some
you
don't
actually
can
remove.
So
the
idea
originally
with
the
segment
component
was
you
were
not
going
to
remove
it.
You
basically
started
over
if
you
wanted
to
make
changes
and
because
you
always
wanted
like
have
the
full
row
of
segments
to
get
your
metric.
A
But
now,
when
you
sort
of
add
them
as
filters
or
group,
buys
things
becomes
way
more
complicated,
so
looking
them
at
our
proposed
solutions.
So
one
thing
is
that
the
segment
component
will
stay
but
only
be
used
in
cases,
so
it
makes
sense
as
with
the
graphite
case
and
some
other
data
sources
work.
Similarly,
but
we'll
also
create
a
new
set
of
components
and
those
will
be
very
clear
with
how
you
interact
with
them
and
also
have
like
an
indication
where
you
can
click
and
remove
them.
A
A
So
what
will
they
look
like?
So
this
is
one
of
the
of
them
and
it's
pretty
clear
that
the
ones
that
look
like
our
inputs
do
in
other
forms
that
have
the
input
background
are
the
ones
that
you
can
interact
with.
So
in
this
case,
you
can
change
the
key
and
you
can
also
change
the
value
and
also
have
this
delete
button
that
will
remove
it,
and
it's
also
highlighted
on
hoover.
A
And
here
you
have
some
of
the
examples
of
them,
so
the
key
value
pairings
you
have
here,
one
with
fixed,
just
equal
light
as
or
one
where
you
have
you
can
change
that
and
for
certain
data
sources
for
certain
user
groups.
We
might
use
words
instead
of
these
equals
because,
of
course,
the
user
has
to
know
what
these
things
mean.
A
We
also
have
this
one
for
function
where
you
act,
where
it's
not
like
a
key
value
pairing,
but
rather
you
have
parameters
that
you
add
to
a
function,
and
these
are
two
designs
we're
looking
at,
and
this
is
nice.
But
if
it's
not
enough
self-explanatory,
we
will
probably
use
something
like
this,
where
you
actually
see
the
parenthesis,
and
now
I'm
just
going
to
share
what
it
might
look
like
in.
A
For
influx
db,
for
instance,
so
here
you
can
see
some
things
has
changed
and
we
have
a
sub
header.
We
are
looking
into
introducing
that.
Is
this
quite
early
exploration,
but
basically
doing
some
of
the
settings
here
where
you
can
sort
of
pick
metrics
or
logs
in
the
influx
database
case,
and
if
you
want
builder
or
code,
you
can
also
have
certain
options
hidden,
and
this
work
is
very
common
case.
Where
you
have
you,
you
get
your
metric,
but
then
you
have
all
of
these
other
options.
A
You
don't
even
use,
and
you
just
take
up
space
in
the
query
builder,
so
having
the
option
to
sort
of
hide
things,
and
here
you
also
can
see,
then
that
we
have
added
labels
on
topics
instead
and
also
have
a
more
intuitive
labeling.
So
here
we
have
database
for
the
database
rather
than
where
and
then
you
also
have
filters
and
fields.
A
A
So
that
is
basically
the
difference
from
the
four
and
here
I
can
then
also
click
here
and
simply
remove
it.
So
everything
is
quite
clear
how
they
work
and
for
a
function.
It's
similar.
We
just
open
here,
and
I
will
pick
this
one
and
then
I
only
already
had
like
a
value
and
stuff,
and
that
is
what
I
had
to
show
you
so
now.
B
So
I
I
can
start.
I
was
curious
if
you've
thought
about
you
know
now
you're
only
showing
one
field,
but
many
users.
They
have
several.
You
know
filters
and
how
do
you
imagine
you
know,
will
it
just
flow
from
one
line
to
the
next
or
could?
Could
you
show
some
example
of
when
you
have
like
three
or
more
filters,
for
example,
in
this
case.
A
A
Yeah,
where
you
have
multiple,
but
they
also
are
sort
of
you
have
the
option
of
end
on
or
this
might
change
into
a
drop
zone
rather,
and
this
is
sort
of
an
especially
interesting
case-
and
this
is,
I
would
love
you
to
hear
people's
thoughts
on
this,
because
these
situations,
it
creates
more
complicated
queries
when
you,
for
instance,
combine
and
use
both
and
then
or
so
in
influx.
For
instance,
you
could
use
something
and
something
and
or
something,
and
something
and
and
and
so
forth,
so
and
so
that
those
situations
becomes
more
tricky.
A
B
B
Did
you
did
you
look
at
you
know
I,
I
honestly
don't
know
what
that
would
look
like,
but
something
that
is
like
on
a
more
higher
level,
or
did
you
explore
other
more
graphical
paradigms?
Rather
than
simply,
I
know
it's
not
simply,
but
replacing
each
token
in
the
expression
for
a
component.
So
let's
say
well,
I
mean
so.
A
A
B
C
A
B
A
B
B
It's
it's
mostly
actually
what
what
patrick
is
already
highlighted,
that
you
know
no
clear
way
of
removing,
for
example,
there
is
no,
you
know
there's
no.
It
behaves
a
little
differently
from
from
from
data
source
to
data
source.
Also,
I
honestly
I
feel,
like
I
sometimes
have
a
difficult
time.
You
know
figuring
out
how
to
map
my
my
expression
to
these
segments,
because
I'm
I'm
actually
thinking
about
the
the
code
expression.
How
would
I
write
this
as
a
query?
B
Usually
I
what
I
send
to
the
data
source
is
code,
and
I
need
to
go
through
this
process
of
trying
to
translate
that
into
a
graphical
representation,
and
I
I've
struggled
to
do
that
with
the
segment.
So
I
I
think
I've
I've
kind
of
used
other
tools.
You
know
like
great
radio
button
and
drop
downs
and
text
fields
and
to
to
because
I
think
they're,
simpler
and
yeah.
D
Is
there
something
else
that
could
help
you
in
terms
of
thinking
from
like
how
that
query
would
look
like
in
code
how
to
translate
this
into
this
interface?
Is
there
anything
else,
apart
from
what
patrick's
showed
that
could
actually
help
you
in
a
way
to
make
this
transition
from
thinking
in
in
terms
of
code
into
and
translating
that
into
interface.
B
So
I
I
guess
a
challenge
here
is
that
we're
looking
for
something
that
works
for
for
many
of
them
and
for
a
plug-in
author,
at
least
for
me,
I,
the
the
biggest
challenge
is
to
you
know.
I
actually
need
to
do
the
work
to
translate
this
into
how
a
graphical
representation
would
look
like,
and
I'm
I
mean
I'd,
love
a
a
rich
ui
library.
So
I
can
pick
the
one
that
makes
more
sense.
A
A
So
this
sort
of
makes
sense,
because
I
think
that
that's
have
been,
though
the
whole
big
challenge
is
that
as
you're
saying
you
use
a
segment
component
or
a
regular
drop
down
or
input
just
to
sort
of
get
things
to
work,
and
then
in
many
cases
I
think
the
segment
components
feels
a
bit
hacked
that
people
are
sort
of.
I
needed
to
do
this
so
then
to
add
that
sort
of
functionality
to
it,
but
then
it
doesn't
really
necessarily
make
sense
for
the
user.
B
When
they're
using
it
like
one
one
nice
thing
about
the
current
segment
component
is
that
it
makes
it
rather
compact.
You
know
you
can
write
something
it
doesn't
take
up
that
much
space
in
your
query,
editor-
and
I
guess
my
first
impression
here-
is
that
there
will
it
takes
up
more
space.
This
component
is,
is
more
spacious,
so
I'd
be
curious
to
see
how
it
would
scale
with
especially
you
know,
maybe
smaller
screens,
someone
looking
at
their
laptop
and
it's
a
limited
area.
A
Yeah,
I
think
that
is
sort
of
this
has
been
a
challenge
from
the
beginning.
Is
that
I
mean
the
segment
component
looks
the
way
it
looks
for
a
reason,
but
that's,
as
you
said,
it's
pretty
compact,
but
so
yeah.
So
this
needs
to
be
sort
of
tried
out
with
data
sources
and
see
also
I
mean
how
many
filters
do
you
add
when
you
do
a
query
and
how
many
group
bytes
and
so
forth,
so
so
it
makes
sense.
A
E
So
you
know
I
would
say
as
a
whole.
You
know
folders
are
very
helpful,
but
there
are
definitely
some
limitations
in
our
current
design
of
folders
today.
So,
for
example,
when
you
first
head
into
the
manage
area
and
then
you're
sort
of
seeing
that
top
level
list
of
folders
and
dashboards,
you
can
delete
folders,
but
you
can't
do
much
else
with
folders
you
other
than
travel
to
go
kind
of
inside
of
them.
E
So
you
know
kind
of
doing
anything
with
folders
requires
multiple
clicks
and
sort
of
multiple
levels
down
into
the
information
architecture
as
a
whole,
and
then
once
you
get
into
the
folder,
we
have
sort
of
tabs
that
are
doing
a
couple
of
things.
Some
of
the
tabs
are
allowing
you
to
take
actions
such
as
set
permissions
or
adjust
settings
and
other
tabs.
E
E
You
should
also
generally
be
able
to
do
with
a
library
panel,
for
example,
and
then
we
also
have,
I
don't
think
it's
sort
of
like
officially
out,
but
we
do
have
an
upcoming
piece
of
content
called
a
library
variable
which
is
going
to
be
basically
a
template
variable
that
can
be
reused
across
dashboards
so
very
early
days.
For
that
one,
I
don't
have
a
sneak
peek
of
it,
but
we
do
have
to
kind
of
come
up
with
a
place
to
put
this.
E
That
makes
sense
and
allows
you
to
do
things
like
we
do
today
with
library
panels
such
as
set
permissions
and
organize
and
manage
that.
But
above
all,
really.
What
I
want
to
make
sure
is
that
any
changes
that
we
make
to
how
we're
navigating
within
folders
and
managing
folders,
that
we
don't
break
anything.
That's
currently
working
well
for
our
current
users.
E
So
this
is
how
you
can
reach
me
and
I'll
come
back
to
this
after
I
show
the
designs,
but
you
can
email
me.
You
can
reach
me
on
our
public
slack
at
amy
super,
but
definitely
I'm
really
looking
for
some
people
to
just
spend
a
little
bit
of
time
with
me
and
give
me
a
better
idea
of
kind
of
what
your
folder
structures
look
like
today,
so
that
we
can
make
sure
that
we're
optimizing.
The
experience
for
you
so
before
I
get
into
the
designs.
E
E
One
of
the
things
that
I
wanted
to
do
so
today
we
have
three
buttons
across
the
top.
Here
we
have
new
folder
import,
a
new
dashboard,
but
import
is
really
just
creating
a
new
dashboard
from
an
import
action.
So
I
just
wanted
to
kind
of
collapse
those
down
into
one
button,
because
we're
going
to
need
that
space
for
some
other
stuff
as
you'll
see
a
little
bit
later.
E
We
still
show
our
tags
with
dashboards
as
we
do
today,
and
I'm
I'm
exploring
this
sort
of
info
column
where
we
can
show
for
a
dashboard.
For
example,
whatever
has
been
put
into
the
description
field
in
the
dashboard
settings
for
the
variables
and
panels
sort
of
what
their
usage
is
so
with
library
panels
today,
if
you
click
to
view
a
library
panel
at
that
point,
then
you
get
a
list
of
all
of
the
dashboards
in
which
it
is
used,
but
you
don't
know
until
you
sort
of
like
go
investigating.
E
E
B
I'm
I'm
curious
about
the
library
variable
a
little
bit.
It
says
that
it's
used
in
in
two
dashboards
and
three
panels.
This
might
be
a
little
outside
what
you're
currently
showing,
but
it's
just
curious.
How
are
we
envisioning
that
you
know
when
you
change
it
in
one
dashboard?
Will
it
change
for
all
other
dashboards?
Will
it
be,
you
know,
will
the
value
be
shared
or
is
it
just
the
values
in
that
variable
so
to
say.
E
So
I'm
not
completely
familiar
with
how
this
is
going
to
work
yet
marcus.
But
my
understanding
is
that
because
it
is
a
library
element
that
yes,
the
idea
is
that
you
update
it
once
and
it
kind
of
pushes
the
changes
everywhere,
just
like
with
a
library
panel
today.
So
you
update
the
library
panel
in
one
dashboard
and
then
it
will
update
it
elsewhere.
But
if
you
don't
want
to,
you
would
have
the
ability
to
sort
of
unlink
it
from
that,
like
parent
element
or
from
that.
E
B
E
It
is
a
frequently
asked
question:
there
are
some,
not
small
technical
limitations
for
us
on
nesting,
so
right
now,
for
you
know
my
particular
effort.
That
is
not
part
of
the
scope
right
now,
but
I
will
say
that
the
design
I'm
going
for
here,
I
think,
could
be
expanded
to
support
nesting.
But
we
got
to
solve
those
technical
problems
before
we
can
actually
do
that.
E
Cool
okay,
so
I'm
going
to
go
ahead
and
move
on
then.
So
the
next
thing
we're
going
to
take
a
look
at
are
the
sort
of
folder
actions,
so
you'll
notice
that
I
have
these
sort
of
little
icons
here
and
you
know,
as
I
mentioned
before
today,
we're
using
tabs
to
give
you
an
opportunity
to
take
action
on
things
so
such
as
set
the
permissions
or
edit
the
name
and
then
delete
is
sort
of
like
in
multiple
places.
E
So,
for
example,
if
I
want
to
change
the
permissions,
I
would
click
this
permissions
lock
button
icon
and
you
can
see
that
the
sort
of
permission
panel
that
we're
accustomed
to
seeing
in
many
places
just
expands
down,
and
one
of
the
reasons
I
really
you
know
kind
of
went
for
this
approach
is
that
I
can
see
not
only
what
I'm
doing,
but
I
can
see
everything
that's
going
to
be
affected
by
that
action.
So
today,
when
you
leave
the
tab,
maybe
you
forget
what
dashboards
are
in
there?
E
E
Likewise,
if
you
wanted
to
change
the
settings
right
now
settings
the
settings,
tab
is
really
just
renaming
and
deleting
so
this
one's
a
lot
easier.
It's
just
a
field
that
we
can
update,
though
there
definitely
are
other
ways
that
we
could
solve
this
particular
problem
that
we've
talked
about
on
the
team
and
I'm
continuing
to
explore,
and
then,
lastly,
with
delete
so
delete's
a
little
different,
it
should
be
a
modal,
and
here
is
why
this
could
be
a
very
destructive
action.
E
E
What's
going
to
be
affected,
you
know
you
can
kind
of
see
it
under
the
modal,
but
I
can't
always
guarantee
where
the
scroll
is
going
to
be
on
the
page
when
you
do
this,
so
that's
why
I'm
providing
that
listing
again
and
then,
because
alerts
are
managed
in
a
little
bit
of
a
different
way.
I'm
envisioning
right.
D
D
E
E
E
E
But
I
think
that
to
sort
of
come
back
to
diana's
point
of
like
are
people
mostly
using
search,
or
you
know
how
many
things
are
in
each
people's
folders.
That's
why
I'm
really
hoping
to
get
people
to
reach
out
to
me
so
that
I
can,
you
know,
learn
a
little
bit
more
about
like
what
your
setup
looks
like,
so
that
we
can
make
these
decisions
better
so
that
I
don't
end
up
with.
You
know
a
modal
that
scrolls
off
of
the
screen,
for
example,
or
or
maybe
that's
not
really
a
problem.
E
So
I'm
gonna
move
on
and,
like
I
said,
I
have
a
couple
variations
on
these,
but
I'm
not
gonna
go
too
far
into
them
today,
but
the
other
thing
that
I'm
looking
at
is
from
a
filter
perspective.
So
now
we're
ignoring
the
table
down
here
and
we're
talking
about
this
space
up
here.
So
once
again,
there
are
a
lot
of
things
you
can
do
here
even
today,
so
you
can
search.
You
can
create
new
things.
You
can
view
it
by
a
folder.
You
can
view
it
as
a
list.
E
You
can
sort
it
today.
We
show
that
you
know
see
the
ones
that
have
stars
see
the
ones
that
don't
have
stars
see
the
one
you
know
filtered
by
a
specific
tag,
and
so
again
it
sort
of
starts
to
get
a
little
crazy
in
terms
of
the
number
of
things
that
you
can
do,
both
from
a
visual
perspective
and
from
a
keyboard
navigation
perspective,
and
so
one
of
the
things
that
I
am
playing
with
is
putting
those
filters
into
this
sort
of
like
top
of
the
page
but
collapsed
view.
E
So
what
I'm
showing
here
is
that
I've
previously
set
filters
where
I'm
only
going
to
show
dashboards
and
I'm
only
going
to
show
dashboards
that
do
not
have
stars
and
again
ignore
the
table
down
here.
I
didn't
actually
set
the
filter
in
my
design
here,
so
we're
just
going
to
focus
on
what
happens
up
here,
not
on
what
the
effects
would
be.
E
E
E
B
I
have
one
very
specific
type
of
feature.
I
hope
that's.
Okay,
yeah,
like
one
thing
that
caught
my
eye,
is
it's
visible
right
now,
but
the
like
the
summary,
the
text
summary
next
to
hide
filter
options
there?
Yes,
that
one
right
now
it
feels
like
the
filter.
Key
is
a
bit
redundant
or
it
does
to
me
it
doesn't
add
anything
you
could
have
just
said
like
dashboards,
not
starred
or
something
like
that.
But.
B
B
E
Yeah
yeah,
I
mean
that's
great
feedback,
and
I
admit
that
I
kind
of
hesitated
on
this
one
personally
as
well,
because,
again
kind
of
going
back
to
my
point
of
like
I
would
love
to
talk
to
people.
What
I
am
not
sure
of
is
is
this
too
technical
for
some
of
our
users,
who
are
only
viewing
dashboards
and
just
want
to
filter
their
view
to
do
this
sort
of
like
type
equals
and
such
like
that
you
know
so
maybe
it
does
need
to
be
a
little
bit
more
plain
language.
E
You
know
I.
I
think
that
really
depends
for
me
personally
on
who's
using
this
heavily
day-to-day
and
and
that's
something
that
I
don't
feel
like.
I
have
a
good
sense
for
right.
This
moment
is
how
heavily
are
our?
Not
so
technical
users
are
doing
things
like
filtering,
or
are
they
just
going
to
search
every
single
time?
For
example,.
B
I
think
I
would
in
this
case
again
because
it's
a
like
limited
number
of
filter
options.
I
I
would
expect
to
be
like
in
a
more
quick
access,
quick
actions
view
because
you
know
just
click.
I
want
to
see
all
the
starred
ones
or
or
not,
and
what
type
I
want
to
see.
I
I
guess
this
you
know,
encourages
me
to
go
into
like
a
filter
mindset.
Okay,
now
I'm
going
to
write
a
filter
for
all
the
dashboards.
B
I
want
to
see,
and
I
think
it
has
to
motivate
you
know,
and
I
I
need
to
build
a
really
complicated
filter
for
it
for
me
to
feel
like
it's
worth
it
in
a
way.
So
our
I
guess
my
follow-up
question:
are
we
looking
to
add
more
filter
options
for
for
dashboards,
or
is
there
realistically
not
going
to
be
more
than
two
three
of
them.
E
Right
now,
I
don't
think
we're
adding
more,
but
that
doesn't
mean
they
won't
come
up
in
the
future.
But
let
me
show
you
one
of
my
other
explorations
that
is
much
much
earlier
in
life
that
might
address
some
of
your
questions
or
your
concerns
about
this
one,
because
it
doesn't
have
to
be
laid
out
just
like
this,
but
I
I
think
it
kind
of
goes
to
the
point
that
you're
making
here
so
in
this
one,
my
sort
of
filter.
E
You
know
I
just
have
the
summary
that
I
have
two
filters
set
so
rather
than
saying,
like
filter
type
equals
et
cetera,
et
cetera,
I'm
just
saying
like
hey.
This
is
a
filtered
view,
you're,
not
seeing
everything
and
I'm
kind
of
again.
I
don't
love
the
layout
of
this
in
particular,
but
this
is
a
little
bit
more
of
like
an
e-commerce
looking
filter
where
it's
just
these
very
quick
like
these.
You
know
you
can
filter
by
type
by
start
or
by
tags,
and
these
are
your
options.
E
B
D
Yeah,
it's
definitely
less
cognitive
loud
to
use
something
like
that,
and
you
know-
and
now
it's
my
gut
feeling,
but
that
is
something
we
have
to
get
feedback
on
or
research
a
bit.
But
when
people
look
for
dashboards
they,
I
don't
think
they're
looking
to
build
another
query
to
find
the
dashboard
they
want
to
do
it
super
quick
and
super
effectively.
E
Yeah,
that's
that's
all
great
feedback.
What
about
the
sort
of
like
right
hand,
drawer,
opening
up
versus
putting
this
type
of
element
in
like
I
could
put
that
in
a
an
accordion
over
here
so
similar
way
to
get
there
as
my
last
option
so
rather
than
in
a
drawer,
have
it
sort
of
push
the
rest
of
this
content
down
the
screen,
but
have
it
be
these
really
quick,
easy,
checkboxes
and
switches.
D
Yeah,
I
think
that
is
a
new
part
like
the
drawer
used
in
that
way
is
a
new
pattern
that
we
would
introduce
and
I'm
not
sure
whether,
with
only
those
three
options,
it's
not
an
overkill
to
be
honest
and
actually
having
this
expandable
in
some
way
at
the
top
of
the
list
of
dashboards
would
be
probably
a
bit
better,
but
still
gut
feed.
Yeah.
B
C
E
E
The
other
thing,
too,
is
that
I
have
been
thinking
that
as
a
drawer.
This
is
a
really
big
element.
It
just
feels
a
little
heavy-handed
to
me
for
what
these
interactions
are.
It
feels
like,
I
should
be
doing
a
lot
more
here
or
reading
a
lot
more
here
than
just
sort
of
hitting
these
filters,
it's
sort
of
again
to
sort
of
diana's
point,
my
gut
feeling,
which
is
why
I
didn't
show
this
first,
because
I
think
that
what
I
don't
like
about
it
is
the
drawer
itself.
C
C
What
you
could
possibly
do
for
like
try
to
optimize
for
the
filtering
is
like
you,
look
for
different
type
of
components
and
like
see
like
the
best
case
scenario
depending
and
choose
from
one
or
two
components
like
for
example.
In
this
case
you
have
the
text
listed
vertically
right
and
that
that
list
can
grow
pretty
much
indefinitely,
but
you
could
potentially
show
like
an
autocomplete
version
where,
as
soon
as
you
start
typing,
you
have
the
name
of
the
tag
and
use
like
pretty
much
a
different
type
of
component
that
will
make
it.
C
D
A
A
So
yes,
as
long
as
you
sort
of
get
some
sort
of
a
good
aligned
solution,
I
guess
I
mean
different
cases
might
have
some
differences,
but
at
least
I
would
treat
filtering
especially
on
tight,
maybe
or
restart
and
so
forth,
and
another
thought
is,
if
tag
filtering
can
sort
of
become
a
part
of
the
search
input.
I'm
not
sure
if
that
makes
sense,
but
we're
having
a
more
advanced
search.
So
you
sort.
E
It
doesn't
sound
horribly
difficult,
but
I
think
there
are
a
couple
of
things
that
will
need
to
be
solved
to
make
that
happen.
So
that's
something
I
will
definitely
take
note
of
when
it's
time
for
me
to
start
having
those
conversations
of
not
just
you
know,
hey,
is
it
okay,
you
know,
can
we
search
all
of
this
stuff,
but
also
like
now?
What
else
can
we
do
now
that
this
is
all
available
from
one
view?
I
think
it
really
opens
up
a
lot
of
great
possibilities
for
navigation
within
your
list
of
content.
E
So
I
just
want
to
put
in
one
more
plug,
for,
let
me
know
if
you
want
to
look
at
these
more
in
depth.
Let
me
know
if
you
want
to
show
me
how
things
are
working
or
not
working
for
you
today,
definitely
interested
in
hearing
more
so
that
we
can
make
these
decisions
based
on
more
than
kind
of
our
gut
feelings
and
how
we,
like
you
know
how
we,
how
we,
like
the
looks
of
things
for
example.
So
again
more
than
anything,
I
don't
want
to
break
anything,
that's
working
today.
B
That's
it
for
me,
thank
you
so
much
and
thank
you
all
to
for
joining
again.
This
will
be
available
on
youtube
in
the
coming
days,
so
stay
tuned
and
don't
forget
to
join
us
for
next
month,
where
we're
gonna
see
the
the
back
end
squad,
I'm
not
entirely
sure
what
the
what
they
will
be
talking
about
you
just
yet,
but
we
will
announce
it
over
the
course
of
the
next
weeks
so
stay
tuned.