►
From YouTube: Adaptive Cards community call - February 2021
Description
This month's community call’s focus - Latest with Adaptive Cards in Team. Topics covered: Full Width Adaptive Cards, Static Autocomplete (type ahead), Input validation and labels, Information Masking, Person Component, ActionSet Flyout (Overflow), and People Picker (an adaptive component). Many of the features are in Dev Preview today and soon to be GA – first in Teams and then in other apps over coming months. This session included Q&A. The call was hosted by Matt Hidinger (Microsoft). Presenters include Matt Hidinger and Ojasvi Choudhary (Microsoft). Recorded on February 11, 2021.
Presenters:
• Matt Hidinger (Microsoft) | @MattHidinger
• Ojasvi Choudhary (Microsoft) | @Ojasvi
Stay connected:
• Twitter https://twitter.com/microsoft365dev
• YouTube https://aka.ms/M365DevYouTube
• Blogs https://aka.ms/M365DevBlog
• Recurrent Invite https://aka.ms/adaptivecardscommunitycall
• Next call: March 11th at 09:00am PST
A
Hi
everyone
thank
you
for
joining
the
adaptive
cards
community
call
on
february,
11
2021.,
I'm
matt,
heidinger.
I've
been
doing
these
calls
for
a
couple
of
years
now
talking
about
adaptive
cards
and
we've
been
those
of
you
joining
the
call
every
month.
I
really
appreciate
it.
We've
been
talking
about
a
lot
of
stuff,
and
this
month
I'm
going
to
be
mostly
quiet
and
handed
over
to
ajasvi,
who
also
works
at
microsoft.
A
A
A
But
basically
one
of
the
big
things
we'll
be
announcing
and
releasing
between
now
and
the
summer.
Time
frame
is
what
we're
calling
the
universal
action
model
and
it's
a
way
to
write
cards,
the
same
way
for
outlook
and
microsoft
teams
and
hopefully
more
apps
in
the
future,
where
you
can
write
a
single
back
end
about
framework
bot
handle
the
actions
respond
with
a
new
card
to
kind
of
refresh
things.
B
B
This
is
something
that
we
announced
in
ignite
last
year
and
the
intent
was,
if
you
look
at
a
bot
over
here
within
the
team's
chat
plane,
there's
quite
a
bit
of
space
to
go
horizontally
in
terms
of
like
the
width
of
the
card
to
take
up
all
of
this
extra
space.
You
won't
have
to
worry
about
your
sentences
being
crowded
and
stuff
like
that,
so
really
wanted
to
just
just
expand
the
space
of
the
card.
B
In
retrospect,
this
is
one
of
those
things
that
looks
like
oh
yeah,
that's
pretty
straightforward,
but
then,
when
you
go
ahead
and
actually
implement
it,
you
know
there
are
various
things
that
we
can
do
with
like
the
windows
within
microsoft.
Teams,
right
you
can.
You
can
pop
out
chat,
which
totally
changes
like
the
width
and
with
new
responsive
design.
B
So
if
you're
looking
at
in
terms
of
like
how
to
use
it,
all
you
have
to
do
is
since
this
property
is
like
host
specific,
because
if
you
move
to
a
different
host
like
the
the
dimensions
of
the
cards,
would
change
and
right.
So
within
the
microsoft
teams
area,
you
can
say
that
okay
width
is
equal
to
full
and
that's
it.
B
So
this
is
also
another
feature
that
is
in
depth
preview,
and
what
you
see
over
here
is
that
hey
we've
got
our
you
know
all
of
us.
We
need
to
file
an
expense
report
and
you
know
we're
at
the
stay
at
home
sales
conference
in
2020.
So
how
do
you
do
that?
Well,
one
way
is
that
this
would
be
like
a
normal,
a
normal
input
choice
set
and
you
would
have
like
the
expanded
categories
were
within
there
and
you'd
have
like
all
these
different
types
of
like
travel
expenses
that
you
could
have
fired
now.
B
B
Take
the
same
input,
choice
set
and
just
start
typing
through
it
and
eventually
what's
gonna
happen
is,
like
you
know,
you'll
be
able
to
select
the
right
one,
it
very
simple,
but
again
we
think
it's
going
to
be
rather
powerful
in
terms
of
like
the
main
experience
and
yeah
it's
just
the
intent
behind
this
was
like.
If
you
look
at
the
way
adaptive
cards
are
being
used
inside
teams,
especially
for
bots,
like
form,
completion
ends
up
being
like
a
typical
use
case
like
it's.
B
A
whole
lot
of
applications
consider
form
completion
or
some
sort
of
like
input,
completion
to
be
very
core
to
their
scenario.
So
that's
that's
another
like
angle
as
to
why
you
think
you
know,
auto
complete
is
going
to
be
really
powerful
in
terms
of
schema.
All
you
have
to
do
is
this:
is
your
standard
input
choice
set?
All
you
have
to
do
is
take
style
and
change
it
to
filter,
and
that's
basically
is
everything
that
you
have
to
do
to
enable
a
static
autocomplete.
B
Now
both
of
these
features
are
in
depth
review
today,
so
you
can
go
today,
change
your
team's
client
to
depth
review
and
try
both
of
these
out.
If
you
have
questions
on
how
to
do
that,
just
paste
it
in
the
chat-
and
I
can
share
some
documentation
and
in
terms
of
like
how
to
go
ahead
and
actually
switch
and
do
that.
So
let
me
give
a
demo
of
both
of
these
just
real,
quick,
okay.
B
So
here
I
am
now
within
teams
and
I'm
using
the
app
studio
bot
which,
if
you
haven't
by
the
way,
it's
a
great
tool
to
see
how
your
cards
are
gonna,
look
within
teams,
so
it's
available
in
the
team's
app
store
over
here
and
you
can
just
download
it
and
there's
a
neat
little
card
editor
that
you
can.
You
know,
use
to
see
visualize
and
send
cards.
B
The
other
benefit
of
this
is
gonna.
Be
is
like
a
lot
of
times.
If
there's,
if
your
card
is
too
much
information,
it'll
just
end
up
covering
your
entire
chat
page
so
you're
going
to
have
to
like
keep
on
responding
to
the
bot
again
and
again,
this
sort
of
mitigates
that
the
application
messages
are
going
to
be
a
little
well
spaced
out,
and
so
this
is
one
right.
I
think
just
you
can
go
ahead
and
try
it
today.
I
think
pretty
excited
about
this.
B
The
second
one
that
I
can
show
you
demo
off
is
autocomplete
and
type
ahead.
So
over
here
we've
got
a
land
survey
and
this
is
the
same
standard
input,
choice
set
and
adaptive
cards
and
we've
got
a
bunch
of
options
over
here
and,
as
I
start
typing
restaurants,
I
can
see
their
name
right
so
yeah.
This
is
what
it
is.
It's
basically
standard
type
ahead.
I
can
select
it
and
then
I
can
respond,
but
I'm
not
gonna
respond
because
the
bot
is
down
right
now,
but
you
know
other
than
that.
A
There
have
been
some
in
the
chat
cool.
It's
awesome,
seeing
those
like
live
demos.
I've
had
this
stuff
in
schema
form
for
so
long.
It's
cool
to
kind
of
see
it
in
the
teams
app.
I
think
the
main
questions
that
you're
gonna
probably
get
over
and
over
is
when
will
it
move
from
dev
preview
to
ga?
Do
you
have
that
information
yet
eddie,
sir.
A
B
B
Yeah,
we
definitely
have
docs
for
that.
Okay,
moving
ahead,
so
input
validation.
So
this
feature
was
released
as
part
of
adaptive
cards
1.3
and
I
believe
we've
already
got
the
documentation
up
for
that.
On
the
adaptive
adaptivecast.io
side,
we
are
in
the
process
of
taking
up
a
1.3
right
now
it
was
checked
into
the
lower
ranks,
I
believe
just
one
or
two
weeks
ago.
So
again,
this
is
something
we're
hoping
will
be
a
in-depth
review,
if
not
g8
by
march
2021
as
well.
So
you'll
have
that
available
over
here.
B
D
A
The
slides
that
I
I
threw
in
and
didn't
tell
them
there
there's
a
couple
things.
That's
really
neat
here
beyond
just
input,
validation,
there's
also
that
label
property.
So
if
you
look
closely
at
this
choice
set
here,
there's
that
text
above
it
that
says
how
would
you
like
your
burger,
prepared
and
then
the
little
red
asterisk?
A
So
this
used
to
be
pretty
verbose.
You
used
to
have
to
have
a
text
block
above
the
choice,
set
a
text
block
to
label
it
that
had
poor
user
interface
things
because
you
typically
in
a
form,
especially
in
an
accessible
form.
You
can
click
on
the
label
and
that'll
focus
the
input.
So
this
now
has
a
much
tighter
association,
a
much
better
accessibility
story
so
using
that
label.
If
it's
required,
we
can
automatically
put
the
red
asterisk
in
there.
You'll
get
the
error
message,
so
it
really
did
improve
the
the
form
validation
stuff.
A
Quite
a
bit.
Now
the
thing
I
would
caveat-
and
this
is
a
bit
of
a
tricky
thing-
that
like
even
on
our
docs-
we
don't-
we
haven't
updated
all
of
our
samples
to
use
this
label
stuff
because
not
all
of
our
hosts
are
on
1.3.
Yet
so
it
you,
you
can't
really
use
that
you
can
use
this
label
property
in
teams
soon,
but
it
won't
work
in,
say,
outlook,
cisco
webex,
I
think,
is
still
in
process
of
rolling
out
1.3.
A
B
E
B
It
it
just
works
interesting
thing
about
this.
One
is,
I
think,
that's
link
the
github
issue
over
here,
so
you
want
to
go
and
read
the
schema
in
more
detail.
Another
interesting
thing
about
over
here
is
just
I
just
want
to
like.
Have
you
walk
through
like
the
diversity
of
features
and
scenarios
that
we're
thinking
of
like
we
started
with
white
width
for
design
coherence,
then
static,
type
ahead
for
scenario?
B
Next
up,
we've
got
persona
component,
so
that's
also
liked
all
of
the
github
issues
for
all
of
these,
typically
right,
like
teams,
is
fundamentally
a
collaborative
app
where
you're
chatting
with
people
you're
bringing
people
together
to
get
work
done.
In
this
particular
case,
you
can
say
that
there
is
some
sort
of
an
approval
app
by
the
way
we
just
gave
the
approvals
app,
which
is
a
really
great
example
of
like
a
modern
message.
Extension
using
adaptive
cards
coming
together
in
teams
so
check
it
out.
B
If
you
like,
to
get
some
sense
of
like
what
essentially
is
fundamentally
possible
with
all
of
these
together
but
many
times
within
the
person
component,
you
want
to
see
like
who
it's
assigned
to
and
visually
it's
just
easier
that
you
know
this.
Particular
approval
was
requested
by
daniella
and
it
needs
to
be
approved
by
these
people
or
it's
already
been
approved
by
these
people.
Furthermore,
you
could
just
hover
over
her
prison
icon
and
it
opens
the
person
card,
and
then
you
can
just
chat
straight
away
from
there
as
well.
B
B
A
Yeah,
so
basically,
what
you're
looking
at
here
is:
we've
talked
about
in
the
past
this
concept
of
for
those
of
you
who
are
long-time
listeners
of
this
call.
We've
talked
about
this
thing
called
adaptive
components
and
it's
the
it's.
It's
going
to
be
our
official
way
of
bundling
in
these
kind
of
higher
level.
Things
like
molecules,
if
you
will
like
people
and
files
and
mail
like
you,
just
want
to
kind
of
drop
in
some
other
piece
of
data
and
have
the
rendering
taken
care
of
for
you.
A
So
the
github
issue
is
going
to
be
the
best
place
to
follow
along
with
that,
we're
not
announcing
or
releasing
the
full
adaptive
component
model
right
now,
but
teams
is
going
out
of
the
gate
with
the
first
one
of
them,
which
will
be
a
user
component,
and
so
the
syntax
you're
going
to
see
right
here.
You
say
this
is
a
component.
A
The
only
one
that
will
work
out
of
the
box
is
graph.microsoft.com
user.
So
this
is
a
user
component
or
a
person
component
and
again,
you
can
sort
of
see
this
pattern
would
be
applied
later
on.
If
you
want
to
drop
a
file
into
the
card,
well,
you
would
say:
here's
a
component
and
the
name
is
graph.microsoft.com
file,
or
maybe
it's
a
dropbox
file,
or
maybe
it's
whatever
it
is,
and
you
just
all
you
have
to
pass
along
is
the
data,
the
properties
of
this
thing
and
the
component
model.
A
The
adaptive
component
mod
will
take
care
of
rendering
it
so
you
don't
have
to
lay
out
the
person
icon
next
to
the
name.
If
it's
a
file,
you
don't
have
to
do
anything
about
the
display,
so
we'll
take
care
of
a
lot
of
that
heavy
lifting
and
that's
super
useful
if
you
just
want
to
put
a
little
snippet
of
data
right
in
the
card.
So
this
is
an
early
look
at
the
first
one
of
those
and
you
can
follow
along
in
that
github
issue.
C
A
A
B
B
B
Configurable
aren't
necessarily
front
and
center
for
the
user,
so
you
can
take
these
secondary
actions,
preserve
this
precious
real
estate
for
the
user
and
like
what
you
really
want
to
communicate
and
move
the
secondary
actions
under
the
ellipsis
menu,
and
that
is
what
we're
going
to
call.
The
action
set
fly
out
of
the
overflow
menu
will
help
within
deems.
A
And
I
did
throw
in
a
little
sample
of
how
it
worked
so
walk
through
the
sample,
real,
quick,
there's,
two
cool
ways
of
using
the
actions
that
fly
out.
You
can
either.
If
you
go
back
one
slide
real,
quick
at
josby.
You
can
put
them
on
your
top
level.
Actions
and
teams
does
a
really
cool
thing
to
organize
those
actions.
So
you
can
extend
these.
I
like
this
slide.
I
think
it's
really
pretty
to
like
zoom
out,
but,
like
you
know,
you
can
basically
extend
these
things
with
any
custom
actions.
A
So,
instead
of
read
online
download
issue,
you
know
you
would
put
them
there
and
if
you
go
to
the
next
slide,
all
you
do
is
add
a
mode
secondary
to
your
actions.
So
if
it's
at
the
top
level
card
actions
they
overflow
into
that
teams
bucket
with
the
dot
dot,
but
you
can
also
use
them
inside
your
card.
If
you
want
an
experience
kind
of
like
seen
here
where
you
just
have
an
action
set
in
a
column
and
all
of
the
actions
are
secondary,
which
means
they're
all
going
to
overflow.
A
So
it
lets
you
kind
of
build
these
more
powerful
cards
without
taking
up
a
ton
of
real
estate
and
that's
issue.
4715
and
just
to
reiterate,
for
some
people
that
may
have
came
in
these
features
are
coming
to
teams
first
they're
coming
to
teams
before
everything
else,
teams
needed
them
quite
a
bit
and
our
team
is
still
growing.
So
you
know
we're
basically
they
they
had
kind
of
helped
out
implementing
some
of
these
so
that
they
could
get
an
early
lead.
A
B
The
the
action
set
fly
out
is,
I
mean
we're
working
directly
with
the
sdks.
This
one
is
going
to
be
available
as
part
of
the
sdk
and
it's
going
to
be
available
simultaneously
in
the
sdk
and
in
teams
like
the
some
of
the
other
ones,
will
be
about
other
games
before
so
last.
One
we've
got
people
picker
again
going
back
to
like
our
form
completion
scenario.
B
There
is
a
huge
person
component
in
terms
of
like
collaborating
and
like
getting
the
right
assigning
the
tickets.
For
example,
in
this
case,
you've
got
like
hey.
You've
got
to
take
it
out.
My
vpn
isn't
really
working
it's
raised
by
susan.
Well,
I
asked
the
person
who
is
triaging
this
issue.
I
really
need
to
move
the
ticket
forward
and
like
assign
it
to
a
particular
person.
B
So
if,
if
you
wanted
to
do
this
by
yourself
like
create
a
people
picture
with
an
adaptive
cards,
you
would
have
to
figure
out
one.
I
think
it
would
be
rather
tough
right,
but
even
if
you
went
like
the
I
framed
out,
just
fetching
the
roster
fetching,
the
entire
list
of
people
who
this
could
be
assigned
to
and
then
sending
them
out
in
addition
to
the
search
capability
would
be
quite
a
heavy
lift.
B
But
now
this
is
going
to
be
available
as
a
component
within
teams
where
you
can
say
that
I
want
a
people
picker.
I
want
to
develop
last
part
of
this
field
and
then
the
user
can,
you
know,
come
over
here.
They'll
see
some
sessions
as
they
start
typing
in
it's
going
to
be
search
an
auto
complete
over
there
and
then
you
can
assign
it
to
a
few
people
and
then
move
forward
so
again,
something
that
we
think
is
going
to
be
rather
powerful.
A
Users.
Teams
will
look
for
that
and
basically
automatically
make
this
into
a
people
picker.
It's
a
choice,
set
that
basically
levels
itself
up
into
being
a
people
picker
longer
term.
This
will
be
broadened
so
that
you
can
again
search
for
anything
search
for
products.
Search
for
you
know
anything
else,
and
that
data
set
will
basically
get
sent
to
your
bot.
Your
bot
gets
whatever
the
user
is
typing
it
filters,
and
then
it
responds.
So
we
can
start
to
do
server-side,
autocomplete,
so
that'll
be
something
you'll
start
to
see
throughout
this
year
as
well.
B
B
A
Yeah
yeah
so
yeah
I
can
go
and
take
over.
It
doesn't
really
matter
much
but
yeah,
so
a
bunch
of
resources
to
get
started.
These
are
always
kind
of
the
same.
A
lot
of
great
questions
in
the
chat
about
when
are
things
coming
road
map
and
things
so
aka.ms
ac
roadmap
is
your
best
place
to
check
that
out.
It's
like
one
click
submission.
Look
at
the
features
on
our
roadmap.
Tell
us
you
need
it
that
gets
back
to
us
and
that
helps
us
prioritize
or
just
kind
of
look
at
the
road
map.
A
I'll
just
switch
it
over
to
there's
a
bunch
of
other
great
m365
developer.
Community
calls
learn
more
about
the
graph
there's
one
dedicated
to
teams
where
I'm
sure
they'll
be
talking
about
a
lot
of
this
stuff
and
all
I'll
say
is
next
month
in
exactly
one
month
march.
11Th
at
9
00
am
we'll
be
doing
the
next
adaptive
cards
community
call.
F
G
B
Yeah,
that's
a
very
good
question.
So
typically
you
know.
When
you're
in
teams
you
will
operate
under
a
particular
scope:
you're
either
talking
to
your
bot
in
a
one-on-one
scope
or
if
you
are
in
the
context
of
a
team
or
channel.
You
are
talking
to
those
people
who
are
also
within
that
team
and
channel.
So
the
scope
of
who
you
can
search
for
is
going
to
vary
between
those
scopes
in
a
one-on-one
board.
We
allow
you
to
search
for
the
entire
tenant.
B
Basically,
all
the
users
that
you
can
search
for
within
a
team
or
a
channel
scope.
It
will
only
be
limited
to
to
those
particular
people
who
are
a
part
of
the
team
or
the
channel,
because
you
don't
want
anyone
who
doesn't
have
access
to
be
able
to
physically
see
the
card
to
be
able
to
actually
be
mentioned
or
be
somewhat
brought
into
that
conversation,
we're
looking
at
ways
at
creative
ways
and
how
we
can
address
that.
But
right
now,
that's
that's
the
design
yeah.
Does
that
mean
the.
A
One
thing
the
specific
schema,
the
one,
the
one
scope
that
we
have
is
that
current
context.
So
if
the
card
is
in
a
group
chat,
for
example,
in
teams
or
some
other
way
and
say
outlook,
you
basically
just
add
this
query
parameter.
So
if
you
just
do
users,
that's
the
full
user
directory,
it'll
search
for
all
the
people.
A
F
A
B
B
B
B
B
All
of
these
latest
by
build
will
either
be
in
depth,
review
or
generally
available.
So
so
that's
the
timeline
that
we're
setting
for
for
up
for
ourselves
that
by
build
generally
available,
which
I
think
we
can
hit.
But
you
know
if
there
are
like
issues
and
like
anything
slip,
then
you
know
at
least
we'll
be
in
that
preview.
A
A
I
think
he
means
the
dynamic
choice
set,
and
that
is
the
case
yeah.
So
the
bot
would
get
like
here's.
What
the
user
has
typed
there's.
You
would
know
what
input
they
in
are
they
searching
for
products
or
whatever,
and
then
you
would
return
the
array
of
data,
the
choices,
really
it's
the
array
of
choices
that
would
be
displayed
in
the
choice
set.
So
you
asked
there's
specifically
about
a
template
spec,
so
you
basically
right
now
you
can
only
return
the
title
and
the
value.
A
A
The
full
customization
of
that,
like,
let's
say,
you're
searching
for
products,
and
you
also
want
a
little
image
of
the
product
where
you
really
want
to
templatize
the
choice
set.
That
is
on
our
backlog.
It
requires
a
couple
of
other
lead
work.
It's
definitely
something
I
fully
imagine
us
to
get
to,
but
that
won't
be
for
a
little
while
so
probably
not
until
next
year,
where
you
would
fully
be
able
to
customize
the
choice
set.
A
C
B
C
A
A
H
A
A
Yeah,
I
will
I'll
send
a
link
to
at
least
his
tweet,
because
that's
the
first
thing
that
came
up
on
my
search
but
yeah.
We
actually
had
hugo
on
the
call
a
couple
months
ago,
demoing
the
sharepoint
web
part
rendering
adaptive
cards,
so
I'm
pretty
sure
it's
possible.
He
did
mention.
There's
there
was
one
he
had
to
make
a
standard
one
and
then
a
react
one
because
of
working
around
something.
I
remember
he
had
two
different
versions
of
them,
but
actually
I
think
this
links
to
his
his
github
as
well.
A
A
B
So
that
I
believe
you're
referring
to
the
delete
card
option
that
you
saw
under
overflow
menu
that
was
just
for
mock
purposes.
That's
not
a
user
choice,
but
you
could
create
that
because
there
are
bot
framework.
Sdk
allows
you
for
the
ability
to
delete
messages
or
edit
messages.
So
you
could
create
like
an
option,
a
button
that
says
delete
card,
but
that's
not
something
that
we
would
support
out
of
the
box.
D
B
D
F
D
B
G
I
was
trying
to
explore
if
there
is
possibility
to
change
or
rather
use
the
windows
resource
rather
to
have
some
wpf
native
styling
on
the
adaptive
card
controls
like
having
some
kind
of
gradient
on
the
adaptive
card
grid
or
some
kind
of
styling
native
wpa
styling
on
the
buttons.
So
I
I
found
there
is
a
way
to
have
some
native
styling
on
the
microsoft
site
that
is
called
native
styling
on
netwp.
G
A
Yeah
thanks
for
that
question,
so
yeah
I
did
just
pull
up
our
docs.
It
looks
like
you
found
them
all
if
you're
seeing
an
issue
or
if
you're
able
to
kind
of
send
us
the
the
the
xaml
you're
using
or
so
I
just
put
a
link
in
the
chat
to
our
github
issues,
if
possible.
If
you
could
just
file
an
issue
with
here,
you
know
here's
what
I
tried.
Here's
the
styles
I
was
using.
A
A
B
D
Yeah,
thank
you.
I
I
just
chat
like
a
clarifier
because,
like
what
I'm
doing
is
my
processes
of
running
a
power
automatic,
that's
creating
the
adaptive
card,
which
then
the
blog
post
is
I'm
just
trying
to
make
sure
if,
like,
if
that's
still
going
to
work
or
if
I
just
need
to
write
that
into
the
json
into
the
adaptive
card,.
B
D
B
A
E
E
G
E
B
A
E
A
A
Yeah
yeah
it'll
it'll
be
most
likely
in
like
our
we
right
now.
We
have
a
pretty
strict
policy.
You
know
we,
we
have
a
bunch
of
sdks.
We
actually
have
more
sdks
than
we
have
developers,
so
we
we
have
to
get
them
in
all
of
them
to
basically
do
a
release,
but
teams
only
relies
on
three
of
them
native
android,
native
ios
and
javascript,
so
we
will
likely
have
them
in
those
three.
A
But
if
you
rely
on
like.net
wpf,
which
we
just
got
a
question
on,
we're
probably
gonna
have
to
start
staging
out
some
of
those
just
to
help
us
scale
and
get
some
things
out
ahead.
But
we
also
are
very
aware
that
fragmentation
is
a
thing
and
we
we
already
are
struggling
keeping
everyone
up
on
the
latest
version
and
that
creates
problems
downstream
for
everyone.
So
it's
a
balancing
act
that
we'll
we'll
keep
doing
our
best.
A
Well,
we're
down
to
the
final
minutes.
I
appreciate
the
awesome
discussion
at
geosphere
thanks
a
ton
for
coming
in
this
has
been
such
a
hot
topic.
Every
time
I
have
to
say,
stay
tuned,
stay
tuned,
stay
tuned,
we'll
we'll
get
teams
on.
We
might
have
a
javascript
back
in
march
to
show
some
more
of
this
stuff,
we'll
kind
of
see
how
we're
doing.
If
anyone
would
like
to
talk
about
what
they're
doing
on
these
community
calls
feel
free
to
reach.
Out
that
workshop,
I
saw
I
got
a
couple.