►
Description
SharePoint PnP Community - SPFx & JS SIG call on August 26. Demo on Getting started on building Microsoft Viva Connection adaptive card components using SharePoint Framework and 3 PnP SPFx web part samples delivered! New version of SharePoint Framework v1.13 - Beta.17 out today! Released this week – React Controls v2.9.0 (SPFx v1.11), v3.3.0 (SPFx v1.12.1), PnPjs Client-Side Libraries v2.8.0. Viva Connections public developer preview! Join for first weekly Microsoft 365 platform community call on Tuesday, August 31st, 8:00 AM PT. The host of this call is Patrick Rodgers (Microsoft) | @mediocrebowler. Q&A takes place in chat throughout the call.
Learn more:
• See the full blog post for this call at: https://aka.ms/m365pnp/community/blog
• Download invite for bi-weekly SharePoint Framework call at: https://aka.ms/spdev-spfx-call
• Learn more about the Microsoft 365 Patterns and Practices community at: http://aka.ms/m365pnp
• Visit the Microsoft 365 Patterns and Practices community YouTube channel: https://aka.ms/m365pnp-videos
A
Hello
and
welcome
to
the
sharepoint
framework
and
javascript
special
interest
group
by
weekly
sync.
It
is
august
26th,
I'm
your
host
patrick
rogers,
for
this
call
and
we've
got
a
great
call
for
you
today,
as
always
with
our
agenda,
so
latest
updates
on
sharepoint
framework
patterns
and
practices
updates
across
the
program,
new
community
samples
picture
time,
and
then
demos
by
me.
So
if
you
don't
enjoy
listening
to
me,
you've
got
a
lot
of
me
to
listen
to
today
and
we'll
also
probably
have
maybe
a
surprise
demo
at
the
end
there.
A
If
you
stick
around
for
the
end
of
course,
we
always
like
to
talk
about
opportunities
to
participate
in
pnp,
and
these
calls
and
the
program
all
up
so
first
off
always
encourage
everybody
out
there
to
demo
demo
demo.
I
know
you're
all
working
on
great
stuff
for
your
companies
and
for
your
customers
and
we'd
love
to
have
you
demo
that,
on
the
call
sharepoint
framework
web
parts,
application
customizers,
I
know
folks,
are
starting
to
get
into
some
of
the
ace
card
development,
which
is
what
I'll
actually
be
talking
about.
A
The
demo
later
would
love
to
start
seeing
folks
doing
more
demos
around
that
really
exciting
new
things.
You
can
do
there
as
well.
You
can
always
contribute
on
github
by
reporting
issues,
submitting
pull
requests
and
helping
with
issues
and
questions
other
folks
might
have
and
as
well.
We
always
appreciate
your
feedback.
How
are
these
calls
going?
How
is
our
documentations?
A
Where
else
can
we
help
and
positive
feedback
is
of
course
okay
too?
It
helps
us
do
a
little
bit
more
of
the
things
you
like
next
up
is
our
page,
oh
links,
so
the
first
up
is
the
developer
videos.
These
are
going
to
be
topic,
focused
videos
on
how
to
achieve
certain
things,
such
as
authentication
how
to
build
certain
kinds
of
web
parts,
very
specific
kind
of
tasks.
A
There's
series
there
on
powershell
all
kinds
of
great
content
there
for
learning
certainly
check
that
out
as
well,
then
the
community
videos,
those
are
going
to
be
the
recordings
of
all
of
our
community
calls
such
as
this
one.
The
other
special
interest
group
call
our
monthly
community
calls
as
well
as
other
calls
throughout
the
month.
You
can
always
catch
up
on
missed
episodes
there
as
well
bunches
of
open
source
organizations
all
open
to
your
participation,
so
sharepoint
pnp
office,
dev
and
microsoft
graph.
A
All
four
of
those
really
welcome
and
encourage
you
to
jump
in
participate
report
issues
submit
pull
requests,
help
out
if
you're
interested
in
any
of
the
projects
across
those
organizations
they're
all
pretty
open
to
having
you
help
out,
join
in
as
well
sample
galleries.
We've
got
team
samples,
spfx
web
parts,
power
platform,
samples,
spfx
extensions
and
list
formatting
samples
all
available
for
you,
a
great
resource.
A
If
you're
looking
to
get
started
or
looking,
you
got
a
new
project,
you
want
to
see
how
others
maybe
have
solved
a
similar
problem,
go
check
those
out
and
then
finally,
that's
a
lot
of
links
to
remember,
but
ak
dot,
msl,
m365
pnp
will
get
you
all
the
links
and
all
the
content
you
might
need
about
the
program
and
about
all
the
resources
I
mentioned
previously.
So
you
can
find
those
very
easily
aka
dot.
Ms
m
365
pnp.
A
A
It's
not,
it
is
the
microsoft
365
platform
community
call
31st
of
august
at
8
a.m,
pacific
time.
So
that's
a
new
weekly
call
with
microsoft,
presenters
and
the
latest
around
the
360
microsoft
365
platform.
So
that's
going
to
be
wall,
deck
and
I'll
shoot
myself.
Reeci
and
andrew
introduced.
The
microsoft
graph.net
sdk
v4
excited
to
hear
about
more
about
that
and
then
will
show
getting
started
with
microsoft
teams.
Ui
library,
that
is
the
most
awesome
name
for
a
presenter
ever
and
so
excited
to
see.
A
B
Correct
so
basically,
what
we're
doing
is
that
we're
combining
sharepoint,
microsoft
themes
and
the
microsoft
craft
calls
to
this
single
weekly,
recurrent
meeting
most
likely
office.
Adding
call
is
going
to
be
merged
on
that
as
well,
and
that
is
the
first
one
next
tuesday
and
we'll
start
doing
that
on
a
weekly
basis
with
microsoft,
btso
product
group,
presenters
cloud
advocates
and
all
of
that
on
every
single
tuesday
8
a.m.
Pacific
time
see
you
there
awesome
and
is
this
now
sharing
is
caring
with
david.
I
think
it
is
we're
kissing
the
same,
slides.
D
All
right,
it
looks
like
it
and
everybody
make
sure
you
attend
that
tuesday
call,
because
you
can
tell
your
grandkids,
you
were
there.
The
inaugural
event
sharing
is
caring,
though,
is
about
including
you
in
the
community,
giving
you
an
opportunity
to
contribute
back
to
use
the
resources
that
are
available
to
you.
We
understand
that
there
are
hurdles
that
might
be
preventing
you
from
not
only
using
but
contributing
back,
such
as.
How
do
you
navigate
github?
What
about
those
terms
like
forking
and
raw
and
pull
requests?
What
do
they
mean?
How
do
you
navigate
them?
D
We
are
here
to
help
you.
These
sessions
are
live,
hands-on,
inclusive,
safe
space
opportunities.
We
do
not
record
them
you're
going
to
collaborate
with
members
of
the
pnp
team
to
see
how
you
can
contribute
back
to
the
community,
so
a
number
of
sessions
are
available.
We
also
have
a
whole
collection
of
amas
coming
up
in
september.
As
you
can
see
recognition
program,
script,
samples,
power
platform.
D
Those
have
been
a
great
opportunity
to
interact
with
those
in
the
community
and
the
pnp
initiative,
so
take
advantage
of
those,
and
we
have
lots
coming
up
for
the
fall
for
new
sessions
now,
once
you
have
contributed,
we
love
to
celebrate
and
recognize
you.
So
don't
forget.
There
is
the
recognition
program
now
that
is
available.
This
is
powered
by
credly,
the
same
credly
that
handles
the
badges
for
your
microsoft
certification.
So
we're
going
to
continue
to
come
out
with
new
badges.
D
We
were
just
working
on
some
yesterday,
thanks
for
samples,
blog
writing
at
tech
community
with
luisa
who
will
love
to
help
you
do
that,
we're
going
to
recognize
all
the
amazing
contributions
that
you're
making
and
the
hard
work
that
you're
putting
in
and
provide
you.
This
formal
fun
way
to
recognize
the
the
work
you're
doing
and
we're
also
going
to
have
some
fun
campaigns
coming
up.
D
Hacktoberfest
is
coming
up,
there's
going
to
be
some
fun,
parker
related
limited
edition,
badges
and,
of
course,
we're
going
to
continue
to
do
this
to
keep
you
involved
and
celebrate
your
work
so
aka
ms
m365
pnp,
dash
recognition.
We
need
you
to
opt
in,
so
we
can
connect
your
profile
to
your
credly
account
and
we
ask
you
to
please
register.
Thank
you
very
much,
patrick
back
to
you.
B
Updates
with
vasa
thank
you
patrick
on
that
one.
So
just
a
reminder
for
everybody
we're
pushing
out
the
new
sharepoint
store
experience,
and
this
is
for
celebrating
and
promoting
our
partner
offerings
in
the
sharepoint
store
or
in
the
app
source
and
we're
gonna
do
a
lot
of
a
lot
of
investments
in
here
and
also
an
app
source.
So
you
can
already
today
in
a
sharepoint
online,
it's
100
percent
rolled
out.
B
If
you
go
and
add
an
app
experience,
the
experience
is
completely
modernized
and
you
will
see
further
investments
in
this
area
in
the
future,
and
there
is
a
nice
blog
post
in
akmsp
block
from
last
week
or
week
before
that
on
the
the
movement
of
sharepoint
framework.
So
1.13
is
the
in
the
beta
status.
There
is
a
new
version
of
1.13
out.
We
pushed
out
the
version.
B
B
Most
likely
is
going
to
happen
within
this
half
and
in
autumn
timeframe
as
well,
and
we're
going
to
keep
on
pushing
in
here
and
we're
also
really
focusing
on
the
team's
improvements
so
making
that
better,
a
lot
of
tooling
updates
and
improvements
on
the
framework
as
well.
So
basically,
what
we
want
to
do
is
to
make
sure
that,
even
though
you
wouldn't
be
implementing
for
viva
or
in
the
teams,
you
will
get
improvements
on
the
on
the
experience.
So
a
lot
of
vision
updates.
All
of
that's.
B
E
Cool
thanks
so
version
2.8
released
just
a
little
over
a
week
ago.
We
got
a
lot
of
new
graph
features
and
we
got
some
sharepoint
features
for
adding
image
field.
We
also
got
a
lot
of
documentation,
updates
so
definitely
check
out
the
release.
Notes
on
2.8.0
also
just
wanted
to
quick
update.
The
v3
development
is
well
underway,
we're
making
some
huge
progress.
E
Anybody
who
watches
the
library
can
see
patrick
and
I
furiously
issuing
poll
requests
for
v3,
so
definitely
check
out
that
branch
see
what
we're
doing
and
hopefully,
we'll
have
something
for
you
all
to
check
out
soon,
as
usual,
follow
us
on
twitter,
m365,
pmpjs
and
be
sure
to
put
all
your
feedback
in
the
issues
list.
If
you
have
any
questions,
problems
need
help,
need
assistance,
put
those
in
that
issue
list
and
we
will
be
happy
to
try
to
help
you
and
that's
all
we
have
for
today.
E
A
Thank
you,
there's
an
airplane
dropping
a
bomb
on
the,
but
it
is
escalated.
It's
on
all
right,
so
cli
for
microsoft,
365
new
preview,
v313
with
retrieving
apps
installed
on
the
site,
removing
application
permissions
from
a
site,
adding
users
to
sharepoint
groups
and
retrieving
microsoft.
Planner
plans
you'd
always
try.
The
latest
beta
npm
install
dash
g
at
pnp,
cll,
microsoft
365
at
next,
and
then
you
can
always
run
it
in
docker.
They've
packaged
this
up
very
nicely
so
docker.
A
So
you
can
run
the
docker
package
very
easily
with
all
the
dependencies
and
everything
ready
to
go.
You
can
also
try
out
the
preview
of
v4,
which
is
coming
up
for
later
this
year.
Npm
install
g
dash
g,
all
those
same
things
at
four
we'll
get
you
the
latest
v4
preview
same
for
the
docker
there
and
all
the
information
ak
dot.
Ms
slash
cli-m365
will
get
you
all
the
documentation,
links
and
understanding
there
for
the
cli
really
an
awesome
tool
to
use
in
your
development.
C
C
There
are
two
new
controls,
live
persona
and
list
item
comments
for
the
live
persona.
Please
read
the
disclaimer
in
the
documentation
because
we
are
using
kind
of
not
official
apis
and
possibilities
from
sharepoint.
So
at
some
point
it
might
break
so
be
aware
of
that
and
note
here
that
we
will
not
release
major
versions
for
v2
anymore,
it's
time
to
upgrade
your
solutions
from
spfx111
to
112.
C
A
Awesome,
thank
you
alex
for
those
updates
and
sorry
about
that.
I
missed
you
had
joined
the
call
so
appreciate
that
and
then
modern
search
updates,
I'll
pause
for
a
second
in
case
anybody's
here
to
speak
to
that
and
then
I'll
start
talking
about
so
building
modern
search
experiences.
It's
a
great
way
to
take
this
set
of
web
parts
and
build
out
search
portals
for
your
users.
It
uses
based
on
spf
x
and
a
lot
of
out-of-the-box
styling,
so
it
looks
very
built
in
it's
got
a
lot
of
flexibility.
A
A
lot
of
power
built
into
it
august
release
delayed
due
to
a
lack
of
resources
and
time,
but
the
v430
july
release
was
out
and
had
a
proper
fix
for
custom
helpers
and
web
components
across
web
parts.
Persona
card
fix,
as
well
as
dutch
translation
and
then
the
321-0
july
release
and
just
a
reminder.
The
v3
branch
is
really
in
maintenance
mode.
A
F
C
F
Using
for
sharepoint
framework
for
a
while
and
you're
just
looking
for
inspiration,
there's
samples
for
web
parts
and
extensions
and
you
can
leverage
any
of
those
samples
you
can
actually
use
them
for
patterns
or
you
could
use
them
for
a
full-on
solution.
This
is
the
updates
for
the
last
two
weeks.
There
is
no
new
updates
on
the
extension
side,
however,
there
is
a
pull
request
from
kunsan
gandhi
that
I
didn't
get
to
process
yet
so
I
apologize
for
that.
But
on
the
web
part
side
we
have
a
new
web
part
called
my
one
drive.
F
It's
a
one,
spf
x,
12
one
by
siddharth
vagisia,
but
I
I'm
sure
I'm
mispronouncing
that
it's
a
simple
web
part
that
displays
the
the
current
user's
onedrive
and
you
would
actually
use
this
web
part.
Let's
say
on
an
intranet
home
page
and
then
you
can
show
a
quick
reference
to
the
person's
onedrive.
The
teams
membership
updater,
which
is
something
we've
demoed
a
while
ago
by
nick
brown
nick,
has
added
support
for
populating
private
channels
inside
of
teams,
support
for
page
list
of
teams
from
graph
and
sorting
as
well.
F
And
finally,
we
have
a
new.
My
events
web
part
by
chandani
prajapati,
this
new
web
part,
will
actually
provide
the
users
outlook.
Events
with
some
advanced
features,
it's
very
cool
and
by
the
way
we
have
reached
a
new
milestone.
We
have
now
passed
over
2000
pull
requests,
which
is
amazing
right
if
you
think
about
it.
So
thank
you,
everyone
for
being
so
awesome.
F
A
I'll,
just
second
that
from
hugo
really
amazing-
this
started
I
think
a
year
ago
or
around
that
and
it's
just
grown
so
quick
or
maybe
a
little
longer
than
that,
but
so
quickly
and
it's
amazing
to
see
everybody
in
the
community
helping
out
here
and
participating
and
contributing
to
the
samples
it's
such
a
valuable
community
resource.
So
thank
you
to
everybody.
Great
work,
hugo
great
work,
everybody
involved
in
this
and
keep
it
up
optional
picture
time.
B
B
Okay,
I
think
we're
maxed
out,
so
everybody,
let's
do
some
handwaving
we're
going
to
do
a
keep
animation
out
of
this
as
well
thanks
everybody,
thanks
for
being
here
hopefully
by
next
by
end
of
this
year,
we'll
actually
meet
physically
in
some
other
conferences
and
seems
pretty
positive
in
some
areas
we'll
see.
But
thank
you
everybody.
Thank
you
for
being
part
of
this,
we'll
post
out
a
gif
animation
later
this
today
and
then
it's
going
to
be
part
of
the
blog
post
as
well
when
we
publish
the
summary
of
the
call.
A
Bye-Bye
okie
dokie,
so
that
is
always
a
lot
of
fun,
but
now
on
to
demos,
which
today
is
me,
followed
by
a
mystery
demo,
so
there
is
some
drama
to
keep
you
sticking
around,
so
first
a
marketing
slide.
So
what
we're
going
to
talk
about
today
is
some
viva
connections.
Dev,
you
saw,
I
believe
it
was
last
time,
julie,
turner,
demoed,
some
great
samples.
A
She
built
she
and
derek,
I
believe-
and
so
that
was
very
cool,
but
we
want
to
talk
about
that
a
little
bit
more
because
viva
connections,
ace
development,
is
really
kind
of
the
next
step
or
next
piece
of
the
evolution
for
sharepoint
framework.
It's
not
a
replacement
for
it's
rather
an
extension
of
sharepoint
framework,
another
part
of
sharepoint
framework.
You
can
take
advantage
of
to
get
some
customization
into
the
viva
connections.
Dashboard!
A
That's
coming
up,
so
this
is
a
marketing
slide.
It's
got
lots
of
stuff
on
it,
so
these
card
views
so
you've
got
kind
of
the
card
view,
which
are
these
little
tiles
on
the
screen
here.
So
imagine
this
is
on
a
mobile
device.
This
would
also
show
up
in
teams.
It
also
shows
up
in
sharepoint.
Eventually
you
can
have
a
dynamic
title
and
icon.
You
can
kind
of
change
these
things
around.
You
can
change
the
text.
You
can
have
buttons
on
these
cards.
A
A
You
can
have
multiple
different
kinds
of
views
here,
so,
whereas
the
card
view
that
first
piece
is
very
fixed,
there's
three
right
now,
there's
three
fixed
layouts:
you
can
use
in
those
cards
and
for
the
quick
views,
which
is
that
center
thing
those
are
completely
sculpted
by
adaptive
cards,
so
you
have
complete
control
over
what
goes
on
there.
So
you
can
have
simple
text
display.
A
You
can
have
images
all
sorts
of
other
stuff
and
then
finally,
the
sort
of
third
part
of
this
is
then
linking
out
to
another
app
could
be
a
teams.
App
could
be
a
sas
app
lots
of
options.
There
link
right
to
a
team's
channel
things
like
that,
so
lots
of
different
capabilities
there.
But
let's
talk
about
how
should
I
the
developer,
think
about
aces
so
aces
are
really
the
container
control.
A
A
It
provides
a
context,
so
very
much
like
spfx
you
have
at
this.context
was
which
tells
you
where
you
are
in
the
world
and
then
it's
got
all
the
lifecycle
events
you're
familiar
with
and
then
some
a
few
differences
from
spf
x,
but
generally
speaking,
it
contains
the
life
cycle.
Events
for
you
and
then
it
hosts
manages
controls
the
various
views
so
pick
how
you
like
to
describe
that.
A
But
it
is
the
the
host
of
the
views
or
the
view
controller
lots
of
obviously
different
view
models
out
there
in
the
world,
but
it
hosts
the
views,
the
views
live
inside
the
ace
and
then
about
those
views.
You
can
have
pretty
much.
I
think
as
many
views
as
you
want,
but
there's
two
types.
The
first
is
card
view
and
those
are
those
little
tiles,
there's
three
fixed
layouts
and
two
sizes.
The
sizes
are
medium
and
large.
A
One
card
view
is
required
per
ace,
but
you
could
have
multiple.
You
can
have
any
number
of
those
things
so,
but
one
is
required
and
then
those
card
views
can
act
as
a
link.
They
can
have
one
or
two
buttons.
You
need
to
have
a
large
card
size
for
the
two
buttons
we'll
talk
about
that
all
a
little
bit
more
when
we
get
into
the
code
and
then
finally,
the
quick
view
cards
have
no
defined
layout,
so
you
completely
control
and
define
those
layouts
using
the
adaptive
card
schema
or
syntax.
A
However,
you
want
to
describe
those
can
have
images,
form,
elements,
text
buttons
and
more
pretty
much.
In
my
testing,
everything
seemed
to
mostly
work
from
adaptive
cards,
dot
io
that
I
tried
in
there.
So
really
neat
really
flexible,
very
easy
to
build
stuff
out
and
you'll
see.
I
was
able
to
build
out
some
fairly
ugly
because
I
built
them,
but
complicated
interfaces
pretty
easily
and
then
you're
not
required
to
have
a
quick
view
card.
A
A
So
that's
enough
talking,
let's
get
to
some
code.
The
first
thing
I
want
to
show
you.
I've
got
three
samples
here,
and
these
are
all
now
publicly
available,
but
the
first
one
is
this
basic
card
deep
link
here-
and
this
is
really
the
three
samples
I
want
to
show
today-
kind
of
start,
very
basic
and
then
work
up
to
more
complex
and
the
hope
is-
and
I'm
of
course
interested
in
the
community's
feedback
on
this.
A
But
the
hope
is
that,
with
these
three
samples
we've
covered
not
exactly
the
the
specific
task
you're
gonna
do
but
the
methods
you
might
do
generally
to
solve
these
tasks.
So
the
first
kind
of
card
is
a
basic,
deep
link
card
we've,
given
it
a
couple
of
properties
here
with
the
url.
That's
a
teams,
deep
link,
it
turns
out
because
it
goes
to
a
channel
and
we'll
hit
preview
there,
and
if
we
click
on
that
we're
gonna
open
up
our
teams
link.
A
This
would
actually
open
up
our
team's
channel
and
we're
gonna
use
the
web
app.
Instead,
because
I'm
on
my
testing
tenant-
and
we
all
know
how
fun
it
is
to
try
and
switch
tenants
mid
demo.
So,
but
this
is
a
test
channel
with
some
some
great
conversations
I've
had
here
with
myself
over
time,
but
that's
it.
That's
a
basic,
deep
link
card.
That's
what
it
does.
I've
got
a
card
on
the
screen.
I
can
click
it
and
it
links
somewhere.
So
how
did
we
build
that?
And
that's
this
code
here?
A
So
what
we
did
is
we've
got
our
adaptive
card
extension
and
these
are
scaffold
exactly
like
sharepoint
framework.
You
start
with
the
yeoman
generator.
You
pick
adaptive
card
extension
so,
where
you
have
like
web
part
application
customizer
one
of
the
new
choices
is
adaptive
card
extension
and
you
get
this
all
scaffolded
out.
Your
main
class
is
this
ace
class
and
that
inherits
here
from
the
base
adaptive
card
extension
class
and
it
takes
some
props
and
state
things.
A
So
that's
very
react
like,
but
again,
this
is
not
backed
by
react
in
any
way
that
you
will
ever
address
or
deal
with
directly,
but
it's
very
react
like
so
it
feels
very
familiar.
It's
very
easy
to
build
in
this
and
it's
also
very
very
much
like
a
sharepoint
framework.
So
it's
going
to
feel
very
familiar
if
you've
worked
in
sharepoint
framework
and
you
start
to
pick
up
aces,
I
think
you're
going
to
get
started
very
quickly,
but
there's
some
interesting
differences.
A
First
off
you'll
see,
we've
got
an
on
init
that
should
be
familiar
to
everybody.
We've
got
to
set
our
initial
state
here,
that's
very
react-like,
a
very
common
thing
to
do
there,
but
there's
this
new
thing
card,
navigator
and
so
card
navigator
is
sort
of
your
index
of
all
the
views
that
can
exist
inside
your
ace,
and
you
have
to
set
these
things
up
kind
of
at
the
beginning
here
and
they
have
a
string
id
and
this
sort
of
factory
function
here,
and
one
important
thing
to
note
is
when
I
register
this
card.
A
It's
gonna
invoke
my
factory
function,
which
can
have
other
logic
in
it
right.
I
could
do
more
than
just
say
new,
but
once
that's
invoked,
it's
gonna
hold
on
to
that
card
object
that
got
created.
It's
not
going
to
reinvoke
this
every
time
the
card
is
shown
so
something
to
keep
in
mind
there
for
how
maybe
you
structure
your
solutions
and
perhaps
how
you
might
build
some
things.
There's
a
property
down
here
render
card
this
tells
it
what
card
to
render
we've
just.
This
is
our
very
simple
example.
A
A
If
we
look
at
the
property
pane,
this
is
where
we've
gone
in
and
added
our
properties
for
link
url
and
teams
link
again
very
sharepoint
framework
like,
but
you
know
just
want
to
show
kind
of
do
the
same
things
here,
set
our
settings
up
and
then,
in
our
actual
card
view
card
views
as
well
as
quick
views.
But
this
solution
has
no
quick
views.
A
But
the
data
here
is
defined,
and
so
I'll
kind
of
dwell
on
this
here
and
not
in
the
next
three
demos.
But
the
way
to
think
about
these
views
and
this
data
property
is
you
have
an
adaptive
card,
sort
of
syntax
or
schema,
and
then
you
have
this
data,
and
so
you've
got
your
model,
which
is
this
data
and
the
view
which
is
the
adaptive
card
and
those
get
meshed
together
to
create
what's
on
the
screen,
so
this
data
really
think
of
this
as
producing
the
model.
A
You
can
do
a
couple
different
things
here,
in
this
case
very
simple
example:
I've
just
showed
you
can
have
some
super
simple
defaults
like
if
we
don't
have
a
link
defined,
we're
just
going
to
send
them
to
the
best
search
engine
on
earth,
bing
and
otherwise
we're
just
going
to
return
our
properties,
the
teams
link
and
the
target
url,
because
we've
got
our
our
url
up
there
from
the
properties
and
that's
it.
We've
built
a
card
view
that
we
can
set
the
link
for,
and
that
will
link
us
out
to
other
stuff.
A
So
if
I
click
on
that
again,
that's
what
we
just
saw
so
we'll
use
our
web
app
and
again,
my
great
channel
of
me
talking
to
myself,
which
we'll
leave
open
for
future
demos.
So
give
me
one.
Second,
I'm
going
to
control
c
out
of
this
and
I'm
going
to
get
the
server
started
for
my
next
one,
and
so
we'll
go
back
into
edit
mode
here
and
we'll
take
this
guy
off
the
screen,
and
we
will
wait
a
second
for
our
server
to
get
going
for
our
second
example.
A
Our
second
example
is
looking
to
cover
this
idea
of.
I
need
to
get
some
information
and
show
it
to
the
user
in
a
carousel
pattern.
Right,
we've
all
written
carousels,
probably
a
thousand
times
in
our
career,
so
I've
written
another
one
here
and
just
want
to
kind
of
show
that
off,
because
I
think
it's
another
very
common
scenario.
A
I've
called
this
one
company
news,
but
you
can
think
about
this
being
images
or
articles
or
or
emergency
updates,
or
company
updates,
or
any
kind
of
pattern
where
you
want
to
page
through
this
stuff,
while
we're
waiting
for
the
server
to
spin
up.
Let
me
see
what,
if
there's
any
questions
here.
If
it's
not
react,
what
is
it
so?
The
aces
are
not
react.
A
They
are
based
on
adaptive
cards,
so
the
adaptive
cards
in
the
background
could
be
rendered
with
react.
They
could
be
rendered
with
react
native.
They
could
be
rendered
with
something
else.
That's
the
point
of
the
adaptive
cards
is
they're
gonna,
give
you
that
flexibility,
or
rather
us
that
flexibility
to
take
your
work
and
render
it
across
many
different
devices
as
natively
as
we
possibly
can.
A
Somebody
want
to
learn
about
technical
underpinnings.
We
could
do
a
session
on
that,
for
sure,
can
we
have
more
than
three
card
templates
for
viva
card
so
right
now
the
card
views
those
tile
views
are
restricted
to
three
layouts
right
now:
post
ga
that
may
change,
but
currently
that's
what
is
available
but
again
for
the
quick
views.
You
can
do
pretty
much
anything
you
want
so
go
ahead
and
refresh
this.
A
I
think
we
should
be
good
to
go
here
with
our
company
news
and
there's
our
company
news,
and
so
this
loads
on
up
and
I've
already
one
thing
I've
got
to
do
here
is
again:
you
need
to
set
the
card
size
to
large
to
get
the
buttons
down
there
correctly,
we'll
go
into
preview,
and
so
this
is
my
article
title.
I
can
click
on
this.
I
get
my
image.
I
get
my
article
text
which
you
can
see
here.
A
I
did
learn
right
now
in
adaptive
cards
you
can't
parse
html,
so
this
is
just
the
raw
html
from
my
input
there
and
I'm
showing
you
can
show
the
rest
of
this
stuff
in
this
view,
but
you
can
see
like
here's.
My
image,
here's
my
image,
here's
my
title:
here's
my
title:
here's
my
little
svg
icon,
here's
my
little
svg
icon!
Those
are
all
being
pulled
from
the
same
state,
so
you're
just
presenting
the
information
from
the
aces
state
in
these
different
views,
and
I
added
some
functionality
here.
A
You
can
actually
like
this
article.
It's
going
to
go
back
and
actually
like
it
in
sharepoint,
we'll
look
at
that
here
in
a
second,
I
can
click
next
and
I
can
click
next.
I
think
we're
all
familiar
with
this
kind
of
thing,
but
this
example,
hopefully,
is
a
very
general
example
of
I
need
to
pull
some
content
and
I
need
to
display
that
to
folks
in
kind
of
this
carousel
scrolling
manner.
So
I
think
that
will
cover
a
lot
of
that.
But
how
did
we
write
that?
A
A
So
we've
got
our
extension
and
sorry.
I
was
looking
at
the
chat
for
a
second
we've
got
our
extension
here
again.
We
inherit
from
the
base
card
extension,
but
we've
got
a
lot
more
going
on.
In
this
example,
we've
got
a
card
view
and
we've
got
our
quick
view.
So
this
this
has
the
card
view,
and
it
has
that
quick
view.
So
the
card
view
is
the
part
that
had
the
previous
and
next
buttons.
The
quick
view
is
the
part
that
popped
up
and
showed
us
the
full
article.
A
So
in
our
on
init
same
sort
of
pattern
here
we
set
our
state.
We
register
our
views,
so
note:
there's
a
card
navigator
and
a
quick
view.
Navigator.
Those
are
separate
things
and
you
register
your
card
views
in
one
and
your
quick
views
in
the
other,
but
they
work
the
same.
So
just
note,
there
are
two
different
places
to
register
those
things,
and
then
I
there's
lots
of
different
techniques
to
do
this.
A
This
is
something
I
like
to
do
because
we
keep
our
contextual
this
and
all
our
variables
available,
but
I
set
a
timeout.
So
this
allows
us
to
to
tell
the
javascript
runtime
engine
hey
next
event:
loop
when
you
get
around
to
it,
do
this
stuff
for
me,
and
so
what
we're
doing
is
we're
getting
an
sp
instance.
This
is
actually
using
pnpjs,
but
the
point
isn't
using
pmpgs.
A
The
point
is
you
can
use
any
third-party
library
in
here
to
do
data
fetching
or
any
other
operation
you
want
to
do
and
all
the
bundling
works.
The
way
you
expect
all
the
inheritance
works.
The
way
you
expect
everything
works
exactly
the
way
you're
going
to
expect
it
to
do.
I
just
happen
to
have
used
pnpgs
here,
mostly
because
I
wanted
to
test
pmpjs
that
it
worked
in
aces
so
set
state
again
we're
setting
the
state
calling
set
state
with
our
updated
articles.
A
So
we've
gotten
our
articles
and
we're
gonna
set
our
state
there
and
we're
gonna
say
our
current
index
is
zero
up
here
our
index
was
negative
one.
Now
our
index
is
zero.
The
first
one
in
the
group
there.
The
rest
of
this
is
pretty
similar
to
what
we
saw
before
we're,
rendering
our
card
view
id
and
so
forth.
So,
let's
look
at
our
card
view
real
quick,
so
our
card
view
has
a
little
bit
more
going
on
in
the
data
here.
A
So
we've
got
if
if
we
have
less
than
zero
right,
so
if
our
article
index
is
at
negative
one,
we're
gonna
return
this
kind
of
loading
view.
So
this
is
just
returning
some
some
hard-coded
data
that
says
loading
and
it's
got
a
svg
icon,
just
as
a
string
in
here
and
so
forth,
and
then
we
do
return
the
selected
article
if
one
of
the
articles
is
selected
in
the
in
the
the
carousel
right.
A
So
this
is
the
current
one
that
I've
selected
and
then
we've
got
a
property
here
we
didn't
see
before,
but
this
is
card
buttons,
so
card
buttons.
You
can
return
one
or
two
buttons
or
undefined.
So
there's
no
other
choice
right.
You
can
run
one
button
or
two
buttons,
and
so
what
we
do
here
is
we
kind
of
build
up.
This
is
our
logic
here
to
say
you
know:
hey
do
we
need
previous?
Do
we
need
our
next
button
and
we
just
you
know,
put
those
buttons
into
this
array
and
return
them.
A
So
we're
returning
either
one
or
two
buttons,
depending
on
how
we
are
in
the
scrolling
through
our
articles
and
then
on
action.
So
on
action
is
our
event
handler.
So
event,
handlers
are
sort
of
auto
subscribe
to
this
on
action
event
or
on
action
method.
Rather,
so
you
don't
have
to
go
for
each
button,
add
and
on
click
and
so
forth.
Every
button
is
going
to
track
through
into
this
on
action
method
and
you
can
kind
of
differentiate
what
happened
by
giving
your
buttons
ids.
You
can
see
up
here.
A
I've
got
an
id
of
previous
and
and
next,
which
correspond
to
previous
and
next
and
all
we
do
is
set
the
state
in
here.
So
we're
going
next,
we're
just
adding
one
to
our
index
previous
subtracting
one
and
setting
state
very
much
like
react
is
gonna
reflow,
your
rendering
and
you're
to
get
your
updated
view.
So
this
is
this
is
showing
us
the
clicking
through
and
that's
the
actual
next
and
previous
happening
right.
So
I
click
previous.
A
A
You
saw
only
when
we
actually
click
on
and
select
those
things,
and
so
we
come
in
here
and
we're
gonna
set
another
timeout.
This
is
a
technique.
I
really
like
to
set
timeout
to
get
an
async
into
the
next
event
loop.
You
could
also
just
have
an
async
method.
You
call,
but
I
I
there's
some
things
here.
I
like.
A
I
think
this
makes
this
a
little
cleaner,
especially
in
you
know,
situations
like
this,
where
you
kind
of
want
to
have
these
variables
fall
through
and
things,
but
so
we're
going
to
get
an
sp
we'll
look
at
that
sp
code.
Very
briefly,
because
that's
not
the
point
of
the
demo,
but
so
we're
getting
our
article
contents
setting
that
item
content
and
then
we're
resetting
our
state
here.
So
a
couple
of
subtle
things
are
happening
here,
so
javascript
arrays
are
by
reference.
A
So
the
fact
I've
gotten
the
cons
or
I've
gotten
the
item
up
here.
Out
of
this
array.
I've
changed
that
item
and
I
reset
the
state
with
that
same
array.
That's
actually
going
to
reset
everything
that
item
in
that
array
is
updated
and
we've
reflowed
our
state
with
the
the
new
articles
there
so
and
then,
if
we
don't
have
any
content,
so
this
is
kind
of
another
sort
of
subtle
thing
here.
A
At
this
point,
so
we
can
show
people
the
title
primary
text
and
so
forth
and
then
once
the
contents
loaded,
this
set
state
will
be
called
and
we'll
reflow
and
it'll
show
the
content,
then
as
part
of
our
model.
So
that's
you
know
a
way
to
do
that
there
and
then
we've
got
an
on
action
here
again.
So
I'm
trying
to
look
back
up
here
at
some
of
the
questions
so
mark's
question
is
so
let
content
equal
item.
That's
actually.
Those
are
two
very
different
statements.
A
So
the
let
content
equal
item
is
actually
destructuring
item
into
content.
So
you
would
your
second
statement
to
be
equivalent
would
be
let
content
equal
item.
Dot
content
would
be
the
same,
equivalent
statement
there
and
well.
You
know
I
don't
know
we'll
see
about
writing
code
at
scale.
I
guess
so
setting
time
out
here,
we've
got
this.
A
Is
our
action
to
like
the
articles
and
we're
going
to
set
the
time
out
again
using
that
technique
and
then
doing
similar
operation
here
we're
going
to
get
our
articles
get
that
item
that's
selected
currently
and
then
we're
gonna.
If
it's
liked
we're
gonna
unlike
it,
and
if
it
is
not
liked
we're
gonna
like
it
and
then
we
reset
our
item
and
then
we
do
the
exact
same
operation
to
set
state
reflow
the
rendering
and
get
our
updated
javascript
shortcut
mark,
not
typescript
exclusive.
A
So
that's
a
javascript
thing
now,
and
so
the
other
piece
here
I
wanna
show
you
is
our
template
bounce
over
here
to
our
template,
so
adaptive
card
templates
are
created
via
json.
Adaptivecards.Io
is
a
fantastic
website.
They
have
tons
of
samples.
They've
got
the
full
schema
defined.
That's
how
I
learned
all
this
so
encourage
you
to
check
adaptivecards.io
out,
but
these
adaptive
cards
are
just
defined
with
json
and
I'm
not
going
to
go
through
every
little
part
of
this,
but
you
can
have
text
blocks
images.
A
Action
sets.
This
is
where
we're
actually
putting
our
button
in
here
to
do
the
liking
text,
block
content,
you
have
things
like
column
sets,
so
this
is,
you
can
set
up
tables
things
like
that,
and
then
you
can
have
a
set
of
actions
that
also
appear
at
the
bottom
of
the
screen.
So
this
is,
you
know
fairly.
In
my
view,
simple
adaptive
card
but
gives
us
that
nice
view
again
of
you
know
a
click
on
here
and
we
see
our
full
article
there
so
great.
A
A
I
wanted
to
show
you
as
well
this
one
real,
quick,
the
pmpgs
part.
You
can
see
this
in
the
sample.
I'm
not
gonna
dwell
on
this,
because
that's
not
the
point
of
this
demo,
but
what
I've
done
here
is
create
my
project
preset.
This
is
one
of
our
samples
as
part
of
our
guidance,
but
I've
also
extended
web
to
using
the
extend
factory
functionality
to
have
exactly
the
methods
I
need
so
they're
very
easy
and
clean
back
in
our
other
code
and
the
other
piece
of
the
pattern
here.
A
Is
this
get
sp?
So
in
our
ace
we
have
access
to
the
context.
This
is
just
like
sharepoint
framework.
It's
got
a
this
dot
context,
so
we
call
the
get
sp
in
the
ace
body
store
that
context
build
up
an
sp
and
then
we
actually
we'll
just
keep
using
that
same
sp,
and
we
can
call
this
get
sp
then,
in
our
views
where
we
do
not
have
access
to
the
context.
So
this
is
a
a
little
shortcut
for
the
pmpgs
stuff.
You
can
check
that
out
in
the
repository
again.
A
A
A
It
might
be
more
and
there's
a
couple
small
caveats
of
things
at
this
point
that
don't
work
exactly
right
yet
in
aces.
So
how
is
ace
related
to
viva
connections?
So
aces
are
going
to
appear
on
the
viva
connections
dashboard.
So
this
is
the
way
you
can
add.
Oh
no
v1.3
supported
currently
so
that
question
was
answered
up
above.
Thank
you
for
that.
So
these
are
the
way
you
can
eject
your
extensibility
into
viva.
A
A
A
So
I'm
just
gonna
get
a
link
to
that
channel,
we'll
copy
that
we'll
come
back
over
here
and
paste
that
there
and
what
you're
going
to
see,
hopefully
hey
good,
it's
working
so
you've
seen
this
now
go
out
and
it's
read
nine
new
messages
in
the
channel
and
here's
here's
the
channel
we're
linked
to.
So
you
can
check
my
work
and
count
these
messages,
but
some
neat
things
here
so
this
is
this
sample
here
is
going
to
show
you
a
little
bit
more
complicated
patterns.
A
We've
got
multiple
card
views,
we've
got
multiple
quick
views
and
we've
got
some
real
interactivity
now
in
a
form
talking
back
to
that
team's
channel.
So
a
couple
things
I
want
to
show
is:
if
I
come
in
here-
and
I
start
a
new
conversation-
and
I
say
hello
from
the
demo-
we'll
send
that
into
the
team's
channel
and
if
we
are
lucky
today,
this
is
going
to
update
momentarily
here.
I
think
it
takes
about
15
seconds,
give
or
take
hey
10
new
messages,
that's
fantastic,
that
it
works,
love
it.
A
So
this
is
neat.
It
shows
us
how
many
new
messages
we
have.
So
you
can
imagine
this
on
your
mobile
device
checking
in
not
necessarily
just
to
teams,
but
imagine
this
pattern
you're
checking
into
a
help
desk
ticketing
system-
or
you
know
your
email
or
there's
lots
of
you
know
things
in
our
world
right
that
are
notification
based
now.
So
this
pattern
kind
of
shows
you
an
approach
to
that.
Now
I
can
click
the
quick
view,
I'm
going
to
caution
folks,
I'm
a
very,
very
good
designer,
so
visually.
A
This
is
probably
the
prettiest
thing
you're
going
to
see,
but
it's
shows
all
our
messages
from
the
channel.
So
you
can
see
here
hello
from
the
the
demo
there
and
you
can
see
you've
got
down
the
little
text
there.
It
says
from
patrick
so
we're
able
to
get
this
information
from
the
team's
channel
and
now
I
want
to
go
in
here
and
this
you
know:
cool
little
sunglasses
icon.
It
actually
says
here
hello
from
the
demo.
A
I
can
enter
a
reply
hi
there
right,
I'm
going
to
click
my
button,
so
there's
a
little
rendering
snafu
there,
but
you
can
see
I've
said
hi
there
and
if
we
go
back
to
our
channel
hey,
it's
always
neat.
When
the
code
works,
we've
responded
to
our
team's
channel
and
said
hi
there.
So
I
can
close
this.
I
can
see
my
other
messages.
I
can
look
at
other
messages
and
they're
all
pretty
much
me
just
talking
to
myself.
So
it's
not
the
most
exciting
chat.
A
But
the
point
of
this
is:
we've
shown
a
pattern
where
we
can
go
pull
something
get
information
from
it.
We've
got
a
quick
view
that
shows
us
a
list
of
things
and
then
we've
got
another
quick
view
that
shows
us
the
detail
of
those
things
and
we've
added
interactivity
into
that
quick
view.
So
we
can
interact
with
that
thing
that
we're
seeing
the
details
of
right.
That
is
probably
one
of
the
most
common
web
patterns
right.
So
this
sort
of
highlights
how
to
do
all
that.
Well,
how
did
we
do
all
that?
A
So
again
we
scaffolded
our
extension
using
the
omen
generator
exactly
as
before,
we're
going
to
go
into
our
adaptive
card
extension
and
there's
a
lot
more
code
in
this
one.
So
we've
got
five
different
views,
three
card
views
and
two
quick
views
and
we've
got
in
our
on
init
we've
registered
all
of
our
different
views.
Just
as
before,
again
using
the
card
navigator
and
the
quick
view
navigator,
we've
set
our
initial
state
note.
One
thing:
we're
tracking
here
is
the
card
view
to
render.
A
So
this
is
saying
our
base
or
our
default
view
is
going
to
be
this
one
which
happens
to
be
called
default
view
make
it
easy
on
myself
and
some
of
the
other
stuff
we're
just
gonna
null
it
up
negative
ones,
no
big
deal,
and
then
we
have
this
method
set
up
views
we'll
come
to
that
in
just
a
second-
and
this
is
now
we've
there.
So
here's
setup
views
and
we're
checking
some
things
now.
So
we've
got
this
idea
that
we
have
these
views
and
we
need
settings
to
actually
go
to
the
channel.
A
A
A
So
if
you,
even
if
this
is
controlled
by
state,
it
will
not
reflow
if
you,
if
the
value
here
changes,
it's
not
checked
right.
So
you,
you
are
responsible
for
using
the
methods
of
the
card
navigator,
in
this
case
we're
showing
replace
and
we're
going
to
show
another
technique
here
in
a
second,
so
replace
says
whatever
view
you're
showing
just
get
rid
of
it
and
put.
This
is
the
view
I
want
you
to
show
now
and
remember
the
views
all
share
the
same
state.
A
So
there
isn't
a
huge
penalty
here,
you're
setting
the
state
as
one
thing
and
the
view
is
another
thing,
so
we're
replacing
our
current
view
with
another
view.
That's
just
going
to
pull
the
current
state
and
show
its
self
to
the
world.
In
this
case.
It's
our
card
that
says
hey,
we
need
some
data
go
please
set
the
the
channel
there
and
then
I
like
regex
is
a
great
way
to
solve
problems.
A
A
You
need
to
understand
how
to
communicate
with
that
channel
via
graph,
and
so
if
our
matches
are
null
or
we
don't
have
the
number
we
expect,
which
is
three-
we
have
another
card
we're
gonna
show
here,
which
is
hey
the
channel
link
you
gave
us,
we
don't
understand
that
could
be
because
you
didn't
give
us
a
channel
link,
that's
correct
or
perhaps
channel
links
have
changed
right.
This
could
be
a
bug
in
our
regex,
which
would
be
shocking
to
have
a
bug
in
regex
and
then
we're
doing
the
same
operation.
A
We're
replacing
that
card
navigator
view
there
we're
going
to
update
the
state
again
with
our
channel
base
url
that
we've
built
from
the
values
we
captured
there
we're
going
to
set
our
card
view
to
render
and
again
we
still
have
to
do
the
replaces
right.
So
everyone
replace
that
we've
got
our
ms
graph
client
factory.
So
this
is
very
much
like
sharepoint
framework
built
right
in
so
I'm
getting
it
off
of
this.context
getclient
got
my
client
and
then
I've
got
a
module
here.
A
I'll
show
you
briefly,
but
again
graph
isn't
quite
the
topic
of
this
demo,
but
we're
passing
in
the
client
and
the
channel
base
url.
So
a
similar
pattern
to
what
you
saw
with
the
previous
one,
where
we're
sort
of
capturing
those
things.
So
we
can
use
this
module
in
our
views
that
do
not
have
access
to
the
context
and
then
we're
getting
a
message
reader
here
and
that
reader
actually
is
just
it's
a
it's
gonna
pull
the
graph
service
and
anytime.
A
A
A
It's
really
up
to
you,
but
I
think
this
is
nice,
because
the
card
views
are
pretty
compact
single
file
things,
and
so
this
is
really
just
saying
this
is
our
default.
So
this
is
saying
you
know:
we've
got
this
many
new
messages,
so
our
state
message
is
linked:
that's
our
messages,
array,
icon
properties
and
so
forth,
and
we
are
returning
from
our
card
selection.
The
quick
view
and
the
view
we're
gonna
show
is
the
message
list
right.
We're
gonna,
look
at
that
in
a
second.
A
A
A
Are
there
new
messages
in
other
places,
right
we're
just
going
to
get
our
messages
from
the
state
and
return
those
messages
we're
going
to
require
a
template
and
on
action
we
set
the
state
of
what
the
selected
method
is
and
then
here's
the
other
option
in
quickview,
navigator,
cardview,
navigator
works
the
same
way
here,
we're
doing
quick
views,
but
we're
doing
push
so
we're
pushing
into
a
stack
of
views,
a
new
view
right
and
you'll
see
in
a
second.
Why
we've
done
that
real,
quick
looking
at
the
template.
A
This
is
a
little
bit
more
complicated
template
again
not
going
to
go
through
this
completely.
But
one
thing
to
note
here
is,
and
where
do
you
do
so
in
adaptive
cards
you
have
this
dollar
sign
data
to
which
you
can
bind
collections
and
then
the
rest
of
the
things
in
this
block
are
essentially
going
to
be
a
repeater
right.
So
it's
going
to
do
a
column
and
it's
going
to
do
a
subject
from
each
message
right
and
the
the
user
from
each
message.
A
So
you've
got
your
data
and
then
adaptive
cards
is
going
to
essentially
repeat
that
and
you've
got
your
action
here
to
view,
and
you
can
see
in
the
data,
you
can
add
things
into
this
data
property
data
value
things
in
my
case,
I'm
using
the
index.
We
go
back
and
look
I'm
getting
the
index
there.
That
tells
me
the
selected
message-
and
I
pushed
our
view
in
there
and
I'm
running
out
of
time
on
myself,
which
is
fine
and
then
message
view
is
very
similar.
A
It's
getting
our
messages,
it's
showing
them
off
center
state
on
our
action.
We're
doing
some
logic
here
to
keep
our
polling
going
correctly,
we're
setting
timeouts
again
to
load
up
that
message.
Content.
Those
message
replies,
I'm
not
going
to
dive
too
much
into
the
messages
module.
I
do
encourage
you
to
check
it
out,
as
you
have
time
outside
of
this
demo,
but
you
can
see
how
we've
done
readers
we've
used.
A
Generator
functions
interesting
pattern
there
to
to
process
delta
next
links,
and
then
we've
got
our
on
message
function
that
is
returning
out
the
actual
messages
from
our
generator
as
we
get
them,
and
then
we've
got
different
functions
here
to
get
message.
Details
get
message,
replies
but
they're
all
using
that
client
that
we
sort
of
grabbed
a
ref
to
with
that
init
messages
when
we
were
still
in
the
ace.
A
So
with
that,
I
do
want
to
take
just
a
second
to
do
a
surprise.
Demonstration
of
pmpgs
v3,
so
julie
and
I've
had
a
lot
of
fun
working
on
this.
We're
really
excited
to
start
showing
it
to
you
and
I'm
just
going
to
give
you
a
very
quick
overview
of
this.
We're
not
going
to
go
into
this
deep,
but
I'm
excited
to
start
talking
about
this
and
to
give
you
all
a
taste
of
what's
coming,
so
you
can
see
a
little
bit
ignore
all
these
variable
names
and
things.
A
This
is
all
just
testing,
but
what
we've
got
here
is
I've
created
a
new
sp
here,
you're,
giving
it
a
url
directly.
We've
got
a
new
model,
that's
very
much
more
event.
Middleware
based
using
sp
default,
we
give
it
some
msal
stuff
we're
using
a
debug
logger,
so
we're
able
to
add
lots
of
things
in
there
and
then
I'm
just
going
to
hit
f5
real,
quick,
mostly
to
prove
to
myself
that
f5
still
works,
but
this
is
going
to
run
and
you're
going
to
see
the
syntax
for
you,
the
user
hasn't
changed.
A
A
A
A
We've
got
a
lot
of
feedback
that
I
just
want
to
write
a
parser
or
I
just
want
to
write
off
or
something
like
that
and
the
past
has
been
very
very
hard,
so
you
know
and
not
intuitive
on
how
to
do
that.
So
what
we've
done
is
created
a
model
where
you
could
plug
into
all
of
these
sort
of
events,
as
the
requests
are
built
and
process,
those
as
we
go
and
you
can
see,
we
actually
did
get
data
back
because
that's
always
very
exciting
to
see.
A
So
that's
a
super
quick
preview
on
pnpgs
v3.
If
you
want
to
know
more
we're
going
to
do
a
longer
session
on
that
when
we
get
a
chance.
But
I
want
to
thank
everybody
for
listening
to
me.
Talk
for
a
long
time
about
aces
about
viva
connections,
development-
I'm
very
excited
about-
I
think,
there's
a
lot
of
cool
opportunity
there,
a
lot
of
new
stuff
to
do.
I'm
really
excited
to
see
what
folks
in
the
community
build
using
this
new
model,
so
check
out
my
samples.
A
Let
me
know
what
you
think
submit
your
own
samples.
Very
much
encourage
you
to
do
that.
Julie's
got
some
great
samples
out
there
and
I
do
want
to
thank
julie,
turner
for
all
her
great
work
on
pmpgs
v3
she's
made
a
huge
impact
there
and
it's
been
invaluable
to
have
her
help.
So
thank
you
to
julie
for
all
her
work
there
and
thank
you
to
all
of
you
for
joining
us
today
on
the
call
the
recording
the
call
will
be
available
about
24
hours
on
our
youtube
channel.
A
Follow
us
on
twitter,
365,
dev
and
m365
pmp.
Next
spf
x,
call
is
going
to
be
september.
9Th
that
can't
possibly
be
right
can't
almost
be
september
next,
general
dev
call
next
thursday
september
2nd.
At
the
same
time,
all
community
calls
aka.mssm
365
pnp
as
well
got
lots
of
developer
calls
coming
up
the
platform,
call
that
I
bungled
discussing
31st
of
august
coming
up
and
then
a
lot
of
the
other
calls
will
reset
as
well
in
september.