►
From YouTube: SPFx JavaScript SIG 31st of August, 2017
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting.
It
is
August
31st
2017
is
our
third
meeting
in
August,
which
makes
this
a
bonus
month
for
us,
which
is
pretty
neat
to
get
three
meetings
in
a
month,
I
suppose,
and
also
a
little
frightening
that
August
is
already
evaporated.
So
looking
ahead
are
looking
at
the
topics
of
this
meeting.
A
This
is
for
folks
that
might
be
listening
to
this,
for
the
first
time
are
attending
the
call
for
the
first
time
we
exist
inside
the
larger
SharePoint
patterns
and
practices
program,
and
these
special
interest
groups
started
out
as
a
way
to
have
a
more
focused
conversation
around
different
topic
areas,
and
this
one
covers
SharePoint
framework,
client
side
development
in
general
on
SharePoint,
and
then
this
javascript
core
library
we've
developed
to
go
along
and
help
with
this
client-side
development
work.
Folks
are
doing.
We
also
have
one
on
the
PowerShell
and
the
manage
code,
see
psalm
library.
A
So
that's
a
great
call
as
well.
You
can,
of
course
attend
as
many
of
these
as
you
like,
and
then
we
do
have
a
monthly
community
call
as
well.
That
covers
the
more
high-level
topics
within
the
patterns
and
practices
program.
So
do
please
check
those
out
and
we
would
invite
you
to
participate
in
as
much
of
that
as
you
would
like
two
links
down
there
at
the
bottom.
A
A
A
Maybe
projects
you're
working
on
are
ideas
to
solve
problems
and
then
as
well
dev
office,
comm,
/
SharePoint
is
your
one-stop
shop
for
all
things:
SharePoint
development
that
is
a
great
place
to
get
started,
whether
you're
getting
started
on
whether
it's
the
the
classic
SharePoint
development,
with
solutions,
whether
it's
a
DIN
development
or
whether
it's
the
new
SharePoint
framework
development,
we're
moving
all
our
resources
there.
So,
if
you're,
if
you're
new
to
SharePoint
framework
and
want
to
get
started
with
that,
we've
got
great
tutorials
great
examples.
A
That's
been
posted
there
as
well
to
the
SPF
X
samples
so
have
both
of
those,
and
then
we
should
have
a
little
bit
of
time
at
the
end
for
an
open
discussion,
depending
on
how
long
the
presentations
take
so
moving
forward,
some
opportunities
to
participate
in
the
SharePoint
framework
patterns
and
practices
stuff,
this
javascript
specialist
group
or
the
larger
patterns
and
practices
program
in
general.
So
you
can
demo
a
SharePoint
framework
web
part
on
this
call
or
now
I
should
change
that
to
also
include
extensions.
A
So
this
is,
if
you're
doing
some
work
in
SharePoint
framework
would
love
to
have
you
get
in
touch
with
us?
You
can
demo
that
work
on
this
call,
so
love
to
promote
the
community
work.
I.
Think
it's
a
great
opportunity
for
all
of
us
to
learn
from
each
other.
You
can
demo
the
SPP
and
PJs
in
a
project.
So
if
you're
working
with
the
core
library
I
would
love
to
see
demos
on
that
as
well,
you
can,
of
course,
combine
that
with
your
SharePoint
framework,
demos
and.
A
Indeed,
you
can
contribute
on
github,
so
contribute
on.
Github
is
submitting
issues,
so
many
pull
requests
helping
other
folks
when
they
have
questions
and
that's
not
just
on
the
core
library,
that's
as
well,
you
can
get
involved
in
the
SharePoint
framework
repos
on
github
or
any
of
the
other
patterns
and
practices
stuff
on
github.
That's
a
great
way
to
get
a
little
more
involved
in
the
community
and
then,
of
course,
you
can
provide
feedback
on
any
of
the
work
we're
doing
so
not
just
the
development
work.
A
But
how
are
these
calls
going
other
than
apparently
my
ongoing
audio
issues
and
how
you
know
what
other
samples
would
you
like
to
see?
What
other
features
would
you
like
to
see,
and
this
or
that
library
really
it
all
boils
down
to?
How
can
we
help
you
be
more
effective
developers,
whether
that's
tutorials,
whether
that's
code,
samples,
whether
that
be
enhancements
to
various
libraries,
so
always
looking
for
that
feedback,
always
value
that
feedback
from
everyone
out
there
in
the
community,
quick.
A
Tell
if
you're
just
messing
with
me
today,
but
I'm
gonna
check
the
recording,
I'm
gonna
cut
that
little
section
out
just
for
you
all
right,
quick
update
on
the
JavaScript
core
component,
so
we
got
300
beta
zero.
The
beta
stuff
is
such
a
long
string,
but
we
got
that
published
on
August
29th
check
that
out
a
lot
of
changes.
There's
a
section
in
the
developer
guide
on
moving
your
code
from
the
to
o
stuff
to
300.
A
Looking
for
feedback
on
those
changes,
those
changes
aren't
done.
We're
still
working
on
three
Oh
that'll
be
delivered.
Hopefully
in
mid-september
is
the
goal,
but
definitely
looking
for
feedback
on
those
things.
Definitely
looking
for
folks
to
help
test
that
out,
try
it
out
with
your
code,
your
existing
code.
Let
us
know
if
we've
broken
something
that
was
working
because
clearly
that's
bad
and
then
we'll
we'll
take
that
feedback
and
try
and
get
things
as
solid
as
we
can
for
the
release.
A
We've
added
graph
support
in
that
is,
with
some
known
limitations,
they're
outlined
in
a
blog
post
I
put
up,
but
really
those
limitations
mirror
the
limitations
in
SharePoint
framework
right
now,
we're
only
going
through
the
SharePoint
framework
client,
the
graph
HTTP
client.
So
we
have
the
same
limitations
around.
You
can
only
really
call
groups
and
reports,
but
we're
only
supporting
groups
at
this
point.
We've
coded
out
a
lot
of
that
API
surface,
but
not
not
nearly
all
of
it.
A
So
that's
some
work
to
be
done
as
well
as
just
testing
and
solidifying
that,
as
we
move
forward,
absolutely
do
not
recommend
that
you
upgrade
any
production
code
using
this
beta.
Yet
I,
don't
wouldn't
claim
it
to
be
that
solid,
I
think
I
mean
I,
think
it's
in
good
shape,
but
it
hasn't
been
thoroughly
tested
out
there
by
the
community.
It
hasn't
been
really
vetted
by
us
heavily
either.
A
So
this
is
truly
a
beta,
but
do
please
check
it
out,
give
us
some
feedback
and
then
once
we
get
the
actual
release
out
there,
that's
when
you
can
start
looking
to
migrate
some
production
code,
I
did
as
part
of
this
in
the
blog
post,
mentioned
some
future
plans
and
sort
of
our
future
thinking.
At
least
that
was
a
snapshot
of
our
future
thinking.
A
Nothing
is
100%,
decided
on
that,
so
we're
still
internally
in
the
core
team
talking
about
that
and
trying
to
figure
out
exactly
how
things
are
gonna
shape
up,
but
we
have
a
couple
of
goals
which
are
absolutely
going
to
be
the
goals
we
carry
forward.
Number
one
is
gonna,
be
making
things
easier
and
clearer
for
consumers
of
the
library
right
now
it's
a
little
bit
jumbled.
We
have
a
lot
of
stuff
in
sort
of
the
global
or
global
library
namespace,
and
things
like
that.
A
We
also
are
starting
to
the
file
size
of
the
library
is
starting
to
get
quite
large
for
a
while.
It
was
we'll
just
say
you
know
heavy,
and
now
it's
it's
giant.
So
we've
we're
looking
at
breaking
up
this
kind
of
single
import
into
lots
of
smaller
imports,
which
will
one
help
with
file
size
in
your
projects,
but
to
allow
you
to
just
sort
of
import
the
parts
you
want
in
need
of
our
stuff
as
opposed
to
right
now.
A
If
you
were
going
to
do
some
SharePoint
work
and
not
touch
graph
well,
it
doesn't
matter
we're
giving
you
the
graph
stuff
as
well
right,
which
certainly
not
ideal.
We
recognize
that
so
we're
gonna
look
to
address
those
in
this
sort
of
future
release,
that's
going
to
come
and
then
really
we're.
Gonna
kind
of
reaaargh
attacked
everything
for
growth
and
expansion,
so
we're
looking
at
covering
not
just
but
additional
services
so
graph.
A
great
example
also,
possibly
teams,
possibly
some
other
things.
A
B
Thanks
so
obviously
the
the
big
news
on
the
SharePoint
framework
side
is
we're.
Gonna
talk
about
that
one
in
a
second,
but
before
we
go
there,
just
a
reminder:
I,
we
do
know
that
the
SharePoint
well,
the
Microsoft
ignite,
has
been
now
fully
booked.
That's
happening
later
in
September
I
almost
said
late
at
this
month,
which
is
well
that
would
have
been
valid
in
tomorrow,
but
we
do
have
a
for
specific
stations
on
SharePoint
development
and
there's
additional
theater
sessions
in
the
expo
area
as
well
and
from
these
four
sessions.
B
All
of
them
are
actually
touching
SharePoint
framework,
so
there
will
be
a
lot
of
content
on
the
SharePoint
development
in
general
and
also
in
a
SharePoint
framework
and
the
future
of
the
SharePoint
framework
and
SharePoint
customizations,
and
we
do
have
a
SharePoint
BMP
booth
with
shipment
engineering
and
MVPs.
So
the
PMB
according
members,
helping
you
with
any
questions
or
anything
what
you
want
to
see
or
if
you
need
any
guidance
on
your
issues
or
whatever
on
your
day-to-day
work,
and
there
is
also
a
chef
on
topics
and
office
def
pre
day.
B
So
there
is
an
old
specific
office
developer.
Pre
day,
which
we
will
aware,
we
will
cover
mics
of
craft
teams
and
shipment
framework.
So,
if
you're
interested
on
that,
one
I
do
not
know
how
many
spots
we
still
might
or
might
not
have
free
on
the
pre
day,
but
I
do
know
that
ignite
is
actually
fully
booked
already
good.
B
So
the
big
news
on
the
chef
on
framework
side
obviously
is
to
release
candidate
of
the
SharePoint
framework.
Extensions
which
went
live
on
Wednesday
time
flies.
I
think
it
was
yes,
Wednesday
yeah
completely
messed
up
on
the
dates.
It's
been
working
way
too
much
recently
now
I'm,
so
the
SharePoint
framework
extension
released
is
the
version
1.2
release
of
the
of
the
SharePoint
framework,
and,
as
part
of
this,
we
released
the
extensions
release
candidate.
B
It
actually
does
contain
a
lot
of
additional
capabilities
and
improvements
also
for
the
web
part
site,
so
do
not
get
confused
that
this
release
would
be
only
if
you're
interested
on
the
extensions.
This
does
contain
a
lot
of
improvements
on
the
on
the
web
parts
side
as
well.
If
you
go
and
have
a
look
on
our
release,
notes
which
I
do
not
have
a
link
in
here,
but
it's
in
the
SPF
docs
repository,
you
can
actually
see
all
of
the
lists
of
things.
What
has
been
improved
on
on
the
web
parts
side
as
well.
B
Probably
the
biggest
things
are:
the
the
version
pumps
on
the
on
the
office
UI
fabric
and
react
so
updated
version.
Dependence
is
no
of
that
because
those
do
have
a
big
meaning
on
your
customizations.
Now
on
the
extension
release
candidate,
which
was
included
in
this
one,
it
does
work
in
both
developer
and
first
released
tenants.
So
you
do
not
no
longer
need
to
have
a
developer
tenant
to
be
able
to
do
extension.
Preview
work.
B
We
do
not
support
extensions
yet
in
the
production
usage,
so
so
they've
theoretically,
might
be
a
some
breaking
changes
when
we
move
into
the
GA,
but
we're
pretty
close
on
one
locking
down
to
api's.
So
it's
pretty
pretty
safe,
but
we
wouldn't
recommend
anybody
to
actually
use
that
in
the
production
for
for
now,
we
are
absolutely
looking
still
feedback
right
now
for
the
initial
GA.
B
There
won't
be
that
many
changes
anymore
just
want
to
stabilize
the
API
I
want
to
stabilize
the
code,
but
we
absolutely
want
to
keep
on
evolving
the
extensions
in
the
future
as
well
and
we'll
take
your
feedback
into
account
in
the
upcoming
releases
as
well
and
the
reality
for
for
us.
It's
always
well,
somebody
might
say:
hey
I
provided
feedback
few
months
ago
already
in
the
issue
list,
and
apparently
that
wasn't
addressed
in
the
release
candidate.
Why
didn't
you
do
that?
B
Well,
let's
think
about
this
from
a
Microsoft
respected
immediately
when
we
coach
EA
with
this
abstentions,
we
can
no
longer
change
the
API,
it's
locked,
so
what
we
need
to
do
is
always
to
stabilize
the
API
make
sure
that
the
API
surface
this
is
essentially
working
properly
and
really
concentrate
on
that
one.
So
we
can't
kind
of
a
in
the
last
time
or
too
much
try
to
get
additional
things
within
the
version
1.0
release
of
the
extensions.
Now
we
will
absolutely
keep
on
evolving
this.
B
B
There's
no
ETA
for
general
availability
at
this
point,
but
the
classic
rule
for
anything
in
related
on
SharePoint
is
that
we
do
quite
often
release
our
stuff
as
part
of
larger
conferences,
and
you
might
have
a
look
on
the
calendar.
If
there's
a
large
conference
coming
up
relatively
soon,
I
cannot
confirm
or
deny
any
of
your
assumptions
based
on
that.
So
I'm
not
gonna
confirm
anything
on
that.
B
The
question
is
on
the:
what
versions
of
react?
Thank
you
Joe
for
obtaining
that
one
from
the
release
candidate
from
the
release
notes.
So
we
do
have
the
exit
versions
available
in
the
in
the
release,
candidate
release
notes,
so
I
can
double-check
those
cute
I
think
I
had
a
few
more
slides,
so
new
guidance
and
tutorials.
Obviously
the
extension
tutorials
meant
live
as
part
of
the
release
candidate,
so
we
updated
all
of
our
extension
tutorials.
B
So
if
we
wanna
start
learning
or
if
you
already
went
through
the
tutorials-
and
you
want
to
double
check
that
hey,
what
do
I
need
to
do
to
update
my
code,
you
can
easily
have
a
look
on
that
in
the
tutorial
written
tutorials.
The
written
tutorials
are
their
sake,
a
coded
version
of
them,
so
the
outcome
version
is
available
from
the
github
and
we
also
have
a
video
versions
now
released
in
the
YouTube.
B
So
if
you
rather
want
to
follow
up
on
the
on
the
tutorial
in
the
video
format,
that's
now
available
from
the
YouTube
as
well,
we
do
have
two
general
new
guidance
articles
around
the
SharePoint
framework.
The
first
one
is
kind
of
a
generic
for
SharePoint
framework
solutions
or
working
guidelines
on
working
with
CSS
and
styling
within
the
work
for
within
the
SharePoint
framework
solution,
and
the
second
one
is
around
integrating
web
properties
with
SharePoint.
B
So
how
do
you
decorate
your
web
part
properties
in
a
way
that,
for
example,
shipment
search
or
search
will
actually
index
them
so
and
there's
additional
things
related
on
that
one?
So
two
quite
nice
articles
which
came
directly
from
engineering,
and
then
we
had
a
few
people
polishing
those
things
up
before
we
push
them
out
in
the
desert.
B
Calm
now
one
thing:
what
I
wanted
to
also
remind
we:
we
did
have
a
I
think
from
this
Monday
we're
release
the
webcast
on
the
PMP
PMP
webcast,
which
was
around
the
TDP,
our
activity
hub
and
the
that
some
might
sound
weird.
But
the
whole
point
of
this
webcast
is
actually
to
have
a
more
ready
to
use,
polished,
starter
kit,
which
is
using
SharePoint
framework,
webparts
and
automatic
provisioning
it.
Actually,
you
can
set
up
this
SharePoint
framework,
modern
solution
up
and
running
within
a
matter
of
minutes
and
it's
using
power,
bi
shape
and
framework
solutions.
B
B
I'll,
come
back
on
the
other
questions
in
a
second
I
just
want
to
make
sure
that
we
don't
eat
up
time
from
the
demos
no
thinks
what's
ship
on
the
engineering
is
working
on
I'm,
trying
to
kind
of
update
this
as
we
move
along
and
add
additional
things
based
on
whenever
we
can
actually
share
something,
but
over
us.
The
SharePoint
framework
extensions
now
in
release
candidate,
so
getting
close
to
be
shipped.
B
The
automatic
solution
deployment
should
be
renamed
actually
tenon
scoped
deployment
of
chevron
framework
solution,
that's
already
out
site
collection,
app,
catalog,
that's
coming
up
sooner
or
later,
mostly
when
we
actually
get
it
fully
polished
and
out.
But
the
whole
idea
is
that
you
can
actually
not
require
that
all
of
the
solutions
are
getting
deployed
on
the
tenant
level.
B
App
catalog,
tenant
administrator
can
actually
approve
that
there
are
certain
site
collections
catalogs
as
well,
where
people
can
test
or
enable
the
solution
by
themselves
without
the
tenant
admin
permissions,
and
that's
really
also
to
isolate
how
the
solutions
are
will
be
visible.
So
if
you
only
put
the
webparts
solution
to
your
site
collections
graph,
catalog,
obviously
that
web
part
would
be
visible
only
within
that
site
collection.
So
you
can
isolate
more
precisely
where
the
customizations
are
available.
That's
in
the
development,
it's
not
in
preview,
even
though
it
has
a
orange
marker,
which
is
my
mistake.
B
Storage
marker
should
have
been
for
those
which
are
in
preview.
On-Premises
supports
for
sharepoint
2016
feature
pack.
2
will
have
sharepoint
framework
with
part
support.
It
will
not
have
sharepoint
framework
extension
support,
but
it
will
support
the
modern
web
port
developments
whenever
that
goes,
live
I
do
not
know,
probably
heard
about
it,
but
I'm
in
a
different
organization:
who's
responsible
shipping,
those
versions
kravitz,
the
big
client-
that's
evolving
as
well.
B
We
should
have
some
new
news
on
that,
one
in
ignite
a
dialog
control
as
part
of
the
SharePoint
framework
extensions,
so
that's
evolving
as
well
ALM
api's.
This
is
for
for
the
fact
that
if
you
need
to
automate
SharePoint
framework
or
adding
solutions
to
get
deployed
on
a
site
election
in
a
targeted
way,
you
can
actually
do
this
in
the
future.
B
It
right,
install
update,
delete,
yeah,
that's
all
what
we
need
and
you're
able
to
get
the
list
of
available
solutions,
and
all
of
that
those
will
work
you
and
me
at
least
when
we
start
they
will
only
work
with
together
with
the
ad
catalogs
and
because
using
the
store
and
deployment
automation,
deployment
from
the
store
has
a
license
in
implications
and
implementing
that
using
API
is
super.
Super
super
difficult
thing,
but
this
should
help
on
the
hey.
B
B
Well,
so
we've
shipped
this
10
scoped
feature
three
weeks
ago
as
part
of
the
chiffon
framer
of
the
previous
release
of
SharePoint
framework.
So
that's
just
a
a
slide
which
has
been
evolving,
try
to
be
moving
on.
Obviously,
we've
been
shipping
a
lot
of
additional
capabilities
and
things
these
are
just
raised
as
a
key
pointers
from
a
capability
perspective
which
we
know
that
has
been
asked
significantly
by
the
community
good.
B
Only
one
of
them
is
Korean
rest
of
them
Israel.
It
looks
bad
yes
because
we
want
to
sell
only
the
latest
things
which
I
meant
to
go
live
for
you
in
the
future.
We
don't
want
to
list
40
different
things
which
has
been
already
shipped.
That's
really
the
turbo
software
after
slide,
so
only
the
latest
things.
What's
the
latest
things
which
will
provide
the
value
for
the
community,
we
certainly
could
have
a
massive
slide,
which
is
listing
all
of
the
things
which
we
have
already
shipped
know
the
value
of
that
one
good.
B
B
Now,
let's
move
into
the
demo
section:
I'll
have
a
look
on
the
on
the
own
window.
If
there
are
some
questions
which
I
missed
when
I
was
chatting
and
having
my
big
monologue,
but
let's
start
with
Stephan
Stephanie
as
Stefan
I
can't
pronounce
your
name
probably
properly.
Are
you
all
ready?
You've
been
upgraded,
Supercenter
good,
it's
definitely
okay,
so
you
can
actually
just
start
sharing
and
take
over
all
moving
the
ion
window
and
after
after
you
will
move
into
the
Christian.
Let's
see
if
we
can
have
time
for
Q&A
and
screen
sharing
is
loading.
B
C
So
hi,
my
name
is
Stephan
Manny
I
am
currently
a
technical
leader
for
mosaic
365.
It's
a
SharePoint
based
internet
solution
and
today
I'm
going
to
show
you
a
page
contributors,
webpart
done
with
the
SharePoint
framework,
but
what
it
does
is
basically
just
showing
latest
page
editors
in
reverse,
chronological
order.
So
if
I'm
going
on
this
page,
for
example,
I
can
see
that
they
she
had
two
editors
and
as
the
user
as
a
reader
I'm
able
to
contact
them.
If,
if
I
want
to
ask
questions,
for
example,
it
has
different
properties.
C
The
first
one
is
the
number
of
people
that
we
want
to
show
the
icon
size.
We
can
check
that
on
purpose
and
server
URL
of
a
page
if
we
want
to
display
data
from
a
different
page
than
the
current
one,
actually,
where
you
think
that
internally
for
development
purposes,
as
here
I'm
in
the
SharePoint
workbench,
but
I'm,
not
in
a
red
page,
if
we
start
go
into
the
code,
we
first
have
our
web
properties,
which
reflects
what
we
have
seen
on
the
Explorer.
C
If
we
go
on
on
a
wet
bath
code,
we
see
that
it's
a
simple
web
part
with
the
property
pan
configuration
that
is
fairly
classic.
We
have
a
slider
for
the
number
of
people
to
show.
We
have
drop-down
for
the
size
and
just
a
text
field
for
the
page
URL.
The
tricky
part
in
this
webpart
code
is
to
on
the
init
function,
to
set
up
the
PNP
library
to
pass
the
context
so
that
the
requests
can
work.
C
Properties
are
initialized
in
the
web
manifesto.
We
have
five
people
by
default
and
we
select
the
small
size
by
default.
Now,
if
we
go
deep
dive
into
our
components
code,
we
see
that
we
reference
both
office,
UI
fabric
library
and
HP
pnp,
JS
library.
We
are
using
different
components
from
fabric
we
have
the
face
by
to
show
the
people
we
have
a
spinner
for
the
loading
part
and
message
bar
to
display
errors
in
cast.
There
are
some
components.
Properties
are
the
same
than
what
past
one.
So
we
won't
look
at
that.
C
C
We
have
two
functions
for
data
loading,
so
as
a
service.
The
first
function
loads
mock
data
in
case
we
are
not
in
the
SharePoint
context,
so
on
the
workbench,
for
example,
each
loss
data
after
two
seconds,
so
that
we
can
test
the
UI
and
for
the
loading
part,
and
then
we
have.
We
have
our
real
function
for
the
service.
C
It
takes
the
you
are
as
an
input
and
it
HSS
PMP
that
espied
that
web
that
get
file
to
open
the
page
and
select
the
modified
by
field
it
expands
it
to
have
the
different
fields
come
composing
it,
and
then
we
check
for
odd
versions
on
the
files.
So
it's
a
different
weekend.
We
request.
We
have
two
requests
there
with
the
dot
versions
here
and
we
order
by
them
by
created
field
and
we
select
created
by
field.
C
Then
we
have
our
page
contributors
state.
This
is
how
web
at
state-
and
it
will
be
used
by
the
different
components,
to
update
the
UI.
We
have
a
first
component,
which
is
a
loading
button.
We
have
the
error
message
using
the
message
per
component
from
fabric
and
we
finally
have
our
web
part.
The
render
function
just
shows
the
face
pile
from
fabric,
the
loading
control
and
the
error
message,
which
will
automatically
update
based
based
on
the
state.
C
We
load
the
different
users
on
the
component
mount
and
we
relate
them
on
the
component
update
if
the
user
changed
the
page,
URL
property
and
we
finally
have
our
large
users
function,
it
just
checks
the
correct
environment.
So
if
we
are
in
the
workbench,
we
just
get
mock
data,
and
if
we
are
in
a
SharePoint
context,
we
can
get
the
real
data.
C
We
see
there
that
we
passed
as
an
argument
either
the
webparts
properties
or
just
the
location
that
path
name
from
the
navigator
and
then
the
other
functions
I'll
just
help
us
to
help
us
set
the
state.
So
we
can
set
the
state
of
not
loading
without
error
and
we
have
our
contributors.
We
have
an
error,
we
build
the
message
from
the
SharePoint
error
and
we
we
clear
the
contributor
spot
and
that's
all.
We
then
have
our
word
part
in
this
page.
B
D
So
my
name
is
Chris
Kent,
the
SharePoint
practice
lead
for
DMI.
There
I
am
on
Twitter
there's
my
website
go
check
it
out
all
right,
oh
and
just
for
Paul
I
added
a
bunch
of
check
marks.
Oh
all,
right,
whoo,
okay,
moving
on
here,
we
talk
about
an
application
customizer
sample,
so
application
customized
just
review,
add
scripts
to
the
page,
but
they
also
give
you
access
to
these
kind
of
standards.
You
know
placeholders
so
as
of
what
Wednesday
right
these
are
now
top
and
bottom.
D
So
these
are
the
ones
you
call
page
header,
page
footer
before
so
put
much
stuff.
In
there
it's
pretty
cool
the
the
application
I'm
gonna
show.
You
got
the
case.
Customizer
I've
got
here
really
focused
on
the
add
scripts
to
the
page.
If
you're
looking
for
a
good
sample
for
the
placeholders
Magnificence
got
one
called
list
driven,
placeholders,
pretty
good,
there's,
actually
five
or
six
and
you
know
repository,
go
check
them
out
all
right.
Okay,
real
quick
here
it
is
jQuery
application
toaster.
It
does
all
of
these
things.
D
The
main
things
to
note
here
is
it's
taking
jQuery
and
the
toaster,
which
is
jQuery
plug-in.
So
those
from
CDN
puts
them
on
the
page.
Let's
show
these
toast
notifications.
Let's
do
some
cool
work
with
the
fabric
Styles
via
Stephan
Stephan
Bower
I'm
gonna
check
some
of
that
out.
It's
also
doing
some
caching
with
local
storage.
It
does
use
a
list
for
the
backend.
D
D
Okay,
so
here
we
have
a
communication
site.
It's
beautiful!
You
got
all
your
pretty
images
here.
You
know
we
want
to
show
some
exciting
notifications.
So
behind
the
scenes
got
this
toast
list
all
right.
So
take
a
look
at
the
toast
list.
We
got
title.
There's
some
content.
You
can
check
out
beyond
there
I'm
just
not
shown
on
this
view.
Severity
is
going
to
correspond
to
color
frequency
is
going
to
be
how
often
you
have
to
click
these
things.
D
Maybe
don't
always
do
these
always
that's
just
mean
we'll
talk
about
that
in
a
second
but
the
issue
you
can
schedule
these
or
enable
them
all
that
stuff
and
what
that
ends
up
doing
is,
if
we
add
our
debug
stirring
here
and
we
load
our
debug
scripts,
we
pray
there.
We
go
all
right,
so
we
get
these
very
exciting
notifications.
D
You
know
these
use
the
themes
you
know
directly,
so
we'll
show
that
here
in
a
second
the
idea
is
they
show
up
here
on
the
page.
You
can
dismiss
them,
you
just
click
them
to
get
rid
of
them,
but
the
idea
is,
we
didn't
actually
change
any
part
of
the
page
right
and
he's
only
show
up
when
you
need
to
they
do
get
cached
and
local
storage
along
with
your
acknowledgement.
So
it's
kind
of
a
neat
way
just
to
get
your
stuff
directly
integrated
into
the
environment
without
actually
changing
the
UI
itself.
D
In
terms
of
the
you
know,
the
generated
markup
for
Microsoft
all
right,
so
let's
take
a
look
at
what
the
code
is
actually
doing.
So,
oh,
that
was
fine.
There,
you
all
right.
So
this
kind
of
the
flow
of
the
code
you
want
to
take
a
look
at
it.
You
know
I'll
go
through
the
code
a
little
bit
here,
but
really
you
know
get
these
samples
go
ahead
and
download
that
whole
repo.
You
can
run
all
of
these
samples.
You
know
just
do
a
quick,
npm
install
you.
D
Do
a
gulp
serve
and
you're
good
to
go
copy,
that
debug
string,
there's
a
ton
of
stuff
in
there.
It's
just
one
of
them.
The
first
thing
we
do
is
load
the
jquery
and
toast,
or
the
CD
ends.
That's
just
using
our
externals.
Then
we
use
the
SP
component
loader,
throw
some
CSS
directly
from
the
CDN
for
toaster
now
and
then
we're
gonna
go,
get
the
toast
from
our
SharePoint
list,
using
this
kind
of
service
built
with
some
toast
service.
D
All
we
do
is
we
insure
toasts
that
just
checks,
your
local
storage
right
for
caching
or
the
list,
then
it's
gonna
reduce
the
toasts.
So
all
it's
really
gonna
do
is
look
hey.
What
did
this
user
already
click
on?
How
often
my
supposed
to
show
this
am
I
supposed
to
show
this
message
every
time.
The
page
loads
am
I
supposed
to
just
show
it
once
per
day.
That
kind
of
thing,
then,
once
that's
done,
we
actually
go
back,
we
configure
toaster
and
then
we
show
some
toast
all
right.
D
So
here
we
go.
You
take
a
look
here
and
you
config
JSON
right
here
and
the
externals
is
the
important
part
right
here,
we're
pulling
in
jQuery
and
we're
pulling
in
the
jQuery
plug-in
toaster,
which
is
a
plugin
by
code,
seven,
which
includes
people
like
C,
John,
Papa
and
I'm,
forgetting
the
other
guys
names
on
somebody
apologize
and
Tim
Farrell.
Okay,
hey
check
that
out.
D
It's
really
cool,
it's
extremely
flexible
and
this
side
we
loaded
into
our
our
extension
and
then
over
here
we
can
actually
see
where
we
start
off
the
extension
we
come
down
here
into
our
on
a
knit
event
which
is
really
or
only
our
on
and
then
a
method
which
is
really
all
we
have.
Now
we
don't
have
an
on
render
method.
That's
been
deprecated
again,
as
of
Wednesday,
so
check
out
that
link
you
can
find
a
bunch
of
stuff
on.
D
What's
changed,
but
here
we
load
in
our
CSS
also
from
the
CDN
that
was
easy
all
right
and
then
we
go
and
we
go
and
get
our
toast.
So
if
we
take
a
look
at
the
toast
service
is
actually
doing
that
you
can
see.
We
have
this
ensure
toast
with
just
checks
if
everything's
been
cached,
if
anything's
loaded
there
right
I
think
I've
got
a
two
minute
timeout
right
now.
Obviously
that
can
be
adjusted.
D
You
know
if
it
doesn't
have
the
cache.
Well,
then
it
needs
to
go,
get
it
from
the
list.
So
we're
just
pulling
this
in
we're
just
using
that
h2
SP
HTTP
client.
You
could
absolutely
use
the
PM
pjs
core,
for
this,
in
fact,
probably
make
things
a
little
easier,
but
for
simplicity
with
this
sample
I
just
stuck
with
the
one
extra
dependency
of
the
toaster
and
jQuery.
D
So
once
we
get
all
our
stuff
back,
we
go
and
we
reduce
it,
and
then
we
show
it,
but
before
we
show
it
over
here
we
got
the
classic
jQuery
document,
ready,
whoo
and
then
we're
gonna
go
through
set
all
these
different
options
on
toaster
all
right,
including
the
specialized
styles
here.
So
we've
got
our
own
styles
right,
but
we're
also
using
some
of
the
MS
icon
stuff
right
here.
So
if
you
take
a
look
at
that,
right,
take
a
look
at
an
actual
style
sheet
here.
D
If
you
checked
up
this
just
by
Stephen
butter,
Stefan,
Bower,
I,
hope,
I'm,
saying
that
right
he's
got
a
great
article
that
he's
written
and
put
together
where
you
can
see
these
kind
of
specialized
variables
that
allow
you
to
take
advantage
of
the
theme
colors
directly
within
your
class.
So
you
can
see
here.
That's
all
I'm
doing
here.
I've
got
Ms
bloom
and
Soren
slider
all
that
stuff.
That
way,
my
toast
matches
very
well.
What
they've
got
you
can
even
choose
the
actual
theme
color
itself
right.
D
So
if
you
want
all
your
notifications
to
match,
whatever
randomly
assign
color
you
got,
I
could
certainly
do
that
all
right.
So
once
it's
all
configured
and
we
get
all
our
toast
back,
we
just
start
show
them,
which
is
pretty
straightforward,
with
toaster,
it's
just
toast
or
dot
whatever
you
want
here
for
the
message
put
a
title
and
then
the
overrides
are
just
ways
that
we're
kind
of
passing
in
the
on
click
events
on
clothes,
which
is
how
we
acknowledge
all
right.
That's
it
pretty
exciting
check
it
out.
D
B
B
Good
work,
no,
but
this
is
actually
real
a
live
scenario,
and
this
is
such
a
great
scenario
from
that
perspective,
that
this
is
something
one.
Typically,
customers
do
want
to
have
within
their
corporate
portal.
They
want
to
have
a
some
sort
of
way
of
notifying
people,
maybe
a
link
within
a
toaster
saying
hey
by
the
way.
You
need
to
confirm
this
one
or
there's
now
an
alert
alert
your
building
is
on
fire.
No,
that's
not
necessarily
the
right
way
of
informing
that,
but
those
are
the
classical
scenarios.
B
People
always
want
to
have
these
kind
of
things,
and
just
as
well,
it
could
be
expanding
the
header
area
or
it
could
be
the
classic.
What
what
was
it?
What
what
did
we
had
back
in
2013?
It
was
the
warning:
no
not
warning
pop-up
thingy,
the
the
yellow
bars
which
we,
you
know,
there's
anyway,
multiple
ways
of
rendering
these
messages.
So
that's
that's
what
I'm
trying
to
find
cool
link
to
the
solution?
I
can
quickly
get
you
that
so
that's
in
SPD,
FFX
extensions
and,
let's
see
who's
fastest.
B
Good
but
I
think
that's
it
for
that.
One
now
I
did
personally
from
a
a
chef
intention,
Iranian
side.
We
didn't
prepare,
prepare
anything
too
specific
related
on,
for
example,
how
to
operate
your
customization
or
extensions
from
release
candidate
or
preview
for
release
candidate,
but
based
on
experience,
for
example,
from
Chris.
What's
your
input
on
on
the
amount
of
work
to
be
done,
it's
pretty
minimal
on
the
upgrading
of
your
extension
from
a
preview
to
release
candidate.
It
wasn't
a
massive
deal
right,
no
to
go,
maybe
half
hour
yeah!
B
So
a
few
things
here
and
there
and
like
Chris
mentioned
it
isn't
mentioned
in
the
notes.
We
did
do
reasons
or
another,
which
is
debatable
even
internally.
We
deprecated
on
render
method
and
application
customizer,
which
might
sound
slightly
weird,
and
we
had
a
pretty
blown
internal
discussion
in
into
engineering
as
well
that
why
did
we
do
that?
B
It
doesn't
make
any
sense,
but
that
now
has
been
done
and
the
final
agreement
hosted
will
do
that,
but
there's
still
ways
and
patterns
to
actually
output,
for
example,
stuff
to
your
placeholders,
so
that
the
capability
of
rendering
something
from
an
application
customizer
to
the
UI
is
not
going
to
go
away
absolutely
support.
That's
not
the
intention
of
getting
rid
of
done
render
and
the
scenario
white
on
render
was
actually
taken
away.
Was
that
quite
often
application
customizes
do
not
take
advantage
of
the
application.
B
Sorry
on
the
on
the
placeholders,
so
there
was
a
statement
that
it
would
be
confusing
for
people
if
there
is
a
mandatory
well,
not
mandatory,
but
if
there
would
be
a
non
render
which
you
can
override,
because
that
would
imply
that
your
waste
output,
something
in
the
placeholder
that
was
essentially
the
internal
logic
behind
of
that
decision,
but
I'll
get
from
that
perspective.
Any
random
questions
we
have
twenty
minutes
unless
Patrick
has
some
random
things
which
he
wants
to
show
Patrick
quickly
on
your
staff.
A
B
What
I'm
thinking,
if
you,
if
you
don't
mind
and
I,
can
have
a
look
on
door
and
window?
We
have
20
minutes
while
we're
doing
that.
We
can
absolutely
have
a
discussion
of
these
things
now
on
AC
engine
I
should
have
the
does,
it
make
sense,
D,
faith
more
frequently,
yeah
I
know
I
know
and
the
Chasen
config
the
the
schema
reference
is
changed.
B
So,
whatever
the
the
thing
which
has
been
deployed
to
the
ship
went
online,
it
has
to
work
for
years
to
come,
so
we
cannot
require
whenever
we
release
a
new
version
of
SharePoint
framework
or
office,
UI
fabric
or
react
or
whatever,
that
your
customization
on
SharePoint
framework
would
actually
pray
up,
it
would
be
aligned
actually
in
the
in
quite
often
a
web
web
stack
development.
World
people
actually
do
require
those
things,
but
in
a
SharePoint
world
in
the
Microsoft
Enterprise
office,
365
enterprise
development
world.
B
We
cannot
ask
people
to
update
their
code
whenever
we
are
pushing
an
update.
Their
code
has
to
work
within
a
SharePoint
Online
without
any
updates
and
we're
working
on
that
one
absolutely
and
we're.
There
was
actually
an
accident
around
this
one
as
part
of
the
release
candidate
release
and
that
has
been
tackled
internally
and
we
I
can
always
promise
that
we
try
to
learn
from
this.
B
We're
human
beings
and
people
are
trying
to
learn
from
the
mistakes,
but
mistakes
will
always
happen,
but
it
is
absolutely
in
our
attention
and
in
our
it
is
our
intention
that
all
of
your
old
versions
will
work
without
any
issues.
Any
updates
on
the
office.
You
have
fabric
react,
support
on
SharePoint
framework,
so
we
did
push
the
version,
but
there's
no
update
on
the
model
of
how
they
will
be
used.
So
the
version
dependency
has
been
pushed
up.
B
If
you
do
use
the
specific
version,
you
would
still
need
to
bundle
office,
your
fabric,
things
to
your
solution,
and
that's
really
because
we
wear
the
SharePoint
UIs
are
evolving
in
a
different
schedule
than
your
customization
and
office.
You
have
fabric
has
quite
often
breaking
chances.
So
that
would
mean
that
your
customization
would
actually
get
broken.
It's
not
an
optimal
situation,
but
realities
of
life
and
the
only
way
we
can
actually
make
that
work
right
now.
B
Any
news
on
enhancements
coming
to
fabric
nothing
list
of
my
site,
nothing.
What
I
can
actually
just
mention
on
there
anything
on
a
wrote,
internship
or
favorite
components,
making
their
way
into
office
store.
It
is
absolutely
in
a
roadmap
to
make
sure
that
people
can
actually
push
and
offer
SharePoint
framework
solutions
through
a
store,
true
with
store
and
how
and
where
that's
a
different
discussion
now
at
some
point.
Absolutely
it
will
happen.
The
probe
there
should
be
some
news
around
this
one
in
ignite
as
well
on
assuming
we
do
have
a
specific
p.m.
B
Well,
let's
actually
jump
on
Patrick
and
I
can
handle
questions
if
there's
any
Yoshi
yoga,
she
is
having
issues
with
latest
and
pay
and
packages
today
and
I
would
actually
and
Petra
as
well.
So
please
do
report
whatever
you
are
finding
and
and
if
you
have
issues
on
the
SPF
Doc's,
we
have
multiple,
multiple
people
and
dedicated
engineer
every
single
week
following
up
on
these
things.
What
I
would
actually
like
to
have
is
that
you
would
always
include
the
NPM
version.
B
B
Yes,
mine
just
worked
as
well,
so
that's
the
thing
I'm
just
trying
to
figure
out
where
the
the
issue
might
be
so
but
good.
We
have
all
the
version
details
in
here,
so
we
can
try
to
figure
out
a
repro
and
we
today
and
our
engineer
actually
was
able
to
make
that
work,
but
somebody
else
is
still
having
issues
so
we'll
follow
up
on
this,
we're
not
going
to
pray
we're
not
going
to
close
the
issue.
A
Problem
yeah,
so
just
I,
don't
really
have
anything
prepared,
but
just
to
kind
of
give
folks
a
little
bit
of
insight
into
what
we're
doing
internally
in
the
library.
So
this
is
the
300
is
gonna
remain
one
sort
of
file
one
package,
but
where
we're
headed
is
to
start
breaking
this
stuff
up.
So
here's
the
graph
work.
So
if
you,
if
you
have
a
chance
to
want
to
check
this
out,
you
can
see
there's
a
graph
queryable,
this
sort
of
mimics
almost
exactly
the
work
that
was
in
the
SharePoint
queryable.
A
We've
got
some
of
the
the
default
parser
and
so
forth
has
been
pulled
out
as
well
as
the
caching
stuff
has
been
pulled
out,
because
there's
nothing
sharepoint
graph
technology
service,
specific
about
caching
and
local
or
session
storage.
So
we've
pulled
that
out,
so
you
can
start
to.
If
you
use
your
imagination,
imagine
each
of
these
starting
to
become
their
own
little
packages
right.
A
So
we'd
have
sort
of
an
OU
data
package
where
maybe
you
want
to
use
some
of
our
OData
stuff,
but
not
you
know,
maybe
the
SharePoint
stuff,
for
example,
I
can't
think
of
a
perfect
scenario
there,
but
we'll
start
to
break
this
stuff
up
for
folks
as
well.
We've
broken
out
the
request
stuff,
so
the
pipeline
that
we
run
all
our
requests
through
is
now
completely
generic.
A
So
everything
gets
passed
into
this,
whether
it's
from
graph
or
from
SharePoint
need
the
graph
to
be
able
to
read
users,
mail
sure
right
now,
that's
a
limitation
of
how
we're
going
through
the
SharePoint
framework
client,
so
that
will
come
either
through
the
SharePoint
framework
client
or
as
we
expand
to
support
authentication
within
this
library.
So
you
know,
but
that's
great
feedback.
Does
the
graph
stuff
need
the
next
version
of
SharePoint
framework?
A
It
needs
the
version
that
has
the
graph
HTTP
client
available,
so
that
was
before
this
release
candidate
that
just
went
out
I'm,
not
sure
what
version
number
introduction
to
that
corresponds
to
this
I.
Don't
know
if
you
have
any
insight
there,
but
it
doesn't
need
the
absolute
latest
stuff
Chris
is
saying:
1
1
3
was
where
the
graph
HTTP
client
was
introduced.
So
we
would
need
that.
B
A
So
we
you
would
need
that
version
of
SharePoint
framework
to
use
the
graph
stuff
through
the
JavaScript
core
library
for
now,
for
this
beta
I
absolutely
understand
and
recognize,
and
got
called
out
immediately
that
we
weren't
supporting.
You
know
things
outside
of
SharePoint
framework
and
we
recognized
that,
but
we
needed
a
first
step
right.
A
We
needed
a
way
to
get
started
and
to
code
out
some
of
these
things,
so
you
can
see
if
you're
familiar
with
how
the
the
SharePoint
side
of
things
was
written
you'll
be
able
to
see
the
graph
side
of
things
to
understand
it
very
clearly.
It's
the
same
structure,
same
kinds
of
classes
and
the
same
ability
to
add
stuff
into
the
graph
so
add
retrieve
we're
working
on
all
that.
One
thing:
that's
really
great
and
I'll
point
this
out
in
case
folks
didn't
know
about
it.
A
The
graph
team
is
actually
put
out
a
graph
types
package,
so
you
can
grab
that
and
all's,
it
is,
is
just
all
the
typescript
interfaces
for
all
the
graph
objects.
So
that's
really
great.
So
if
you
need
that,
you
can
grab
that
that's
fully
separate
from
anything
we're
doing
in
P
and
P,
that's
from
the
graph
team,
so
grab
that
that
types
all
the
objects,
so
events
and
all
that
stuff,
it
actually
has
all
the
types
that
have
that
we
don't
even
support
yet
in
the
PNP.
A
So
it's
all
the
types
so
just
a
little
inside
baseball
for
me,
I
wish
I'd
known
about
that
about
three
hours
before
I
found
it
because
I
had
started
coding
out
all
the
types,
but
then
I
found
it,
which
is
awesome
and
so
check
that
out
whether
or
not
you're
using
our
stuff.
That
will
help
you.
In
terms
of
typing
your
stuff,
the
graph
team
has
released
a
library.
B
A
And
we
need
to
have
some
conversations
around
what
it
makes
sense
if
they're
gonna
be
right
in
the
library.
Does
it
make
sense
for
us
to
also
be
writing
in
the
library
and
have
those
kind
of
conversations,
but
so
that
will
come
we'll
see
the
question
of
where
is
that
Microsoft
slash,
Microsoft
graph?
That
types
is
the
the
package
name:
I.
Don't
actually
have
a
link
handy
for
the
website
for
that,
so
you
can
check
that
out
and
then
what
other?
A
A
You
know
and
really
let
people
grab
just
the
grass
just
the
pieces
they
need
without
maybe
you
know
having
them
carry
around
all
this
extra
weight
for
stuff
they're.
Never
going
to
use
again.
That
example,
if
I'm
only
doing
SharePoint
stuff
I,
don't
need
any
of
the
graph
stuff
to
be
in
my
project.
It's
just
extra
weight,
so
we're
gonna
look
at
doing
that
and
once
we
get
to
a
place
where
we
can
start
exporting.
A
A
A
We
can
get
you
know,
sort
of
bunch.
These
configurations
up,
you
know
as
they
as
they
make
sense
right
and,
as
we
potentially
would
add
additional
services,
we
would
have
configuration
areas
for
those
services,
so
that'll
be
out
there.
Another
thing
we'll
probably
take
some
of
these
different
providers
and
things
will
become
their
own
libraries,
but
again
with
an
eye
to
providing
all
the
same
functionality,
but
some
of
it
will
be
optional.
A
Imports
excuse
me
that
you
would
have
to
add
to
your
project,
so
we'll
have
much
more
on
this
as
we
move
forward
and
we'll
keep
everybody
very
much
a
prize
of
the
progress
we
make
and
then
we
will
see
you
know
how
this
shapes
up.
Like
I
said
we
have
some
internal
discussions
of
exactly
how
we're
going
to
present
this
out
to
the
community
where
it's
gonna
live,
etc.
A
So,
once
all
that's
decided,
everyone
will
know
will
provide
very
clear
guidance
on
moving
from
one
to
the
other
and
will
provide
very
clear
guidance
on
the
things
that
are
removed
and
put
into
their
own
packages
on
what
you
need
to
do
to
import
them
and
use
them.
As
you
do
today,
so
there
will
be
no
loss
of
functionality,
but
there
will
be
a
movement
of
functionality
to
other
packages
and
potentially
other
you
know,
patterns
or
ways
of
doing
the
same
things,
but
we
will
support
all
the
stuff
we
support
now.
A
So
that
being
said,
I'll
answer
any
questions.
It
looks
like
there's
some
heated
debate
about
something
was
really
cool,
but
now
everybody
hates
it
because
it
wasn't
in
the
type
space
which
is
a
fair,
fair
comment.
So
any
questions
on
what
we
just
talked
about
through
the
graph
work
or
anybody
have
any
questions
on
any
other
stuff.
We
discussed
today.
B
Sorry
I'm
at
least
I
was
just
started,
treating
the
issue
less
than
the
in
the
types
craft
types
anyway,
let's
see
if
we
can
actually
influence
on
some
of
this
stuff
internally
as
well.
Unfortunately,
craft
guys
are
in
a
completely
different
organization
as
the
SharePoint
guys,
so
we
can
directly
influence
them.
Maybe
I'll
chat
with
Yuna,
even
though
maybe
Anna
isn't
quite
up
to
date
on
this
level,
but
still
the
latest
and
latest
in
ignite.
B
B
Anyway,
if
there's
no
additional
questions
for
time
being,
we
do
have
a
following
meeting
coming
up
on
September
14th.
This
is
already
getting
pretty
close
to
date,
night,
which
means
that
we'll
prep
on
the
Ignite
demos
and
everything
else,
we
can
probably
show
you
anything
new
which
we're
planning
to
show
in
an
ignite.
B
Just
to
be
honest
on
that
one
I
might
be
actually
able
to
show
in
this
special
in
in
in
here
how
to
automate
full
site
deployments
and
everything
else
well,
we'll
see
we'll
see,
but
we're
getting
closer
and
closer
to
take
night
as
well
any
like
nation,
the
unique
night
there
will
be
announcements.
There
will
be
new
things
around
the
sharepoint
development
as
well
and
updates
on
all
of
the
things
which
is
great.
B
But
thank
you
everybody
for
joining,
and
now
do
I
remember
this
paul
and
related
at
all
and
eric
eric
is
not
on
the
call.
We
need
to
chat
at
some
point
on
random
on
the
on
our
common
community
things,
but
thank
you,
everybody
for
joining.
Thank
you
Stefan
and
Chris
for
your
great
demos,
good
stuff
and
they're,
showing
how
to
make
scenarios
to
work.
B
A
Thank
you
to
Chris,
thank
you
to
Stephane,
for
the
great
demos
really
appreciate
that,
and
as
always,
if
other
folks
in
the
community
have
stuff,
they
would
like
to
demo
just
get
in
touch
with
us.
I
think
it's
one
of
the
most
valuable
things
we
do
is
get
those
community
demos
out
there
for
everybody
to
see
and
share.
So
thank
you
to
all
of
you
for
attending
and
look
forward
to
seeing
you
guys
on
the
14th
of
September.
That's.