►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 20th of December. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
Demos:
- Luis Manez - React teams tab suggested members
- David Warner II - Combining Docker, SPFx & Office365 CLI
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
A
So
welcome
everybody.
This
is
SharePoint
Patterson
practices,
a
SharePoint
framework
and
JavaScript
special
interest
group.
So
this
is
the
bi-weekly
string
and
on
every
single
choice
that
we
basically
have
a
SharePoint
developer
community
call
every
other
week.
It
is
around
general
SharePoint
development,
which
is
everything
with
which
is
outside
of
the
SharePoint
framework
and
then
bi-weekly.
It
is
a
SharePoint
framework
and
JavaScript
development
and
the
other
one
is
more
on.
A
Let's
say:
PowerShell
provisioning
solution,
designs,
power,
apps
flow
and
all
that
kind
of
things,
and
this
one
is
more
on
the
SharePoint
framework
side
of
the
game.
Now
we
have
once
again
a
cool
set
up
of
functionality,
so
cool
demos
coming
up
today.
But
let's
do
a
few
random,
slides
and
I
do
have
some
updates
on
the
ownership,
one
framework
and
next
versions
as
well.
A
So
today
we're
going
to
talk
about
a
small
update
on
the
SharePoint
framework
from
the
engineering
side
which
equals
me
so
I
I
didn't
do
a
proper
introduction
but
I'm
from
the
SharePoint
framework
engineering
site.
So
I'm,
basically
updating
you
on
what's
happening
there,
and
then
we
do
an
update
on
the
BMP
jeaious.
Hopefully,
patrick
can
actually
talk
a
few
minutes
on
there
and
office
365
CLI
and
SPF
x,
reusable
controls.
So
do
we
have
a
nice
update
there
from
elio
ealer
is
gonna.
A
Do
a
quick
demo
on
two
new
controls
as
well,
and
then
SPF
X
yeoman
generator
from
Stephan.
So
these
are
our
open
source
initiatives
around
SharePoint
framework
and
JavaScript
development,
and
then
on
top
of
that
we
have
to
call
community
demos,
so
one
from
Louis
around
creating
a
react
team
stamp
using
SharePoint
framework
and
then
which
is
showing
you
suggestions
for
the
people
who
would
be
turning
on
the
crib
and
the
other
one
is
from
David
Warner
around.
A
How
would
I
actually
and
why
would
I
care
about
the
docker,
and
why
is
that
useful
for
SharePoint
framework
and
why
and
how
to
get
started?
It
is
actually
quite
easy
to
get
started
on
docker
if
you
actually
find
it
beneficial
for
you
and
let's
have
that
discussion
when
David
is
presenting
good
end
good,
just
a
quick
reminder
when
you're
joining
please
remember
to
be
mute
yourself.
A
So
there's
no
background
noise
just
in
case
so
that,
because
everybody
is
joining
here
now
by
the
way
before
we
go
to
the
most
likely
in
two
weeks,
potentially
we
might
have
actually
moved
over
to
the
Mike's
of
teams.
We
are
in
progress
of
making
that
transition
happen
at
some
point.
Apparently
max
of
teams
I
haven't
actually
tested
the
exactly
the
final
status
would
be
now
suitable
for
the
use
cases.
What
we're?
Having
that?
We
need
to
still
verify
that
for
the
before
we
actually
flip
over
now,
when
we
flip
over.
A
That
means
that
you
don't
have
to
worry
about
anything
in
if
you
have
downloaded
to
ICS
invite
from
the
from
internet.
That
has
an
a
kms
link
and
we
will
test
that
data,
a
kms
link
on
our
system
and
that
will
then
redirect
you
beyond
the
Skype
or
to
the
max
of
teams,
depending
again
on
the
on
the
target.
A
What
we
want
to
do,
but
that's
coming
relatively
soon
or
sooner
or
later
so,
we'll
see
when
we
get
there
and
we've
been
delaying
that
transition,
mainly
because
that
there
has
been
a
critical
functionalities
which
have
been
missing
and
the
Skype
is
actually
relatively
reliable
as
Skype
for
business
as
the
platform
as
well.
Now,
okay,
moving
on
so
a
quick
reminder
for
anybody
who
is
actually
turning
on
the
call
you
have
opportunities
to
participate
on
the
on
the
patterns
of
practices
and
special
interest
group
course,
and
so
you
can
our
the
community
in
general.
A
So
you
can
always
suggest
that
you
do
a
demo
around
SharePoint
framework
solution
or
JavaScript
development
areas.
So
please
be
me
or
Patrick,
or
anybody
from
the
core
team
if
you're
interested
in
actually
doing
a
live
demo
in
this
course,
we
do
have
now
a
few
upcoming
course
already
fully
booked,
but
we'll
catch
you
a
10
to
15
minutes
in
some
upcoming
schedule
whenever
it's
suitable
for
you
and
you
can
do
a
live
demo
on
your
functionalities
as
well.
A
Demos
are
super
important
because
I
think
demos
are
really
the
the
value
of
this
course
as
well.
So
surely
it's
good
to
know
what
has
happened
from
an
engineering
perspective
but
then
also
good,
seeing
the
live.
Demos
helps
people
to
understand
how
things
can
what
can
be
done
and
how
things
can
be
implemented
in
SharePoint
in
Cheryl.
Now
you
can
absolutely
a
demo
PMP
chase
in
an
application
in
this
course
as
well.
A
You
are
more
than
welcome
to
contribute
in
github,
so
with
the
pull
request
or
issues
and
then
also
remember
the
provide
feedback
or
input
in
general
and
as
an
example.
So
yesterday
there
was
a
small
itsy-bitsy,
well,
not
a
small
hiccup,
but
there
was
a
hiccup
actually
in
SharePoint
Online.
Luckily,
people
did
actually
provide
that
feedback
and
pink
to
us,
in
social
media
and
in
Twitter
and
in
Kitab,
and
we
were
able
to
fix
that
issue
relatively
fast.
We
do
apologize
on
the
under
any
inconvenience
that
might
have
actually
cost.
A
You
cost
you
in
your
tena
now
moving
on
on
things.
So,
let's
start
with
a
shape
on
framework
engineering
updates,
as
a
few
updates
from
here.
I
have
few
new
slides
here
as
well.
Just
a
reminder
again,
the
recommendation
is
available
from
AMS
SP
dev
ducks,
and
this
is
introduction
of
microsoft.com
platform.
Msdn
is
or
has
been
already
shut
down
on
100%
sure
what
has
happened
there
I
haven't
checked,
but
anyway,
all
of
the
relevant
documentation
on
SharePoint.
It
is
in
here.
A
And
I
would
say
four
decks
and
so
am
I
the
only
one
who's
having
out
who
can
hear
me.
So,
let's,
let's
now
double
check
this
one
so
clearly,
there's
some
audio
issues.
Okay,
cool
David
can
hear
me
and
Russell
can
hear
me:
okay,
cool!
Thank
you.
Thank
you,
okay,
so
for
those
who
can't
hear
please
reconnect
that
typically
should
result,
déjà
and
and
sure
we
are
heading
to
the
mics
of
themes
that
should
be
rough,
slightly
more
reliable
in
the
future.
A
Now
moving
on
on
things-
and
please
remember
them
yourself
now-
somebody
is
actually
joining
again
with
the
background
noise,
so
we
can
actually
send
this
no
surprises
over
there.
Excellent.
The
second
thing,
a
classic
client
which
we
are
we're
repeating
here-
is
that
please
remember
the
report
issue.
So
yesterday
a
small
hiccup
which
we
had
to
go
stapled.
We
were
able
to
fix
that
relatively
fast,
because
a
person
submitted
an
issue.
A
If
it's
an
on
deaf
topic,
if
it's
something
related
on
out-of-the-box
web
parts
or
or
something
else,
we
cannot
actually
take
that
input
to
you.
We
cannot
take
that
input
using
this
issue
list.
So
you,
those
kind
of
out-of-the-box
functionalities,
have
to
be
reported
using
the
tenant
admin
support
channels.
So
please
remember
that
as
well.
A
So
if
you
submit
an
out-of-the-box
functionality
or
issue
related
in
order
to
box
functionality
using
this
issue
list,
we
will
unfortunately
have
to
close
that
issue,
because
our
internal
process
doesn't
allow
us
reporting
that,
through
the
normal
channels,
now
so
new
stuff,
few
updates
on
the
under
usage.
So,
if
you're
interested
on
one
of
what
is
to
use
it's
on
SharePoint
framework,
is
people
actually
using
that?
Well
answer
is
yes,
if
you
haven't
heard
about
this
one
yet
so
the
growth
is
absolutely
unexpected,
but
not
unexpected,
but
it's
it's
growing
in
really
fast.
A
So
we
crow
now
571
percent
from
the
start
of
the
year
and
year-over-year
crow
is
508
percent
that
doesn't
make
sense.
There
has
to
be
a
type
out
there,
but
anyway,
so
the
growth
has
been
insanely
cute
and
it's
growing
all
the
time.
So,
every
single
week
we
are
basically
seeing
a
record
on
the
usage.
A
Since
the
last
time
when
we
had
the
call
so
SharePoint
framework
1.71
went
live
on
Tuesday.
This
was
a
relatively
minor
maintenance
release.
There
was
two
box
kind
of
a
nasty
box.
Well
now
the
nasty
box,
but
two
things
what
we
wanted
to
actually
address.
So
one
was
related
on
yarn
and
pian
MP
packaging
systems
and
the
second
one
was
related
on
dynamic
data.
So
if
you
were
using
those
things,
you
might
have
actually
run
into
those
issues.
A
If
you're
not
we're
not
using
those
things,
you
probably
don't
even
necessarily
have
to
upgrade
to
the
latest
version,
so
the
changes
are
relatively
small,
but
the
1.71
went
live
on
Tuesday.
So
if
you
are
now
downloading
or
considering
taking
the
latest
version,
you
will
get
and
the
the
1.71,
which
is
now
out
the
next
version.
Let's
talk
about
that
one
in
a
second
in
the
road,
much
line,
but
also
one
update
on
this
one.
So
SharePoint
starter
kit
has
the
new
version
available,
which
is
now
updated
to
1.7.
A
So
it's
not
in
1.71,
but
it's
in
1.7,
so
we're
looking
into
updating
that
1.71
relatively
soon.
But
there
is
a
new
version
related
on
SharePoint
starter
kit
version
1.4,
which
is
now
using
SharePoint
framework
1.7,
so
just
making
sure
that
everybody
is
aware
of
this
now
and
if
you're
not
aware
what
is
a
strap-on
starter
kit,
this
is
a
basically
a
nice
reference
to
lose
a
solution
with
to
PowerShell
commands.
You
can
install
this
to
any
tenant
and
it
will
demonstrate
what
is
possible
using
SharePoint
framework.
A
Everything
is
open-source,
there's
like
15
to
16
different
web
parts
and
extensions
and
an
even
sample
content
included
in
the
solution.
So
whenever
it
is
provisioned,
you
will
have
a
multiple
site
collections.
Multiple
example
news
multiple
functionalities
and
you're
able
to
demonstrate
what's
possible
with
the
modern
SharePoint
experiences.
Now
the
next
line
was
the
one
which
I
wanted
to
actually
spend
a
slightly
a
few
more
minutes,
so
just
to
explain
where
we
are
related
on
next
steps,
and
this
isn't
anything
written
not
that
traumatic.
All.
A
We
talked
about
many
of
these
things
already
in
the
past,
but
I
want
to
talk
to
at
the
Rotem
slide,
to
make
sure
that
everybody
is
up
to
date
on
what's
happening
so
SharePoint
framework
1.8
is
coming
out
on
the
first
quarter
of
2019,
so
a
first
quarter
means
between
January
and
March.
You
can
pretty
much
expect
that
nothing's
gonna
happen
in
early
January,
so
you
can
kind
of
estimate
where
this
is
plan
to
go.
But
if
there's
any
late
findings
that
might
be
later.
A
The
schedule
in
here
in
1.8
we're
planning
to
have
a
general
availability
of
likes
of
teams.
Development
with
SharePoint
framework,
so
that's
going
to
be
their
general
availability
for
single
part.
Update
ease
is
fun
to
be
there.
General
availability
for
isolated
webparts,
which
was
in
preview
right
now,
and
also
general
availability
for
provider,
hosted
solutions
in
SharePoint,
a
SharePoint
site,
which
basically
means
the
team's
applications
in
SharePoint
sign
and
then
also
general
availability
of
SharePoint
espy
HTTP
client
batch,
which
is
still
in
in
the
preview
mode
in
the
current
releases.
A
Now
all
of
this
is
still
subject
to
change,
so
basically
it
might
be
that
if
you
find
something
a
late-breaking
or
something
new
surprising,
we
might
still
delay
some
of
the
functionalities
to
1.9.
So
I
cannot
promise
that
all
of
these
will
appear
delivered
in
1.8.
But
that
is
the
intention
right
now
and
I
will
keep
on.
Obviously
updating
this
slide.
We
within
the
future
community
cause
as
well,
so
everybody
will
be
up-to-date
on
what's
happening
now,
other
topics
and
come
back
on
the
other
question
from
Rolla
FINA.
A
Second
other
topics
on
the
bubbling
under
as
the
store
and
App
Store,
apps
or
story
for
SharePoint
framework.
We
are
currently
working
on
that
one,
so
that
seems
to
be
progressing
potentially
already
in
the
first
quarter
of
this
of
next
year,
simple
framework
life
or
packets,
support
for
third-party
developers,
potentially
in
one
point
and
maybe
in
1.9,
and
then
others
were
looking
into
extending
the
SharePoint
framework
usage.
The
mites
of
teams
is
already
actively
adapting
that
so
and
potentially
we're
looking
into
doing
that.
A
Free
the
office
client
add-ins
as
well
so
that
work
is,
is
already
ongoing.
So
we're
looking
into
making
that
happen,
but
now,
if
that
will
happen
sooner
or
later,
we
will
need
to
start
to
think
rethinking
the
the
name
of
the
SharePoint
favor,
because
it's
no
longer
just
about
SharePoint.
It's
about
office,
365
or
Microsoft,
raises
to
five
customizations,
so
somebody
from
marketing
will
probably
then
make
a
decision
again
on
the
on
the
framework
name.
A
Now
there
was
an
interesting
question
on
the
on
time
window
from
Ralph
related
on
SharePoint
2016
and
the
support
SharePoint
framework
support
for
SharePoint
2016.
Let
me
be
super
clear
on
this
one
99.99999%.
Certainly,
we
will
never
change
the
supported
SharePoint
framework
version
for
SharePoint
2016
and
somebody
might
be
asking
why
not
answer
is
SharePoint.
2016
does
not
support
modern
experiences.
It
only
supports
SharePoint
framework
with
parts
on
a
classic
pages
and
SharePoint
2016
will
never
support
modern
experiences.
A
So
therefore,
we
cannot
actually
get
a
updated
version
of
SharePoint
framework
supported
in
to
SharePoint
2016,
so
just
to
be
super
clear
on
that
one
and
I
that
Steinke
route
for
the
feedback
as
well
on
the
sharepoint
2019.
That
is
supporting
one
point.
Four
point:
X
version
of
SharePoint
framework,
potentially
in
the
future,
we
might
change
that
version
support.
We
might
increase
that
as
part
of
SharePoint
2019,
CU
or
service
pack,
one
on
the
other
side.
A
I
think
we
have
open
asset
that
there's
no
service
packs
in
SharePoint
2019,
so
most
likely
that
will
not
happen
and
it
and
changing
the
the
supported
version
for
2016
or
2019
would
be
a
massive
massive
massive
testing
effort.
So
most
likely
we
are
unable
to
actually
get
that
investments
internally,
and
that
means
that
that
will
not
happen.
A
B
If
you
just
want
to
click
to
it,
I
don't
need
to
take
over.
So
again,
apologies
for
my
voice.
Today,
everybody
quick
updates
on
P
and
PJs
client-side
libraries
will
have
1
to
8
version
going
out
in
early
January
I
think
the
date
is
January
11th.
We
are
still
doing
beta
releases,
so
you
can
always
preview
what's
new,
those
are
generally
coming
out
on
Friday,
but
sometimes
at
other
times.
If
we
get
some
good
functionality
added
in
you
know,
I'll
push
out
a
beta
release
for
that.
B
So
that's
always
a
good
way
to
check
out
what's
new
and
what's
latest
through
those
beta
releases
and
again
their
betas.
So
maybe
don't
use
them
for
production,
but
they
are
a
real
release
right.
So
it
is
the
same
code
that
would
be
going
into
a
production
release,
so
do
give
them
a
try
and
it's
a
good
way
to
maybe
try
some
stuff
out
in
between
the
monthly
releases
again
wanted
to
mention
we're
starting
to
think
about
version
2.0,
so
bumping
that
major
version
means
we
can
break
stuff.
B
B
So
I've
added
a
roadmap
label
into
the
issues
list,
I
think
there's
three
things
out
there
right
now
tagged
with
that
and
happy
to
get
feedback
on
any
of
those
three
things
or
if
you
have
ideas
for
other
things,
certainly
would
love
to
hear
those
ideas,
not
necessarily
promising
we'll
be
able
to
do
everything
or
or
everything
exactly
the
way
folks
might
want,
but
definitely
want
to
hear
those
ideas.
So
we
don't
miss,
miss
any
feedback
or
ideas
and
again
one
of
the
stress
there's
no
date
for
this
2.0.
B
Yet
at
this
point,
we're
just
kind
of
in
the
planning,
Road
mapping
stage-
probably
well,
not
probably
sometime
in
2019
but
again
I,
don't
have
a
date
in
mind
yet
and
a
little
bit
will
be
when
I
have
a
chance
to
circle
back
and
spend
a
good
chunk
of
time
on
prepping
for
that.
But
so,
if
you
do
have
ideas
would
love
to
hear
them.
B
Excuse
me
and
then
I
want
to
always.
Thank
of
course,
we've
had
again.
This
month
of
December
a
bunch
of
great
contributors,
new
contributors
really
appreciate
that.
So
thank
you
to
all
of
you
who
are
new
contributors,
and
thank
you
to
all
of
you
who
are
returning
contributors.
It
really
makes
a
big
difference
in
the
amount
of
new
stuff
and
enhancements.
We
can
add
in
the
libraries
to
get
folks
from
the
community
contributing
those
pieces
of
code
really
helps
us
grow
a
lot
faster
and
make
things
better.
B
A
lot
faster
for
folks
did
want
to
highlight.
The
numbers
I
mentioned
last.
Call
that
I
hadn't
put
on
the
slides
but
for
November
was
the
first
month
that
PM
pjs
has
crossed
over
two
billion
requests
in
a
month,
went
through
the
library
and
that's
really
fantastic,
and
those
are
actually
just
the
ones
going
to
SharePoint
Online.
So
very
much
wanted
to
thank
everybody
for
that.
That's
a
testament
to
all
of
you
using
it
in
your
solutions,
using
it
with
your
customers
and
in
your
projects.
B
B
Links
down
there.
Well
one
link
down
at
the
bottom
and
a
hashtag
PNP
that
github
got
io
/
PNP
jeaious
will
get
you
the
documentation
for
the
PNP,
Jas
libraries
and
you
can
follow
the
hashtag
PNP
jeaious
on
Twitter,
as
well
as
myself,
at
mediocre
bowler
on
Twitter
and
I
generally
I'm.
Just
posting
updates
about
P
and
PJs.
You
won't
get
a
lot
of
spam
and
things
like
that
from
me,
and
there
was
a
question
here:
where
can
we
find
the
road
map?
B
That's
in
the
issues
list,
so
there's
issues
in
the
issues
list
tagged
with
a
road
map
label,
it's
kind
of
a
dark,
orangish
color,
but
you
can
check
that
out
and,
like
I
said
comment
on
any
of
those
existing
ones
or
if
you
have
other
ideas,
please
suggest
those
and
we'll
certainly
you
know,
be
interested
to
hear
what
you
think
and
see
what
we
can
incorporate
into
upcoming
changes
in
the
library.
So
that's
why
I've
got
thanks.
Everybody
again
appreciate
all
the
contributions,
all
the
feedback,
it's
really
making
a
difference.
So
thank
you.
Thank
you.
A
Thank
You
Patrick,
your
voice
is
carrying
on
really
well.
So,
let's
move
to
see
a
line
because
we
still
have
two
demos
coming
up
as
well,
so
on
the
CLI
slide
office.
Resist
if
you
see
a
line,
so
this
is
a
cross-platform
command-line
tool
for
managing
checkpoint
online.
So
if
you're
in
a
Mac
or
in
a
Linux
the
power
sharepoint
online
power,
shell
or
and
does
not
work.
A
Waldek
is
actively
also
building
a
cross-platform
PMPs
target
or
share
points,
not
a
get
setup
script,
so
that
could
be
then
used
also
in
an
on
Microsoft
platform
and
although
there's
a
high
interest,
knowing
what
kind
of
commands
people
would
like
to
see
in
the
office
365
CLI,
now
moving
on
on
things,
I
will
jump
on
the
SP
FX.
Reusable
components
and
I
think
we
have
earlier
on
the
call
elio
do
we
want
to
actually
talk
through
the
latest
version
and
then
again
do
it.
The
live
demo
under
under
Co
new
controls
as
well
yeah.
A
C
Hi
everyone
so
last
week
we
did
a
new
version
or
becomes
of
the
version
of
the
property
pane
controls,
property
paint
controls
are
the
ones
that
is
are
being
used
for
configuring.
Your
bad
parts,
major
changes
on
that
one
were
the
collection
data
control,
which
has
now
support
for
custom
field,
rendering
like,
for
instance,
the
custom
field.
Rendering
was
a
question
or
an
ask
from
Frank.
Are
you
from
the
search
web
part?
Marika
now
overrides
the
custom
rendering
of
some
filters?
C
Also,
we
added
the
functionality
for
sorting,
and
it
was
also
a
request
that
we
had
initial
list
and
then
there
were
some
bug
fixes
what
we
are
currently
working
on.
The
react
controls,
which
is
the
controls
that
you
are
going
to
use
inside
the
content,
some
of
your
web
parts
or
inside
your
extensions
is
version.
1
was
11
and
version.
1.7
will
contain
two
new
controls,
which
is
really
really
nice,
which
is
first.
C
The
map
control
which
you
can
already
see
and
I,
will
quickly
demo
that
as
well
and
a
short
control,
so
you
can
now
build
charts
with
the
PNP
controls.
Also,
some
enhancements
are
coming.
We
rewritten
the
people
picker
and
completely
from
scratch.
It's
now
doing
different
calls
to
other
API
endpoints
list
view
control
got
a
filtering
option,
so
you
can
now
filter
the
items
within
your
control.
So
much
much
is
coming
to
the
latest
version.
Hopefully
we
can
release
it
tomorrow.
C
So
what
you
can
here
see
is
a
quick,
develop.
A
quick
web
part
that
I
just
developed
with
these
new
controls.
Creating
about
these
controls
is
they
don't
really
require
a
lot
of
properties
and
a
lot
of
configuration,
so
you
can
just
copy
paste
the
snippets
from
the
documentation
and
Europe
to
go.
So
what
I
have
done
on
this
Web
part
is
I
used,
two
new
sharp
controls
and
one
nap
control,
so
the
map
control-
that's
the
one
you
can
see
at
the
top.
Of
course,
configuration
that
is
required
only
needs
to
have
a
title.
C
That's
up
to
you
coordinates
and
if
you
want
to
enable
searching
or
not
so
you
can
just
go
in
and
you
can
start
looking
for
different.
So
let's
say
that
we
want
to
go
to
New
York,
let's
search
and
now
I'm
in
New
York,
it's
using
OpenStreetMap
free
to
use.
So
that's
why
the
author
of
this
and
used
it.
So
let's
go
back
to
your
London,
for
instance,
and
all
working
fine.
So
this
is
a
really
nice
control
that
you
can
insert
in
your
webparts
charts.
C
There
are
a
lot
of
shirts
I
think
you
know,
beignet
I,
don't
know
if
you
are
I've.
If
I'm
saying
your
name
correctly,
you
know
sorry,
but
you
written
this
control
completely
from
scratch.
I
think
and
he
has
added
a
lot
of
documentation
around
these
controls.
So
all
the
controls
are
all
the
shards
that
are
available
are
all
documented
in
different
pages.
So
really
nice
way
for
you.
If
you
want
to
get
started
with
using
this
control,
then
you
see
all
the
possibilities.
So
we
have
it's
not
yet
in
the
public
documentation.
C
This
is
going
to
come
from
the
moment.
This
release
comes
out,
one
more
thing
for
the
property
pain
control.
If
you
really
want
see
it
now,
we
have
the
sorting
available
over
here.
So
you
can
just
say
we
can
change
the
sorting,
and
here
you
can
see
the
custom,
rendering
that's
my
custom
renderer
that
I
can
define
in
my
codes
over
here.
You
can
see
that
I
can
just
over
eyes
my
render
methods
of
the
control.
So
sky
is
the
limit
with
this
one.
C
A
C
A
Good
can
people
say
the
flights,
so
I
moved
back
on
the
slides,
Louis
Thanks.
Somebody,
yes,
excellent!
Thank
you
very
so,
and
we
do
apologize.
Some
of
you
are
saying,
having
some
issues
related
cup
again
we're
looking
into
moving
to
Mike's
of
teams
relatively
fast
from
next
calendar
year,
so
that
should
hopefully
increase
the
quality
of
the
of
the
course
as
well.
A
D
Can
you
hear
me
yep,
okay,
that,
okay,
so
on
Tuesday,
the
Microsoft
generated,
SharePoint
version
1.7.1
was
released
and
after
that
we
upgraded
the
product,
the
new
version,
7
PP
chef,
SPFs,
generator
version
1.5.2,
which
includes
a
new
generator,
that
is,
it
has
been
released
in
the
as
the
core
engine
to
create
your
new
projects
in
this
release.
I
also,
we
also
upgraded
the
office
365
CLI,
which
actually
does
the
checking.
If
your
project
is
currently
running
over
1.7
1.6
or
what
steps
you
need
to
do.
So
you
get
a
full
report
out.
D
What
you
need
to
do
is
to
upgrade
your
ship
and
project
to
the
latest
version.
We
also
updated
the
PMP
chess,
so
we
support
now
one
point,
two
point:
seven
version
in
there
and
the
PPS
pfx
property
control
that
eleo
actually
mentioned
with
the
version.
One
point
certain
point,
one
so
the
package
that
we
now
deliver
in
the
PPS
pfx
generator
at
under
under
late,
mostly
the
latest
releases.
So
in
future
we
actually
have
some
things
that
we
want
to
implement
or
add
to
the
bad
part
to
the
generator
in
general.
D
So
there
is
something
named
webpack
value
analyzer,
which
allows
you
to
identify
possible
flow
things
in
your
bundle
sizes
and
that
you
can.
For
example,
you
move
some
library
to
jQuery
and
this
and
analyze,
and
so
before
you
ship
it.
It
actually
shows
you
what
library
needs
what
space
in
your
package.
Another
thing
is
from
a
testing
perspective,
we
actually
looking
into
to
implement
chest
testing
workbench
directly
for
react,
GS
projects.
D
There
is
some
things
that
Andrew
Connell
already
did,
because
we
used
support
9,
SP
FX
to
different
react
versions,
so
we
had
15
and
to
react
version
16
in
the
future.
You
will
also
be
can
directly
use
it
when
you,
when
you
create
a
new
project,
can
directly
write
in
chest.
Another
thing
is
that
this
coming
in
the
future
is
the
style
in.
So
basically
you
can
do
some
landing
on
your
style
sheets.
D
This
is
something
that
Sergei
it's
okay,
if
currently
is
building
and
because
the
the
backpack
bendlin
bundle
analyzed
at
the
chest
framework
the
style
in
there
they're
all
for
for
all
projects.
Potentially,
we
need
to
make
some
architectural
updates
on
the
add
on
generator,
which
currently
handles
the
libraries
like
jQuery
to
have
actually
golfs
tasks
that
would
be
automatically
deployed
with
a
library.
You
know
for
examples
of
epic
bundle
analyzer
you
want
to
have
to
gulp
task
directly
in
the
calc
file.
D
You
want
for
the
styling,
that's
the
same,
and
these
are
the
things
that
are
coming
up:
I
think
somewhere
in
in
January
yeah.
So
if
you
want
to
get
the
latest
version,
just
do
MPM
install
chi
at
microsoft,
generator
SPF,
X,
there's
a
small
typo
in
there
and
for
more
information.
You
find
it
on
pimpy
github,
but
io
/
generator,
/s
prefix,
and
that's
all
for
my
size.
Okay,
how.
A
Do
we
harvest
f1
actually
missed
that
one
sorry,
the
TMP
means
that
was
completely
wrong.
We
need
to
fix
that
for
the
template.
That's
that's
weird.
So
ancestor
quickly
clarifies
that
the
BMPs
VFX
generator
extends
the
out-of-the-box
generator
which
is
coming
from
engineering
and
extends
that
with
an
open
source
aspect,
so
like
adding
a
angular
support
and
VJ
as
support
and
all
of
that
stuff.
So
this
one
is
using
the
art
of
the
box,
SP
FX
generator
under
the
hood,
so
it
is
100%
safe
to
use
this
one
and
then
based
on
your
selection.
A
It
is
extending
stuff
in
the
in
your
scaffolding,
so
support
for
B
and
angular
is
in
the
latest
versions
of
p.m.
PSP
FX
generator.
Now
the
installation
command
is,
however,
wrong.
So
Stefan
you
should
actually
have
the
installation
command
on
the
iron
window
for
the
ESP
FX
generate.
Now
we
are
three
minutes
above
delayed
on
the
targets
which
I
my
internal
socket,
but
let's
start
with
Louis
and
we
need
to
promote
Luis
as
a
presenter
first,
so
Luis
are
you
in
the
call,
hopefully
our
hi
guys
excellent,
you're
they're
huge.
A
A
E
So
sometimes,
when
you
create
a
group
is
not
easy
to
know
all
the
members,
all
the
people
that
you
want
to
to
add
to
the
group.
So
I
thought
it
was
a
good
idea
to
get
some
suggestions
and
using
the
the
graph
API.
So
if
we
jump
into
the
general
tab,
as
you
can
see
here,
there's
suggested
team
members
tab.
This
is
my
s
PFF
solution
and
I'm
getting
some
members
that
I
work
that
I
working
close
to
this
member.
E
E
With
just
one
click,
you
can
add
different
members
to
the
team,
so
I'm
getting
the
message
that
these
two
members
are
part
of
the
team
and
if
we
go
back
to
the
teams,
you
can
see
that
that's
a
couple
of
of
new
members
in
case
that
you
are
having
a
member
that
is
actually
already
amended
in
the
in
the
solution.
You're
just
gonna
get
a
warning
message:
oh
yeah,
the
one
that
was
added.
E
We're
gonna
take
a
look
to
the
container
in
a
minute,
but
note
that
one
of
the
big
things
is
that
the
solution
is
PFF.
Solution
can
work
in
in
cell
phone
as
well.
So
you
can
see
here
the
same
solution
in
a
SharePoint
site.
Again
we
can
see
here
that
there's
only
one
one
members
and
we
can
give
it
a
try
again
and
we
are
adding
the
new
members
and
if
we
refer
some
here,
hopefully
we
should
find
the
new
members
yeah.
E
So
it's
working
in
story
point
is
working
in
teams
and,
as
you
can
see
here,
the
different
is
that
we
are
not
in
a
team's
context.
Here
we
are
just
rendering
the
the
idea
of
the
of
the
group
instead
of
the
okay
name
of
the
of
the
things.
So
this
is
the
functionality
of
the
solution
and
we're
gonna
take
a
quick
look
to
the
code.
E
So
if
we
jump
into
this
one
studio
code
well,
first
of
all,
there's
some
small
pill
here
in
the
Endicott
five.
What
I've
done
is,
as
you
likely
know,
when
you
are
deploying
the
solution
into
teams
at
some
point,
you're
gonna
need
to
create
a
zip
file
with
this
three
function
here
in
the
in
the
themes
folder.
This
is
the
team's
manifest
and
a
couple
of
of
Falcone's
and
well.
You
have
to
create
a
zip
file
with
these
three
files.
If
you
want
to
to
deploy
into
theme,
so
happy
has
created
a
custom
gulp
task.
E
So
if
you
do
gulp
package
themes
here,
you're
gonna
get
the
zip
file
and
if
the
zip
file
already
exists
is
going
to
be
even
more
fun
and
sip
it
again
using
the
data
packets,
a
small
utility.
So
if
we
go
to
the
main,
the
entry
point
is
the
word
part
and
on
here
the
main
thing
is
that
we
need
to
get
to
Microsoft
in
this
context,
and
to
do
that,
we
need
to
use
the
only
need
method
and
in
they
only
need
what
we
are
calling
is.
E
The
Microsoft
teens
feel
that
we
have
in
DSP
effects
context
and
we
need
to
call
the
cave
context,
fans
field,
and
this
is
a
mess
in
function.
So
when
we
get
there
the
context
but
callback,
we
are
just
setting
this
private
fill
with
with
the
contest.
So
in
the
render
of
the
of
the
web
part,
we
are
just
rendering
we
are
component
and
we
are
passing
the
teens
context,
the
graphics,
TTP
clan
and
the
group
I
vehicles
are
this:
we're
gonna
need
these
fields
in
the
word
part.
E
So
if
we
jump
into
the
word
sorry
into
the
react
component,
what
we
have
here
is
just
a
couple
of
main
forces.
The
first
one
is
checking
that
producer
is,
is
the
owner
of
the
of
the
group,
and
this
is
just
on
calling
the
graph
API
again,
this
objects
endpoint
filtering
by
a
group
ID.
So
if
the
response
is
okay,
the
idea
is
the
owner
of
the
group.
Otherwise
the
user
is
not
it's
not
the
owner
and
then
to
get
the
suggested
people.
As
I
said
before,
we
are
calling
the
people
endpoint.
E
This
is
the
same
type,
for
instance,
is
doing
dev.
What
is
getting
you
suggested
people,
but
that
could
be
any
other
loading
that
we
can
apply
once
we
can
call
the
rough
API,
we
could
get
people
by
the
apartment
or
office
location
or
a
complex
functionality.
In
this
case,
we
are
just
calling
the
people
endpoint
and
returning
the
different
peoples
in
a
custom
interface.
E
So
when
we
are
rendered
the
component,
as
we
can
see
here,
it
sure
is
no
toner.
We
are
display
error
and
if
the
user
is
owner,
we
are
checking
if
we
are
in
a
team's
context,
or
not
just
to
show
the
title-
that
the
name
of
the
team
in
the
in
the
title
or
just
a
group
ID
if
we
are
driving
the
web
part
in
insert
point.
So
that
way
you
can
that
this
thing
is.
If
you
are
running
in
on
inside
themes
or
SharePoint
and
apply
to
your
project
at
least
we
have
another
custom.
E
We
are
component,
the
member
speaker
and
in
this
one
there's
a
bunch
of
code
actually
related
with
the
people
picker
office
public
do
I
just
because
you
need
to
do
to
code
the
functionality
that
you
wore.
When
are
you
sure,
if
selected
in
the
list
you
remove
the
user,
you
type
a
save
and
so
on?
We
are
not
gonna
go
through
all
this
code,
but
the
main
thing
here
is
the
action
to
add
the
selected
members
to
the
to
the
themes
or
the
group
and
to
do
that.
E
E
So
you
can
do
the
match
because
you
can
get
the
response
of
the
second
request
in
the
first
place
and
so
on
so
have
to
use
that
custom
ID
too
much
too
much
the
request,
and
then
we
are
using
the
client
to
post
to
the
bastion
point
and
we
are
taking
the
different
responses.
So
we
have
far
204
response.
The
user
was
added
successfully,
otherwise
something
went
wrong
or
just
maybe
the
user
is
already
it's
already
a
member
so
yeah.
This
is.
E
A
You
Louis
great
staff
and
a
great
demo
on
how
to
use
the
craft
API
is
together
with
SharePoint
framework
in
the
SharePoint
or
in
the
Microsoft
team.
So
it's
a
it's
a
nice
nice
sample
showing
quite
a
few
different
technical
concepts
and
it's
not
not
also
too
complex,
which
is
which
means
that
it's
a
good
sample
for
people
to
learn
from
which
it
occurs
as
well,
but
Thank,
You,
Louis
I,
think
it's
time
to
move
then
to
David.
So
David
you
are
a
presenter.
So
it's
matter
of
sharing
the
screen
all.
D
F
F
Take
it
away
cool
all
right,
so
for
those
that
don't
know
me,
David
Warner,
a
big
SharePoint
fan,
PNP
fans,
warts
fans,
so
here's
my
contact
information
and
my
blog
feel
free
to
reach
out
to
me.
If
you
have
any
questions
today,
we're
gonna
talk
about
office,
365,
CLI
and
combining
that
with
dr.
an
SPF
X.
Now
this
is
a
really
cool
strategy.
There's
a
lot
of
benefits
for
using
dr.
mystery
effects.
It's
one
of
many,
though
so,
don't
don't
mind
me
it's
it's
I'm,
not
saying
this
is
the
way
we've
got.
F
You
know
the
OG,
the
Original
Gangster
of
using
NPM
and
node,
and
all
that
on
your
machine,
and
you
get
the
as
was
highlighted
by
stuff
in
the
pnp
SPF
X
generator
docker
is
just
one,
so
you
might
want
to
look
into
it
after
this
and
we're
gonna
highlight
a
couple
of
different
things.
It's
not
gonna
go
too
in
depth.
Wallach
is
a
fantastic
blog
on
how
to
get
started
with
this,
so
we're
not
gonna
go
over
too
much
of
that
just
kind
of
see
how
we
can
use
it.
F
So
we're
also
gonna
see
how
to
include
CLI
inside
of
our
docker
strategy
in
the
docker
file,
we'll
initialize
it
and
it
will
show
a
quick
upgrade
for
a
web
part
alright.
So
what
are
the
benefits
of
using
docker
and
SPF
X
development
together?
So
it's
isolated
very
much
like
a
VM.
It
allows
you
to
keep
your
OS
clean
you're,
not
installing
node
or
yeoman
or
gulp
or
any
of
the
other
dependencies.
F
The
only
thing
you're
really
installing
is
docker,
and
that
allows
you
to
quickly
switch
between
versions
of
SPF,
X
or
any
other
dependencies
that
you
include
in
your
docker
image.
So
to
the
next
bullet
point
it's
very
fast
and
efficient
slight
weight.
Again
is
the
only
thing
that
you
need
to
install
on
your
machines.
So
it's
got
really
fast
startup
times
that
you'll
see
a
couple
of
benefits.
F
This
is
a
very
busy
slide.
We
could
almost
spend
a
half
an
hour
talking
about
just
this,
so
don't
let
it
don't
let
it
overwhelm
you,
though,
the
concept
here
is
that
doctor
uses
images
and
containers.
It's
very
much
like
VMs
images
are
non
editable
entities,
so
you
can
see
up
here.
I've
identified
a
one
6.0
non-edible
image,
which
includes
the
basic
dependencies.
F
F
So
what
makes
up
a
docker
image
you
use,
what's
called
a
docker
file
now
this
is
kind
of
like
the
ingredients
list
to
the
recipe
that
creates
your
docker
image,
and
you
would
then
compile
this
into
a
docker
image
that
you
can
store
on
your
hard
drive.
You
can
store
in
the
docker
hub
for
free
waldek
has
some
up
there
that
you
can
grab.
F
I
have
some
up
there,
that
you
can
grab
and
and
they're
very
quick
and
easy
to
get
to
it's
anonymously
accessible,
and
you
can
see
here
that
what
we're
identifying
is
our
necessary
ingredients,
so
in
this
case
I'm
running
node,
8,
11.3
and
then
I'm
identifying
all
the
necessary
dependencies
in.
So
we
think
great.
That's
all
we
need
to
get
started.
Fantastic
I
do
want
to
include
the
office365,
so
it's
an
NPM
package
I
can
just
install
it
after
the
fact,
as
a
local
guy
from
my
container,
but
that's
not
the
case.
F
It
does
have
to
be
a
global
installation,
and
so
it's
super
super
complex
and
the
way
we
do
it
is
you
just
simply
add
it
to
your
image
and
your
docker
file.
It's
really
really
super
easy
and
very
cool.
This
gives
you
full
access
within
your
docker
development
strategy
to
all
the
power
of
the
CLI,
and
so
we're
gonna.
We're
gonna
go
ahead
and
see
how
that
can
be
utilized
today
in
one
particular
method
for
upgrading
a
web
part.
So
let's
go
ahead
and
switch
over
here
now.
F
What
I've
got
is
I
pre
created
a
couple
of
web
parts.
We've
got
our
web
part
numero
uno.
What
part
part
do
and
so
we're
going
to
start
up
a
1.6
dot,
o
docker
container,
connected
to
a
docker
image,
and
this
is
going
to
have
all
of
the
1.6
dotto
framework
that
we
need
and
we're
gonna
go
ahead
and
add
a
third
web
part
to
that
to
this
solution,
so
I'll
go
ahead
and
copy
here.
I've
got
a
lot
of
stuff
pre
ready
to
go
now.
F
This
is
a
docker
command
that
instantiate
our
docker
container
again
a
lot
of
documentation
around
what
all
these
means.
We're
essentially
saying
go
start
my
1
6
0
image,
write
connect
a
container
to
it
and
I
want
to
point
it
to
the
files
that
are
living
on
my
hard
drive,
which
are
right
here.
Alright,
that's
the
the
basic
that
you
really
need
to
know.
The
rest
of
these
are
just
ports
and
docker
specific
commands,
so
I'm
gonna
go
ahead
and
enter,
and
it's
gonna
kick
us
in.
F
We
see
we're
now
inside
of
our
docker
container
and
and
just
to
know
that
we
have
our
16.0
I'm
gonna
go
ahead
and
do
a
search
on
NPM,
outdated,
looking
specifically
for
the
SharePoint
generator
and
it's
gonna
pop
up
and
tell
us
that
we
are
outdated.
We
actually
could
upgrade
to
1.7
to
know
so
we
know
we're
using
the
1.6
dot.
Oh
information,
that's
framework
files,
so
I'm
gonna
go
ahead
and
I'm
gonna
create
another
web
part
I'm
just
gonna.
F
F
We
will
call
it
when
it's
ready
doesn't
take
this
long
typically,
but
this
is
a
demo
there.
We
go
ok,
so
we
want
a
web
part
and
we're
gonna
go
ahead
and
call
it
web
part.
Thrice
is
nice,
and
so
we're
gonna
see
that
loaded
up
here
once
we
go
ahead
and
Scout
pulled
it
out,
hit
enter
I'll
just
leave
the
description,
no
JavaScript
framework.
F
What
is
that
that
looks
new
okay,
full
disclosure
engineering
team
didn't
create
this.
This
isn't
official
you're,
not
gonna,
find
this.
When
you
go
run,
your
npm
install
I
was
just
playing
with
this
last
night
and
having
fun
with
some
ascii
but
kind
of
go.
If
we
might
see
something
like
this
coming
soon,
hopefully
all
right.
Okay!
So
now
we've
created
our
webparts
Isis
nice.
You
can
see
again.
This
is
all
running
within
docker
I.
Don't
have
node
installed
on
this
machine
at
all.
F
On
my
on
my
root,
hard
drive,
so
I
am
now
loaded
in
1.6
we
created
what
park.
Bryce
is
nice,
and
so
now
what
we're
gonna
do
is
we're
going
to
jump
over
to
a
1.7.1
docker
image
that
created.
That
also
includes
the
CLI
in
this
one,
I
did
not
include
the
CLI,
so
if
I
try
to
instantiate
it
using
oh
three,
six
five,
it's
gonna
simply
tell
us
that
it
can't
find
it.
F
You
can
see
that
down
here
at
the
bottom,
so
let
me
go
ahead
and
exit
my
container
and
I'll
just
clear
the
screen,
so
we
have
up
top
and
I'm
gonna
go
and
paste
in.
This
is
exactly
like
the
last
container
instantiation
we're
just
booting
up
docker
to
say,
hey
point
to
these
files
here,
but
instead
this
time
use
my
docker
image
that
is
specifically
pointing
at
1.7.1,
and
we
know
it
includes
the
CLI
cuz.
F
F
There
you
go
so
now
we
want
to
instantiate
the
CLI.
It's
super
easy.
You
literally
just
type
O
365
and
wait
a
second
and
then
it's
going
to
instantiate
and
now
we're
inside
the
CLI
simple.
Is
that
now,
if
you
have
done
any
research
or
exposure
to
the
CLI,
you
know
that
one
of
the
features
one
of
many
is
called
the
project
upgrade
command
and
you
can
use
that
to
identify
what
your
solution
needs
to
do
to
upgrade
to
to
an
X
or
a
future
version.
F
In
this
case,
1.7
1.1
I
am
using
the
newest
version
of
the
CLI,
so
I
can
go
up
to
1,
SOT
7.1
and
then
what
I'm
saying
here
is
that
I
want
to
output
the
information
markdown
to
a
report
here
in
my
solution,
called
docker,
CLI,
upgrade
report,
and
so
we're
gonna.
Do
that
we're
gonna.
Take
a
look
at
that
real,
quick
to
see
what
benefits
it
brings
us.
So
I'm
gonna
go
ahead
and
enter,
and
it
just
rolls
through
it
does
output
everything
on
the
screen
for
you.
So
you
you
know.
F
If
you
really
enjoy
pain,
you
could
scroll
back
up
and
read
through
all
of
this
yourself
or
we
could
open
up
visuals
to
your
code
and
go
look
at
our
files
and
find
our
upgrade
report
right
here
and
go
ahead
and
use
vs
code
to
preview.
It
now
this
is
I
mean
I.
I
did
a
video
on
this,
but
to
me
this
is
still
just
super
cool
right.
We
see
we
ran
it.
F
Today's
the
20th
and
it
went
through
did
all
of
our
findings
and
it
highlights
everything
that
we
would
need
to
do
to
upgrade
this
particular
solution
and
all
of
the
web
parts
to
1.7.1
as
I
scroll
through.
You
can
see,
there's
all
kinds
of
stuff
and
you
could
just
copy
and
paste
each
one
of
these.
But
what
you
could
also
do
is
look
at
the
summary.
F
There
is
a
summary
here
down
at
the
bottom
that
you
can
just
go
through
and
copy
and
paste
or
save
as
a
file
and
execute
and
it'll
do
all
of
that
for
you,
and
so
we're
not
going
to
do
the
NPM.
Because
again
we
know
we
don't
have
time
for
that,
but
I
am
going
to
highlight
what
part
of
1.7.1
we
do
want
to
look
at,
which
is
that
it
creates
the
team's
folders.
We
saw
a
demo
of
that
moments
ago
with
Louis
right
and
it
creates
these
teens
folders.
F
Now
to
me
one
of
the
coolest
things
when
the
CLI
is
that
I've
got
multiple
webparts
in
here
and
typically
when
you
scaffold
that
you're
gonna
get
one
team's
folder.
This
is
intelligent
enough
to
do
a
couple
of
things
one.
It
knows
that
I'm
within
a
different
container
right,
so
it
it
knows
I'm
not
using
C
colon
blah
blah
blah
as
if
it
was
on
my
local
machine,
and
it
does
everything
perfectly
right
here
to
where
I
am
running
within
docker
and
then
in
those
hey.
F
You've
got
more
than
one
web
part,
so
we
can't
just
have
one
team's
folder
with
a
manifest
file,
because
it's
just
not
enough
space
for
everybody,
three
of
crowd.
So
if
I
were
to
copy
this
I
literally
just
need
to
copy
it
and
I
will
scroll
down
to
the
bottom.
We
know
it
needs
to
include
all
these
PNG
files
and
I'm
gonna
copy.
That
and
I'm
gonna
go
back
to
my
command
window
and
I'm
gonna
exit
CLI.
You
just
do
that
with
exit
and
then
I'm
gonna
exit,
doc
urban
stay
within
docker.
F
So
I'm
still
looking
at
my
solution,
and
we
want
to
look
right
over
here.
We
want
to
pay
attention
to
over
here
on
the
left
within
our
within
our
visual
studio
code,
I'm,
going
to
paste
what
I
just
copied
out
of
the
report
and
what
it's
going
to
do,
ideally,
is
it's
going
to
create
those
folders,
create
the
manifest
and
copy
the
P
and
G's
from
within
my
docker
image
into
my
docker
solution
files,
I'm
going
to
do
that
and
bam
there.
They
are
showed
up
perfectly
here's
the
manifest
here
is
the
tabs.
F
If
I
open
this
up,
let
me
go
ahead
and
close
this
and
close
the
preview
and
we
scroll
down.
We
can
see
everything
is
here
and
then
there's
a
separate
manifest
for
each
one
right,
and
so
it's
intelligent
enough
to
know,
and
if
we
go
over
to
our
files
here
they
are.
Here's
I
go
back
up
to
the
top
of
my
solution
there.
It
is
all
lives
on
my
hard
drive,
doesn't
live
an
image.
I
can
upload
this
to
github
or
whatever
a
file
repository.
F
We
we
need
or
want
to
have,
and
it
shows
you
the
power
of
combining
something
like
docker,
SPF,
X
and
CLI
together
to
work
in
some
perfect
harmony
and
again,
all
I've
installed
on
my
machine
is
docker
and
I'll,
just
kind
of
prove:
there's
no
wizard
behind
the
curtain.
If
I
exit,
docker
here
I'll
clear
my
screen
and
go
node
doesn't
even
know
it
exists,
my
machine
doesn't
even
know
it
exists.
So
again,
a
couple
of
options
here,
really
so
much
more
to
each
one
of
these
using
docker
using
the
CLI.
F
A
Excellent
excellent,
thank
you.
David
I
think
understanding
the
how
the
doctor
works
and
understand
the
value
of
doctor
is
super
super
important.
Now
there
was
a
question
related
on
docker
support
and
1.7,
which
we
had
apparently
some
issues
we're
still
working
on
that
one.
So,
unfortunately,
no
news
on
on
that
one
as
such,
what
good
stuff,
good
stuff,
really
good
stuff
cool?
A
That's
it
right
about
now
for
the
actual
community
call.
We
have
two
minutes
for
the
Advocate
Q&A
as
if
there's
any
super
super
super
super
super
urgent
questions
with
me:
David
Lewis,
Patrick
or
Elio
or
Stefan
miss
during
the
call.
Now
is
your
chance
for
two
full
minutes,
and
obviously
we
should
have
slightly
more
time
always
on
Q&A
on
this.
But
hey.
A
Can
anyone
share
a
blog
post
to
set
up
a
docker
I?
Think
probably
won't
X
block
posts
around
that
one
is
the
the
easiest
one
if
somebody
can
actually
easily
find
out
what
is
the
hex
code
for
the
exact
orange
tone
that
face
all
eyes,
so
you
can
you
can
go
and
have
a
look
on
the
static,
its
historical
of
theme,
colors.
You
can
find
it
from
there.
A
Thank
you
David
for
the
framework
talker.
So
that's
there.
Any
ad
hoc,
new
out-of-the-box
web
parts
are
quick
links
and
my
stuff
implements
what
wasn't
started.
That
is
absolutely
correct,
so
you
will
see
more
and
more
web
parts
coming
in
the
future
out-of-the-box
web
parts
in
the
future,
which
might
or
might
not
address
some
of
the
samples
what
we've
been
having
in
the
past,
and
that
is
obviously
by
design.
A
A
Microsoft
open-source
first
party
web
parts
from
Gotham
good
question
and
served
from
now
is
know
there
are
reasons
behind
of
that.
So
on
I
can't
actually
go
too
much
details
right
now
on
that
one,
but
there's
a
process,
logistics
and
other
reasons
why
we're
not
open
source
in
the
first
part
back
part
for
now
open
sourcing
them
would
just
an
example.
It
would
change
completely
the
whole
engineering
process.
It
would
mean
that
somebody
would
have
to
follow
up
on
one
out
contributions
from
the
community.
Somebody
would
have
to
merge
those
together
with
the
engineering
efforts.
A
We
would
have
to
have
multiple
Forks,
because
there
might
be
something
which
we
are
building
for
to
be
released
in
a
few
months
and
all
of
that,
so
it
would
be
a
pretty
significant
change
on
the
on
the
thinking.
How
do
we
do
development
now?
Some
point
in
the
future
who
knows
do
Ryan
do
Rio
is
asking
around
the
extra
parameters
around
the
director
that
around
craf
API
call
to
be
fair.
I
do
not
know
if
somebody
knows
an
answer
about
there's
an
extra
parameter
and
I
using
endoscope.
Thinking.
A
Also
that
there
is
a
separate
craft
community
call
which
is
happening,
I
think
on
first
Tuesday
of
every
single
month,
except
the
next
one
will
be
two
days
later
so
Thursday
on
the
week
of
I.
Think
it's
the
third
of
January
so
charming
take
or
somebody
else
would
be
the
right
person
to
answer
the
craft
questions
I
don't
want
to
actually
answer
them,
because
I
might
actually
say
something
wrong,
not
really
in
their
time
cute.
A
We
are
one
minute
onto
on
top
of
two
hours,
so,
let's
actually
close
up
so
the
the
recording
seems
to
be
a
relatively
successful.
This
time
there
was
a
small
hiccup
at
some
point,
some
point,
but
we
should
be
fine.
The
recording
will
be
out
in
the
YouTube
channel
within
24
hours,
aka,
MSSP,
PMP
or
SPF
of
videos
is
the
YouTube
channel
where
all
of
the
old
recordings
are
available
as
well.
A
Next
SP
FX
meeting
is
in
January
3rd,
so
this
is
Thursday
in
two
weeks
and
then
the
next
week
we
will
have
a
general
point
of
special
interest
group
call
on
to
27th.
That's
well.
If
you
please
remember
the
also
rest
and
take
time
for
your
family,
but
if
you
aren't
working
and
if
you're
interested
in
joining
the
call,
we
will
be
here
on
next
Tuesday
as
well
with
community
demos
already
queued
up
but
happy
holidays
have
been
new
year
depending
on.
Are
you
working
or
not?
I
don't
know
anyway.