►
Description
Recording of the community call from 4th of January 2018. Latest news on SharePoint Framework and on the SharePoint JavaScript community efforts. Unfortunately, we did lose some parts of the call due to Skype recording issues, but key pieces are included.
Details on covered content from https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-SharePoint-Framework-Community/m-p/142011#M4098
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
bi-weekly
special
interest
group.
This
is
our
meeting
for
January
4th
2018.
Welcome
to
2018
our
first
meeting
of
the
new
year.
Hope
everybody
had
got
an
opportunity
to
take
some
time
off
and
relax
a
little
bit
at
the
end
of
the
year,
and
we've
got
a
big
meeting
for
you
today,
so
just
to
cover
real
quick
for
folks
that
might
be
new
to
the
call
or
watching
these
recordings
for
the
first
time.
A
These
special
interest
group
meetings
are
part
of
the
larger
patterns
and
practices
programs,
and
they
were
begun
to
give
a
little
bit
of
a
better
focus
around
some
different
topic
areas
because,
as
we
grew
and
expanded,
our
coverage
we
weren't
able,
in
our
monthly
calls
to
cover
everything,
there's
just
too
much
to
cover,
so
things
were
getting
missed
and
it
felt
like
the
thing
to
do
is
to
have
more
meetings,
which
is
always
the
answer,
but
these
meetings
helped
us
focus
on
these
different
areas.
So
we've
got
this
one
you're.
A
In
now
around
client-side
development
and
SharePoint
framework.
We
also
have
one
on
the
manage
code
and
PowerShell
are
our
two
special
interest
groups
currently,
and
you
can
of
course
attend
one
or
both
or
all
of
our
meetings,
so
glad
to
have
everybody
here
today.
So
we
are
going
to
cover
an
open
discussion
around
the
SharePoint
framework,
client-side
development
patterns
and
latest
releases
in
SharePoint
framework.
We
talked
about
that
as
well.
Our
reusable
components,
office,
365,
CLI,
some
other
things
we're
doing
within
the
patterns
and
practices
program
around
client-side
development
and
then
as
well.
A
A
But
that
is
now
the
current
home
for
the
documentation
around
all
of
SharePoint
development,
whether
you're
looking
to
get
into
SharePoint
framework
and
are
new
to
that
and
looking
to
get
started
or
whether
you
need
to
do
stuff
around
client
side
or.
Oh
sorry,
around
manage
code
development
or
the
add-in
model.
The
provider
hosted
add-ins
check
that
stuff
out.
All
your
documentation
is
going
to
be
there
at
that
link.
A
So
without
further
ado,
our
agenda
for
today
we're
gonna
have
a
quick
update
on
the
JavaScript
core
component
update
on
SharePoint
framework
latest
news
and
update
around
the
office.
365
CLI
work
that's
going
on
and
then
update
around
our
patterns
and
practices,
reusable
client-side
controls
and
then
as
well.
We
have
a
community
demo
from
Eric
Brent,
zig
I,
hope
I
said
that
right
around
a
neat
little
pattern.
A
They
can
use
what
we're
working
on
within
their
day
to
day
either
development,
work
or
administrative
work
or
just
hoping
to
make
your
lives
easier,
which
is
our
our
goal
at
the
end
of
every
day,
so
some
opportunities
to
participate
both
in
this
special
interest
group,
as
well
as
the
larger
patterns
and
practices
program,
we
really
invite
anyone
from
the
community.
If
you've
got
a
SharePoint
framework
solution,
you've
written
this
could
be
a
web
part.
A
This
could
be
an
extension
to
come
demo
that,
on
this
call,
just
get
in
touch
with
us,
myself
or
visa,
and
we'll
get
you
on
the
agenda
and
we
really
see
a
lot
of
value
from
those
community
demos.
We've
had
some
amazing
ones
in
the
past
and
I
think
it's
really
an
opportunity
for
us
to
all
learn
from
each
other
and
honestly
I
think
it's
really
cool
just
to
see
what
folks
out
there
are
doing,
because
in
some
cases
it's
stuff
I
would
never
have
thought
to
do
that
ends
up
being
really
really
cool.
A
So
come
on.
The
call
show
off
what
you're
working
on
really
love
to
see
it.
You
can
also
contribute,
of
course,
on
github
either
to
the
core
JavaScript
core
libraries
we're
working
on
the
office.
365
CLI
is,
of
course,
open
source
as
well
and
then
as
well.
The
community,
the
reusable
controls
that
we'll
talk
about
here
in
a
little
bit,
are
also
open
source.
A
So
through
any
of
these
channels,
we
love
to
get
feedback
on
all
the
work,
we're
doing
across
patterns
and
practices.
We
get
both
good
feedback
and
you
know
constructive
feedback,
and
all
of
that
is
valuable
to
help
us
at
the
end
of
the
day,
produce
better
assistance
and
guidance
for
those
of
you
out
there
in
the
community.
So
thanks
to
everybody
that
has
provided
or
participated
in
any
of
these
ways
and
really
encourage
folks,
if
you're
on
the
fence
jump
in
and
give
it,
let
us
know
do
a
demo
on
the
call
contribute
on
github.
A
We
really
couldn't
be
doing
this
without
all
of
your
support
out
there
in
the
community,
so
update
on
the
JavaScript
core
component.
So
short
update,
I
took
some
time
off
at
the
end
of
last
year.
So
not
not
a
lot
happened
in
the
last
couple
weeks,
but
I
did
want
to
give
folks
an
update
on
where
we're
at
so
work
continues
on
those
at
PMP
scope.
Libraries,
as
I
mentioned
on
the
last
call,
those
are
essentially
code
complete
at
this
point
code
complete
in
the
sense
of
ready
for
release.
A
Obviously,
nothing's
ever
percent
code
completes
in
terms
of
new
features
and
things,
but
aiming
for
a
January
15th
release.
I'm
gonna
try
and
aim
aim
that
release
to
go
with
the
SPP
and
PJs
release,
which
is
also
for
January
15th.
Really,
the
only
blocker
for
the
release
is
documentation,
as
I
mentioned
before
I
think
I'm,
probably
one
of
the
slowest
documentation
writers
in
the
world,
but
I'm
working
on
that
and,
of
course,
if
folks
want
to
jump
in
and
help
there.
Please
do.
A
You
know
contribute
on
the
docs
and,
if
you're
unsure
how
to
do
that,
just
reach
out
and
I
will
definitely
get
you
involved
and
I
didn't
want
to
mention.
There
was
some
talk
on
the
last
call
around
timelines
and
I
want
to
I
want
to
talk
about
that
again
briefly,
just
to
hopefully
avoid
any
confusion,
and
we
talked
about
so
when
we
release
the
new
at
PMP
scoped
libraries.
A
We
are
going
to
give
then
a
timeline
on
SPP
and
PJs
for
six
months,
where
we'll
continue
to
support
that,
and
then
our
work
is
going
to
shift
over
after
those
six
months
to
just
be
on
the
pnp
scoped
libraries,
meaning
the
new
features
and
things
we
add
are
going
to
go
there
now.
This
only
applies
to
the
client-side
libraries.
This
has
nothing
to
do
with
powershell,
see
some
SharePoint
framework,
reusable
components,
office,
365,
CLI
or
anything
else.
A
A
It's
going
to
remain
in
github
is
going
to
remain
published
on
NPM,
so
none
of
your
existing
work
will
break
and
we
will
always
be
open
to
if
folks
in
the
community
put
together
pull
requests
and
want
to
submit
those
to
the
SP,
P
PJs
library.
That's
absolutely
encouraged
and
wonderful
and
you're
welcome
to
do
that,
though.
We
wouldn't
also
encourage
folks
for
new
work.
So
then
look
at
putting
that
into
the
at
P
and
P
scoped
libraries
into
whichever
library
it
might
be
appropriate.
A
There's
the
SharePoint
one,
the
graph
one
or
or
any
of
the
supporting
libraries
so
we'll
continue
to
discuss
this
I
want
to
be
very
open
and
kind
of
upfront
about
what
we're
doing
so.
Nobody's
really
surprised,
but
just
wanted
to
mention
that
again
and
then
SPP
and
page
is
quick.
Like
I
mentioned,
release
scheduled
for
January,
15th
and
I
appreciate.
We've
got
some
good
issues
and
some
good
feedback
coming
on
that.
Keep
that
coming
in
really
appreciate
that
that
helps
us
fix
bugs
and
make
things
better
for
everybody.
So
appreciate.
A
B
B
Still
doesn't
work
in
rest,
so
we
gotta
keep
it
there
hold
still.
So
what
I
got
here?
My
left
side
is
a
normal
SharePoint
page.
It's
innovation,
sorry
for
hats.
The
right
side,
I
got
my
ID.
So
first
thing
I
will
make
the
move.
I
go
to
you
something
I
called
tick.
Tick
is
a
tool
we
made
that
work
that
we
use
for
for
testing
things
and
running
things.
It's
kind
of
neat
so.
B
B
B
So
it's
that
simple,
just
work,
testing
and
hacking-
and
you
can,
we
can
say
it
faster,
it's
kind
of
neat,
but
not
the
thing
I'm
going
to
show.
So
what
I
need
to
do
get
now
is
that
the
JSON
stuff?
So
we
got
three
functions
that
we
talked
about
in
Victor,
which
are
used
to
help
us
using
JSON
and
help
us
compliant
JSON
with
with
BMP
and
other
libraries.
B
C
B
B
And
then
we
need
to
load
the
web
still
same
old
JSON
code.
There
comes
the
cool
thing
you
can
now
do
await
and
execute
the
context,
and
now
the
web
should
be
loaded
yay
so
that
that's
the
whole
magic
magic
thing
and
it
helps
us
with
wrapping
JSON.
So
we
also
got
a
couple
of
other
methods.
We
can
get
items.
B
B
B
B
Yeah,
because
also
to
our
a
so,
we
don't
need
to
our
in
longer
remove
that
as
well
and
it
works.
Nice
did
I
like
to
to
show
how
how
the
code
really
looks
in
more.
First
of
all,
I
would
like
to
show
how
how
you
might
think
that
the
load
will
execute
every
time
because
of
the
way
it
looks
so
I
do
load,
web
and
load
items.
B
If
I
now
go
to
network
flare
it
and
run
the
code,
you
would
expect
to
process
periods,
but
it
doesn't
do
that
it
uses
promises
in
owl
if
I
hack
away
so
it
will
actually
run
only
once
until
the
next
height.
If
I
like
this,
it
will
probably
be
too
big.
Wait
this
little
bit.
You
know:
okay,
it's
a
bit
blue
on
the
run,
once
I
can
prove
that
it
works
by
thinking
it.
D
B
Yeah,
you
can't
vote
and
it
does
only
one
request.
Paratus
value
I
would
like
to
show
the
help
people
for
execute.
It's
this
part.
That's
all
it's
hard
to
see
now,
but
basically
all
executed,
Korea
I,
think
and
it
will
resolve
and
reject
it,
and
then
lastly,
I
will
do
one
other
tests
just
to
show
how
cool
Jason
is.
B
E
Indeed,
so,
from
a
ship
of
engineering
perspective,
quick
update
on
the
ship
on
framework,
so
last
time
we
had
a
community
call
in
the
PI
weekly
schedule
and
21st
of
December.
So
technically
it's
pretty
obvious
that
nothing
super
major
has
happened
between
the
21st
of
December
and
the
4th
of
January,
but
we
have
been
actually
working
on
something
which
I
promised
to
show
in
two
weeks
ago
in
the
community
called
weeds,
moss
around
the
craft
and
the
future
capabilities
and
SharePoint
framework.
E
Before
we
go
there
like
nation,
when
we
started
the
community
call
just
a
reminder,
all
of
the
SharePoint
development
documentation,
not
just
the
shape
and
framework.
Everything
which
is
relevant
has
been
moved
to
the
doctored,
my
stuff
comm
platform,
and
please
please,
please,
go
and
check
this
out
and
give
us
feedback
also.
E
No
I
think
the
most
important
interesting
topic
of
today
is
actually
the
craf
call,
and
my
animation
in
here
is
actually
slightly
messed
up.
Maybe
let's
see
now
the
the
craft
access
all
the
third
party
API
access
works,
and
this
is
something
which
were
not
going
to
be
released
relatively
soon
as
part
of
SPF
X.
E
One
point,
four
point:
1
or
1.5,
we'll
see
how
the
the
versioning
will
be
free,
Kurt
out
I
can't
give
you
an
exact
date
or
a
week,
but
it's
it's
in
matter
of
days
rather
than
weeks
when
this
one
will
be
available
for
preview
usage
in
the
SharePoint
or
not.
Now
and
we've
been
kind
of
a
in
the
Ignite,
and
during
the
autumn
we've
been
promising
that
pretty
soon
you
will
have
additional
scopes
in
Microsoft
graph.
What's
beauty
and
what's
super
beautiful
within
this
design?
E
Is
that
it's
not
only
for
crafts,
it's
also
for
other
stuff
as
well.
So
in
the
future,
you
have
unlimited
scopes
in
Microsoft
graph,
except
the
Tanakh
administrator
will
actually
manipulate
and
make
those
decisions.
What
are
the
scopes
and
what
are
the
permissions
for
the
sharepoint
online
client
object,
and
so
the
chapman
online
client
is
something
which
we
will
provision
automatically
for
every
single
other
ad
application,
and
that's
the
one
where
we
grant
additional
scopes.
E
Additional
permissions
and
tenant
administrator
essentially
is
doing
that
and
we
give
you
powershell
commandlets
and
the
manipulators
will
give
you
a
powershell
commandlets
to
request
those
and
then,
whenever
there's
a
a
sharepoint
framework
solution
web
part
or
a
extension,
it
doesn't
really
matter
when
it's
actually
calling
when
it's
actually
executing
something.
There's
new
as
your
ad
client
or
crap
ms
craft
client,
which
is
aware
of
those
tokens
and
scopes
which
have
been
granted
for
this
particular
object.
E
So
this
is
really
really
obviously
crate,
because
it
enables
us
in
a
safe
way,
call
third-party
third-party
ad
ice,
so
Web
API,
so
it
reaches
the
holy
crao
of
sharepoint
online,
so
being
able
to
securely
call
a
web
api
in
a
way
that
it's
it's
all
indicated
and
authorized.
The
second
thing
is
that
this
enables
you
to
actually
have
access
or
enables
you
to
configure
additional
scopes,
for
example
from
acts
of
crime.
E
So
if
your
solution
requires
a
certain
set
of
additional
permissions
like
details
allotment
around
the
personas
within
your
organization,
you
can
actually
do
that
using
the
new
design,
which
is
then
available
relatively
soon
and
again.
This
goes
to
preview
relatively
soon.
There
will
be
some
ugly,
you
is.
There
will
be
some
things
which
we
need
to
still
saw
down
during
the
preview,
but
the
preview
is
already
a
great
start
to
get
to
learn,
what's
actually
coming
and
then
it
will
go
worldwide.
E
Availability
later
this
spring
now
to
be
able
to
actually
show
you
in
practice
how
this
works,
we
actually
are
delegated
this
responsibility
for
Paulo,
who
can
actually
start
sharing
his
screen
and
did
a
live
demo.
Paulo
has
been
helping
on
us
on
the
documentation,
support
and
making
sure
that
the
basics
are
working
before
we
go,
live
and
release
this
for
a
wider
audience.
But
Paulo
can
you
share
your
screen
and,
yes,.
C
E
E
C
Know
I'm
a
web
designer,
so
that's
the
result
just
kidding
of
course.
Well.
This
is
a
client-side
web
part
which
uses
these
new
capabilities
that
you
were
talking
about
a
few
seconds
ago.
So,
through
these
client-side
web
part,
we
can
use
the
micrograph
to
search
the
users
in
the
current
tenant
based
on
their
first
name
last
name
or
display
name,
and
we
can
get
back
the
list
of
all
of
the
matching
users.
C
C
Because
now,
with
the
one
point
four
point
one
or
whatever
version
it
will
be
of
the
SharePoint
framework,
we
will
have
two
different
client
types
that
we
can
use
to
consume
a
is
ready
and
secure
the
applications.
The
first
one
is
to
consume
any.
If
you
ready
secured
application.
The
second
one
is
to
use
the
graft
client
within
the
SharePoint
framework.
So
let
me
try
to
explain
you
how
these
demo
works.
So
let
me
switch
to
the
source
code
of
my
solution.
This
is
a
sharpen
framework.
C
A
client-side
web
part
built
using
react,
but
this
it
doesn't
really
matter
what
kind
of
development
framework
you
use
and
my
client
side.
What
part
is
using
the
client
mode
property
in
its
own
properties
to
define
what
kind
of
client
we
want
to
use?
But
the
key
point
of
this
solution
is
the
react
component.
C
In
fact,
in
the
area
component,
aside
from
the
UI,
we
have
a
primary
button
built
using
office
way
fabric
in
which
we
fire
a
search
method
in
which
we
can
select
if
we
want
to
use
the
azure
ad
client
or
the
graft
client,
and
we
have
two
different
procedures
that
we'll
use
each
of
the
available
options.
First
of
all,
whatever
will
be
your
choice,
whether
you
will
use
the
AAP,
HTTP,
client
or
the
graft
client.
You
will
have
to
be
declare
in
your
solution.
C
What
permissions
you
want
to
have
in
order
to
run
your
solution
and
in
the
package
solution
that
JSON
file
in
the
config
folder.
We
have
a
new
section,
the
Web
API
permission
request
section
through
which
we
can
define
an
array
of
permission,
scopes
that
we
need
to
have
in
order
to
run
our
solution.
Keep
in
mind
that
this
setting
is
at
solution
level.
So
if
you
will
have
multiple
clients
that
will
part
with
different
requirements,
you
will
have
to
collect
all
of
the
permission
requests
at
once
in
this
place.
C
Now,
once
I
declare
this
option
in
the
package
solution
and
once
I
package,
my
solution
and
I
deploy
the
solution
on
the
target
up
Catalan
in
my
tenant
I
can
grant
the
permission
that
this
solution
is
requesting
for
using
the
admin
UI,
which
is
still
in
preview
as
like
as
all
of
the
functionalities.
We
are
talking
about
right
now
in
the
new
SharePoint
central
administration
in
SharePoint
Online.
C
So
whenever
you
configure
a
permission
on
this
side-
and
you
approve
a
permission
on
this
side,
you
will
have
in
the
age
I
decide
the
same
permission
available
under
the
permission
sections
in
the
security
settings
of
the
SharePoint
Online
client
applications.
Once
you
have
the
permissions
properly
configured
for
your
solution
in
your
code,
you
can
simply
say:
ok,
if
you
want
to
use
the
aad
HTTP
client
object,
you
just
need
to
create
a
new
instance
of
that
type.
D
Both
everything,
a
document
with
some
screenshots,
if
you
don't
like
it,
feel
free
to
contribute
or
create
some
issues
so
that
we
know
what
you
want
and
how
we
can
improve
some
things.
An
amazing
figure
that
we
implemented
is
the
field
term
picker,
which
allows
you
to
go
to
a
taxonomy
term
set
and
select
a
particular
term.
You
don't
have
to
do
any
plumbing.
Everything
is
arranged
for
you.
The
only
thing
you
have
to
do
is
provide
right,
English
like,
for
instance,
which
title
which
initial
values
and
so
on.
D
That's
it
all
the
SharePoint
calls
or
the
API
calls
that's
partly
done
by
the
control
itself.
So
these
are
the
property
pane
controls.
Besides
that,
they
also
have
the
react
controls
the
react.
Controls
are
the
ones
we
are
going
to
use
in
the
comfort
zone
of
our
web
bar
or
any
other
SharePoint
framework
solution.
So
what
we
have
right
now
is
the
file
type
icon
in
combination
with
the
ListView,
a
placeholder
which
was
in
the
beginning
available
in
SharePoint
framework,
but
it
was
removed.
D
So
we
moved
it
over
to
the
reusable
control
section
so
that
you
can
use
the
placeholder
control
if
you,
for
instance,
create
a
new
control
and
you
still
need
to
do
some
configuration.
You
can
use
that
placeholder
control
as
the
configuration
part
of
your
web
part,
so
that
person
knows
that
it
still
needs
to
be
configured
and
once
that
is
configured
it's
going
to
be
removed.
So
if
you
copy
this
code,
then
you
can
have
a
report
like
this.
Let
me
go
to
my
head.
D
H,
you
see,
I
have
configurable
your
available
and
now
I
can
select.
This
everything
you
see
here
is
built
with
TMP
controls,
so
I'm
not
using
any
normal
control
set.
So
this
is
a
list
picker.
The
only
thing
I
have
to
specify
is
which
list
I'm
interested
in
so
I
might
have
interested
in
normal
lists
or
document
libraries,
so
I
just
I
want
to
have
document
and
the
document
library
do
you
want
to
toggle.
This
is
a
normal
total,
but
it
also
has
an
over
card
available.
D
So
you
can
add
some
extra
information
once
we
apply
this.
You
see.
This
is
a
list
view
control.
Another
great
control
we
added
is
the
change
bulb
of
our
title.
So
you
see
here,
I
can
immediately
change
the
title
of
my
webpart
I'm,
just
typing
it.
If
I
click
on
publish
this
title
would
be
sets.
When
I
go
back
to
my
edit
modes,
this
web
marcantel
can
be
changed
again.
D
Without
actually
opening
the
property
thing,
so
this
is
all
what
you
can
find
in
these
two
modules
or
in
these
two
libraries,
so
free
free
to
test
them
out.
It's
done
some
feedback
in
on
get
up
everything
in
government.
If
something
is
not
clear,
just
file
an
issue
and
we
respond
to
it
better
back
to
you.
E
And
unmuting
myself,
that
leaves
us
three
minutes,
so
let
me
actually
go
to
the
slides
and
we
can
close
up.
So
there
was
a
unfortunate
failure
on
my
side,
so
my
skype
actually
completely
crass
but
apparently
I
was
able
to
save
the
start
of
the
call
the
recording
of
the
call.
So
luckily
that
didn't
take,
we
didn't
fail
completely.
E
So
there
was
there's
an
interesting
question
on
the
atheists
set
up
now
from
Joel
and
everybody
else.
So
we
had
I
there's
nothing.
I
can
actually
share
on
this
one
right
now,
but
the
reality
is
that
we
have
thousands
or
millions
of
add-ins
registered
in
SAS.
So
it's
not
like
this
is
going
to
be
shut
down
without
without
any
notice
for
anybody
in
SharePoint,
Online
and
clear
replacement
method.
For
that
one.
E
So
you
know
there
will
be
more
news,
we'll
be
more,
let's
say,
clarity
on
what
does
it
mean
in
practice,
but
we're
not
really
obviously
so,
let's,
let's
think
about
this,
and
in
practical
terms,
in
SharePoint
Online,
we
have
tens
of
millions
of
customers
in
SharePoint
Online.
We
also
have
millions
of
atoms
installations
and
registrations
in
SAS
would
Microsoft
be
stupid
enough
to
just
check
down
the
ACS
for
all
of
these
customers.
Answer
is
no
sir,
should
be
ok.
E
Then
we
are
working
on
on
the
clarity
on
the
end
result
and
the
story
on
on
behind
of
that.
But
I'll,
that's
a
good
point.
Maybe
that's
could
be
a
one
topic
to
talk
about,
potentially
and
in
the
channel
SharePoint.
A
special
interest
group
call
just
to
get
people
up
to
date
on
what
it
is.
How
open
source
are
the
reusable
controls?
They
are
completely
open
source.
So
the
intention
is,
hopefully
we
get
additional
people
contributing.
E
We
do
have
already
multiple
people
contributing
so
Alex
from
SharePoint
the
list
as
an
example
elio
there's
an
idealist
list
of
ideas
in
the
key
table.
So
if
you
go
to
the
key
tab
list
for
the
for
the
issue
list,
there's
an
idea
if
you're
looking
into
contributing-
and
you
don't
have
an
idea-
we're
also
looking
into
harvesting
more
and
more
stuff
from
the
first
party
controls
and
first
party
webparts,
so
get
that
stuff
more
and
more
available
through
these
controls.
So
you'll
see
more
and
more
stuff
in
these
controls
in
the
future.
E
Hopefully
people
are
happy
and
give
us
feedback
so
on
on
these
things.
So
we
understand
that
there's
an
interest
and
there's
an
interest
on
them,
so
we
know
that
we
could
keep
on
investing
on
them
gute
and
what
else
we
are
hitting
the
hour.
Thank
you
for
every
person
who
demonstrated
something
today,
I
do
apologize
on
my
behalf.
E
Apparently
Skype
was
partly
site
way,
so
I
was
unable
to
do
the
demo
Thank
You
AC,
for
trying
to
do
the
demo
on
cell
phone
no
variation
on
the
fact
that
there
was
a
unexpected
issue
on
your
side
as
well.
It's
a
demo
machine
or
sorry
def
machines,
so
your
setup
is
slightly
different
than
would
have
been
on
my
side.
Let's
do
the
demo
on
that
one
next
week,
but
I
think
Patrick
I
think
we
are
good
to
go
on
this
one.
So
I
have
the
recording,
saved
I.
E
Think
I
missed
like
two
seconds
from
the
earliest
part.
I
will
cut
all
of
the
the
unnecessary
chat
on
the
unnecessary
wait
times
on
the
video
when
I'm
processing
that
and
we'll
get
the
video
out
within
24
hours
in
our
BMP
YouTube
channel.
You
will
see
also
a
a
tweet
from
me
Patrick
and
office
div
and
office
staff
p.m.
page
waits
when
the
video
is
sound
but
I
think
that's
it
happy
2008
and
2018
year.
It's
4th
of
January
will
thank
you
for
joining.
Hopefully,
the
stuff
is
interesting.
E
Please
keep
on
giving
us
feedback
I
go
to
the.
If
you
find
an
issue
in
SharePoint
framework.
As
an
example
go
to
the
SB
dev
docks,
let
us
know
where
Microsoft
is
failing.
What
is
good,
let
us
know
where,
where
we
are
whatever
you
need,
because
unless
we
know
we
can
fix
it
so,
but
thank
you,
everybody
and
let's
stay
in
touch.
The
next
special
interest.
Good
call
for
SharePoint
framework
is
on
January
18th.
We
have
no
idea
Patrick
right.
What
are
we
going
to
present
on
the
18th?
Probably
at
least
office
365
CLI.