►
Description
Details on the covered topics from https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-JavaScript-Special-Interest/m-p/46551
A
Hello
and
welcome
to
the
weekly
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
called
as
februari
16
2017
flying
through
2017
so
far,
let's
go
ahead
and
get
started
so
just
for
folks
that
might
be
joining
the
call
for
the
first
time
or
a
quick
refresher
for
folks
that
have
been
here
before.
This
call
is
the
special
special
interest
group
for
a
SharePoint
framework
and
JavaScript
client
side
development,
10am
and
sometimes
does
time
in
in
my
timezone,
so
I'm
not
good
enough
to
do
the
math
and
go
through
all
the
time
zones.
A
But
we
sit
under
the
larger
patterns
and
practices
program
which
now
as
part
of
SharePoint
engineering.
So
that's
a
very
exciting
development
that
happened,
though,
six
or
so
months
ago.
Now
so
that's
been
going
on
for
a
while
and
that's
given
us
a
little
bit
tighter
integration
with
the
engineering
teams,
and
so
it's
really
helped
bring
kind
of
a
their
better
channel
of
the
feedback
from
this
group
and
the
rest
of
patterns
and
practices
back
to
engineering
and
then
getting
some
fresh
information
out
of
engineering
to
these
calls,
which
is
really
fantastic.
A
So
we
focus
on
two
main
areas
in
the
calls
first
in
SharePoint
framework
and
the
client-side
patterns
and
things
that
go
along
with
that.
So
that's
getting
really
exciting
and
we're
getting
closer
and
closer
every
day
to
release
release
candidate
0
has
been
out
for
a
little
bit
and
then
we'll
see
we're
getting
like
I,
said
closer
and
closer
to
the
next
step
there
and
then
also
as
well.
A
We
talked
about
the
JavaScript
core
component,
which
is
something
we've
been
developing
for
over
a
year
now,
a
lot
of
folks
are
using
that
that
can
be
very
helpful,
with
SharePoint
framework
and
helpful
in
your
standard
development
as
well.
So
we
try
and
talk
about
those
two
topics
as
well.
As
generally
all
the
things
client-side
development,
JavaScript
development.
You
know
those
sorts
of
areas
if
you
have
questions,
we're,
always
happy
to
help,
and
if
you
can't
get
your
question
in
on
these
calls.
A
Please
join
us
in
the
community,
which
is
the
first
link
there,
the
AKA
ms
SP
p
and
p
dash
community,
and
that
will
take
you
to
the
microsoft
tech
community
and
then
the
other
site.
There
is
dev
office
com,
/
or
point,
which
is
your
one-stop
shop
for
all
things:
sharepoint
development.
So
if
you've
got
questions
about
the
new
SharePoint
framework,
you've
got
questions
about
AD
in
development
and
even
questions
about
classic
sharepoint
server
side
development.
A
That's
your
place
to
go
and
you've
got
links
there
out
to
the
different
topic,
areas
and
guidance
in
all
those
areas.
So
moving
on
what
are
we
going
to
talk
about
today?
We've
switched
our
agenda
or
switch
our
ordering
around
just
a
little
bit
based
on
some
of
the
feedback.
We
were
getting
so
we're
going
to
go
through
the
core
component
update
first
and
then
we'll
get
into
the
latest
on
the
SharePoint
framework
with
the
standard
time
for
discussion,
but
we
felt
this
would
be
a
little
bit
better.
A
We
wouldn't
have
to
cut
off
the
SharePoint
framework
discussion
to
move
on
to
other
topics.
We
could
just
kind
of
keep
that
rolling
as
long
as
folks
had
questions
or
or
topics
they
wanted
to
discuss,
and
then,
of
course,
we
have
time
at
the
end
for
just
general
open
discussion
if
you're,
if
you
don't
have
a
question
that
you
know
maybe,
is
directly
related
to
SharePoint
framework
or
you
think
of
something
late.
We
should
have
plenty
of
time
at
the
end.
Unfortunately,
this
week
we
don't
have
any
demos,
so
it
would
remind
everybody.
A
We
welcome
your
community
demo.
So
if
you've
got
something
you
want
to
show
off,
please
let
us
know
we'd
love
to
show
it
off
on.
This
call
show
the
community
what
you've,
developed
and
I
think
that
really
benefits
everybody,
because
we
get
to
learn
from
all
the
great
things
that
folks
have
done.
I
know:
I've
learned
a
lot
from
all
the
demos,
seeing
different
frameworks
that
I've
not
personally
had
a
chance
to
use,
yet
so
a
lot
of
cool
stuff.
A
So
please,
if
you're
doing
something
fun,
let
us
know
we'd
love
to
give
you
a
chance
to
show
it
off
on
this
call
to
the
community
so
jumping
in
to
the
Jazz
core
component
updates
again,
as
always
want
to
say
thank
you
to
the
contributors.
The
Jazz
core
component
really
appreciate
everybody's
work
there,
and
not
just
the
folks
that
are
contributing
the
folks
that
are
also
submitting
issues
and
providing
feedback
on
the
library
as
well.
So
that
really
helps
us
grow
and
make
things
better
in
terms
of
everybody
having
a
better
experience.
A
So
David's
got
a
question
here:
can
the
demos
include
SharePoint,
specific
JavaScript
coolness,
but
not
directly
tied
to
the
sheriff
in
framework
I
mean
you
like
using
JSON
to
enhance
experiences
in
classic
mode
sure
I
don't
have
a
problem
with
that.
Obviously
we'd
like
it
to
be
tied
to
SharePoint
in
some
way,
but
if
it's
plied
the
SharePoint
and
doesn't
necessarily
use
the
SharePoint
framework,
I
think
that's
definitely
stuff.
That's
worthwhile.
We
can
show
off
that
I
I
think
falls
in
the
the
category
of
client-side
development.
A
So
if
you've
got
something
like
that,
let
us
know
you
know
I.
Think,
like
I
said,
our
area
is
client-side
development
as
sort
of
a
big
umbrella.
We
sit
under
in
this
special
interest
group,
so
if
you've
got
something
that
falls
into
that
umbrella,
I
think
it's
definitely
worthwhile
to
share
that
with
the
community.
Again,
it's
all
about
learning
and
sharing
and
growing
together,
so
I
think
that'd
be
great.
A
So
the
updates
on
the
JavaScript
core
component
for
201
that
has
been
released
last
Friday
again
we're
going
to
try
and
start
aligning
to
the
the
rest
of
the
patterns
and
practices
releases.
So
that's
going
to
mean
monthly
releases,
which
are
going
to
be
a
little
bit
smaller,
but
a
little
bit
more
frequent,
which
I
think
is
going
to
be
good.
Sometimes,
we've
waited
a
little
bit
of
time
to
get
a
release
out
and
I.
Think
that'll
be
a
good
change.
We've
got
updated
guidance
in
that
release
for
working
with
the
SharePoint
framework.
A
You
can
see
that
in
the
release
blog
post,
as
well
as
the
developer
guide
in
the
wiki,
but
basically
that
involves
passing
now
the
this
context
from
inside
your
web
part
to
the
framework
and
the
reason
for
that.
Just
real
quickly
is
that
moving
forward
in
terms
of
working
with
the
SharePoint
framework,
there
isn't
going
to
be
the
idea
of
sort
of
a
global
pagecontext,
your
page
context
or
you're.
Sorry,
I
should
say
your
web
part
context
is
very
much
going
to
be
within
the
closure
of
that
web
part.
A
So
your
web
parts
I
think
I
can
say
this
in
the
roadmap
might
not
be
loading
necessarily
exactly
in
the
site.
They
could
be
loading
through
other
means,
but
that
context
within
the
web
part
will
always
be
correct
for
where
that
web
part
is
supposed
to
be
living
and
so
meaning.
In
the
past,
we've
relied
on
the
underscore
pagecontext
info
a
global
variable
to
help
construct
the
URLs
for
our
rest
requests
and
that's
not
going
to
be
valid
moving
forward.
A
So
we
added
a
fix
in
2010
or
an
enhancement
really,
so
you
just
pass
the
context
in
and
we'll
take
care
of
things
from
there.
That's
all
so
I
just
want
to
mention
if
you've
got
your
own
libraries,
that
is
not
the
spp
and
pjs,
but
you've
written
your
own
thing
and
you're,
using
the
underscore
pagecontext
in
so
global
variable.
A
You'll
want
to
look
at
updating
your
code
as
well
to
take
in
that
context
or
taking
at
least
the
information
you
need
from
that
context,
because
the
global
variable
will
no
longer
necessarily
either
exist
or
be
valid
for
where
your
web
part
may
be
loading
in
the
future.
So
just
a
heads
up
there
and
a
change
we
made
so
hopefully
folks
find
that
useful
and
then
also
in
that
release
we
did
a
rewrite
of
the
request
pipeline
that
should
be
invisible
to
everybody.
A
So
unless
you
dig
down
into
the
code,
you
shouldn't
really
notice
that,
but
we
did
that
for
two
reasons.
The
first
is
we
added
a
bunch
of
logging,
so
you
can
now,
if
you,
if
you
fire
up
the
jas
core
logging,
you
can
see
all
your
requests
and
the
data
that's
being
passed
through
the
pipeline.
Now,
in
terms
of
was
your
request
found
into
cash
and
things
like
that,
and
you
can
monitor
it
and
I
think
we've
got
much
better
error,
reporting
things
like
that
now,
so
I
think
that
should
help
with
development
and
troubleshooting.
A
That's
also
mentioned
in
the
blog
post
in
a
little
bit
more
detail
and
the
other
piece
was
we're
moving
towards
and
it's
not
there,
yet
it's
not
into
dotto
one,
but
looking
at
the
future
of
making
that
pipeline
extensible
so
allowing
folks
to
plug
in
their
own
methods,
say
for
caching
or
their
own
methods,
say
even
to
send
the
request
and
having
options
there
and
the
ability
to
insert
stuff
into
that
request
pipeline.
Maybe
to
do
data,
validation
or
some
custom
authentication,
or
you
name
it,
but
making
that
pipeline
extensible.
A
So
that's
kind
of
laying
the
groundwork
for
that
future
updates
there.
So
I
think
that'll
be
great
once
we
get
that
out.
But
that's
sort
of
laying
the
groundwork
doing
some
of
the
dirty
work
to
get
us
into
position
to
make
that
an
extent
a
pipeline
for
for
folks
consuming
the
library.
Another
thing
I
learned
to
mention:
I'm
going
to
start
trying
to
use
milestones
as
much
as
possible
an
issues
list.
A
So
what
that
to
be
again
trying
to
work
on
the
transparency
and
communication
out
to
folks,
so
they
now
have
a
little
bit
better
heads
up,
what's
happening
so
going
to
start
trying
to
attach
milestones
the
issues
in
terms
of
the
release
and
again
I
think
that's
going
to
help
with
the
monthly
releases.
We
can't
I
milestones
to
each
monthly
release
and
even
set
some.
You
know.
A
Maybe
a
few
releases
down
the
road,
for
example,
that
extensible
pipeline
is
probably
not
going
to
be
in
the
next
release,
but
maybe
in
a
couple
releases
brendan
has
got
a
good
questions,
the
global
page
context
into
a
variable.
Is
it
going
away
from
sharepoint
in
general
or
don't
use
it
in
SharePoint
framework
webparts?
So
in
classic
pages
and
classic
sites,
nothing
is
changing.
Sp
pagecontext
into
the
variable
will
be
there.
Everything
you've
used
in
the
past
will
be
there
no
changes
in
classic
sites
at
all
this.
A
What
I
said
earlier
applies
to
SharePoint
framework
webparts
and
then
the
other
pieces
of
SharePoint
framework
that
we
rolling
out
in
the
future
are
going
to
all
be
sort
of
wrapped
in
their
own
closure,
which
means
you're
going
to
need
to
rely
on
the
disk
context
that
will
be
provided
to
you
so
classic
sites
everything's
fine,
no
changes
to
existing
code,
but
for
SharePoint
framework
work.
You
can
no
longer
count
on
that
SP
pagecontext
info
variable,
even
if
it's
defined
it
might
necessarily
not
necessarily
be
correct.
A
Another
thing
I've
been
working
on
is
Travis
CI
integration.
The
first
thing
I
want
to
say,
is
that's
been
really
easy
to
set
up.
I've
been
really
impressed
with
that.
So
that's
pretty
much
done.
I'm
doing
some
final
testing
and
polishing
on
that
today,
but
there's
two
types
of
things
that
are
going
to
run
now.
A
So
that
will
help
all
of
us
have
a
little
bit
cleaner,
pull
requests
and
then
the
other
time
it'll
run
is
on
merges
and
all
the
blog
posts
on
how
to
set
this
up
for
your
Forks.
But
when
we
do
a
merge,
we're
going
to
run
the
full
test
suite
against
SharePoint
out
of
Travis,
which
is
kind
of
really
cool,
so
that
will
run
all
our
web
tests
as
well
and
make
sure
a
library
is
up
to
speed
and
then
Travis
the
site
is
work.
A
Travis
CI
the
site
is
working,
I
keep
talking
about
it
like
it's
a
person,
but
it's
a
site,
they're
working
on
the
ability
to
have
scheduled
test
so
cron
jobs
that
will
run
daily
weekly
monthly.
So
once
that's
released,
which
is
should
be
hopefully
soon
we're
going
to
schedule
tests
to
run
daily,
which
will
be
in
line
with
what
we're
doing
for
the
PowerShell
and
the
sea.
A
Psalm
libraries
running
the
daily
tests,
I
think
we're
doing
it
for
PowerShell
I
know
we're
doing
for
seesaw,
so
we'll
get
a
full
test
report
pretty
much
every
day
against
sharepoint
to
ensure
nothing's
changed
in
sharepoint
that
might
affect
our
work
and
that
our
work
is
still
valid.
So
I
think
that'll
be
great
as
well,
so
really
impressed
by
Travis
and
I'll
get
a
blog
post
out
around
my
experience.
A
Setting
that
up
as
well
as
you
know
how
to
configure
it
for
your
own
repo,
because
you'll
be
able
to
actually
run
our
web
tests
against
your
SharePoint
site
when
you
like,
do
a
push
into
your
fork,
so
that'll
be
pretty
cool
as
well.
I
think
that
would
be
a
neat
enhancement
and
I'll
say
honestly
had
I
known
it
was
as
easy
to
set
up
as
it
is.
A
I
would
have
done
it
sooner
and
then
we've
got
an
upcoming
webcast,
which
need
to
still
schedule
is
basically
getting
that
recorded,
but
talking
about
the
jail
or
how
it
fits
in
with
SharePoint
framework,
where
we
see
it
growing
and
then,
where
we
see
you
know
just
sort
of
the
general
place
of
jas
core
in
the
world
of
sharepoint
development.
So
we
get
a
lot
of
questions
about
that
and
I
think
we've
answered
it
a
few
times
and
then
from
then
to
now.
A
The
answer
has
changed,
as
everything
in
life
involves
a
little
bit
so
I
think
that'll
be
a
valuable
webcast
for
folks.
That
might
still
be
wondering
how
does
this
jay
s
core
library
fit
in
with
SharePoint
framework
or
fit
in
with
other
sharepoint
development?
You
might
be
doing
so.
That's
our
updates
for
this.
A
So
we
get
great
feedback
and
issues
list
great
feedback
on
git
er,
it's
really
great
stuff.
So
again,
thank
you
to
everybody
with
the
feedback
and
look
forward
to
getting
some
more
demos
on
these
calls.
So
really
try
to
encourage
folks
to
demo
your
stuff
on
these
calls.
So
now,
I'll
turn
things
over
to
vase
Oates.
You
give
the
updates
around
SharePoint
framework,
and
if
anybody
has
any
questions,
happy
to
try
and
answer
them
as
well
in
the
iron
window,
basically
all
set.
B
Unmute
myself,
so
I
can
actually
keep
on
going.
I
just
realize
that
I
haven't
actually
updated
all
of
the
slides,
but
there
are
few
slides
in
the
end
to
talk
about
the
roadmap
or
SharePoint
framework,
which
probably
is
interesting
for
everybody,
and
we
kind
of
actually
relate
some
road
map
details
and
its
deathbed
of
stuck
on
relatively
soon
as
well.
But
some
if
you've
gone.
If
we
were
here
two
weeks
ago,
I'm
going
to
repeat
some
topics,
and
hopefully
the
audio
quality
is
fine.
B
I
can
say
some
challenges
on
the
network,
but
tablet,
please
let
me
know
if
there
are
some
audio
issues
and
so
first
of
all,
there
is
again
some
level
of
a
new
guidance
in
the
Delta
X
becomes
a
SharePoint
there's
two
new
articles
actually
ending
which
are
under
review
and
which
will
go
live
probably
tomorrow
there
as
well.
The
list
of
new
articles
is
actually
directly
from
two
weeks
ago,
because
I've
update
at
least
so
I
do
apologize
on
that
one,
but
in
general,
in
the
deathbed
of
Kentucky
opponents.
B
If
you
go
to
SharePoint
framework,
webparts
and
guidance,
that
group
of
articles
is
expanding
right
now
quite
nicely,
so
the
current
contributions
from
the
community
engineering
is
contributing,
and
all
of
that,
so
that's
really
good
a
reminder
on
our
shape
and
framework
samples.
So
it's
just
letting
everybody
know
and
reminder
on
that.
One
AKA,
ms
s&p/asx
samples
you
land
into
the
PMP
sample
gallery
and
we
have
like
30
individual
samples
for
sharepoint
framework.
There
was
an
issue
within
the
within
the
gallery:
research
previously
that
you
were
unable
to
use
the
language
of
the
future.
B
All
that
has
been
no
fixed,
so
you
can
actually
use
if
you're
interested
in
react
or
angular
o
clock
out
as
an
example,
you
can
use
those
to
filter
when
you
filled
it
down
on
the
samples
which
are
available
now
latest
development
in
SPF
x.
This
is
pretty
much
exactly
the
same
status
as
such
a
reminder
from
of
two
weeks
ago.
Before
I
move
into
the
actual
new
topic
off
for
this
week,
so
written
and
video
tutorials
has
been
updated
to
release
candidate
of
several
level.
We
will
keep
on
updating.
B
B
Some
sample
updates
are
still
ongoing.
Unfortunately,
there's
so
many
examples
in
the
in
the
gallery
already
that
we're
kind
of
running
behind
of
the
curve
trying
to
get
them
all
on
the
release
candidate
level
thanks
everybody
who's
helped
around
upon,
because
a
lot
of
the
owners
or
the
original
sub
meters
of
the
samples
have
already
submitted
a
new
version
which
is
working
with
release
candidate,
which
is
really
good
getting
sponsorship
on
framework
training
packages
getting
closer.
Actually,
we
do
have
that
packets
already
available.
B
Updating
all
of
these
to
the
chair
level
whenever
the
TA
is
getting
on
now,
I
mentioned
this
getting
started
to
trip
on
framework
we've
been
mentioned
in
this
quite
a
few
times.
Just
has
been
quite
a
long,
lasting
process
already
right
now,
if
you
are
interested
about
on
getting
access
on
this
material,
it
may
actually
close
that
one.
This
is
available
in
the
kids,
hop
onto
our
own
kind
of
paste
in
the
URL
on
the
window.
Where
we
have,
let
me
see
eight
modules
and
inside
of
individual
modules.
Stairs
are
smaller
bits
and
pieces.
B
So
as
an
example,
the
SharePoint
framework
tools
and
libraries
is
the
sub
module
or
a
section
in
the
getting
started.
Module
and
all
of
the
material
is
already
available.
Bike
mentioned
in
a
case
are
preferred.
We
will
keep
on
scope,
we
will
have
a
proper
announcement
and
videos
and
everything
else
coming
up
slightly
later,
but
already
today
there's
some
labs.
There
are
some
videos,
sorry
system,
labs,
different
presentations
and
all
of
that
available
indicator.
B
This
is
going
to
be
relocated
slightly
sooner
or
later,
or
it
cannot
be
actually
at
least
merged
to
the
Masters
most
a
branch
of
this
github,
but
why
not
actually
share
the
URL
right
now
with
you
guys
if
you're
interested
now?
What
I
really
wanted
to
concentrate
on
today
is
if
something
related
on
the
questions
on
the
future
of
the
SharePoint
framework.
So
everybody
knows
that
we're
heading
the
ghe
is
going
to
happen
rather
fish
soon
for
client
site
with
parts
and
but
that's
not
the
whole
story.
B
So
we're
looking
into
doing
a
lot
of
other
stuff
as
well,
and
let
me
be
one
hundred
percent
clear
on
this
topic-
switch
we're
going
to
go
through
on
the
following
slides
as
well.
So
this
is
what
we're
looking
we're,
not
actually
promising
that
this
is
going
to
happen.
We're
not
promising
a
most
likely.
B
So
the
number
one
thing
obviously
on-premises
we're
looking
into
releasing
SharePoint
framework
in
on
premises
for
SharePoint
2016
SharePoint
2016
during
this
calendar
year
within
telling
taps
already
in
the
past,
we're
also
looking
into
improving
the
client-side
web
parts.
So
absolutely
there
will
be
improvements
there,
but
there
will
be
improvements
into
adding
model
as
well,
so
to
add
a
model
you
most
likely
can
build
modern
add-ins
using
this
checkpoint
favor
in
the
future
and
that's
what
we
actually
want
to
do
now.
When
will
that
happen?
That's
a
different
discussion
again.
B
Let
me
paste
with
a
clear
on
that
we're
looking
into
how,
in
code
parts,
goat
parts
essentially
means
pretty
much
the
same
idea
as
chase
link
or
use
the
custom
actions
of
in
a
slightly
more
structural
way
and
I'll
come
back
on
that.
One
in
a
second
versioning
story
is
getting
clarified.
Application
Lifecycle,
Management
I'll
get
back
on
that
one
in
the
second
as
well,
improvements
from
developer
experience.
Absolutely
and
obviously
this
is
a
public
webcast
and
this
will
be
recorded.
So
this
will
be
a
youtube
video
within
24
hours
notice
for
answering
Kim's
information.
B
This
is
absolutely
public,
so
we're
looking
into
full
page
apps
as
well,
so
making
sure
that
you
don't
have
to
just
think
about
the
smaller
with
art.
You
can
actually
go
to
fold
a
champ
improvements
on
the
web
hooks
and
then
ordered
occasion
and
Microsoft
crafts
improvements
as
well.
Now,
like
super
clear
we're
looking
in
the
we
are
aware
of
that
we're
looking
into
doing
this.
This
is
a
big
big,
big,
massive
backlog,
so
it
will
take
a
while
for
us
to
get
there.
Some
of
them
theoretically
might
be
that
we
never
actually
get
there.
B
Unfortunately,
because
everything
is
related
on
the
resources,
what
we're
having
but
absolutely
in
our
radar
to
get
these
things
done
now,
let's
have
a
quick
look
slightly
more
details.
Look
on
the
so
long
term
of
this
sorry
did
I
jump
or
one
flight
if
I
didn't
so
on
primitive.
The
SharePoint
framework
is
planned
to
be
shipped
as
part
of
the
feature
back
to
own
premises.
B
So
for
SharePoint
2016
the
target
is
to
have
a
full
feature:
fidelity,
but
with
a
different
pace
in
sharepoint
online
we
can
book,
but
with
updates
on
the
backend
quite
fast
and
also
on
the
packages
for
on-premises.
The
story
is
slightly
different,
but
really
the
key
point
is
that
we
would
have
a
common
development
platform
across
on-premise
and
cloud,
so
it
doesn't
matter
if
you're
doing
adding
model
development
or
Chevonne
framework
development.
B
You
would
be
able
to
take
advantage
of
the
exactly
the
same
development
story
in
total
size
objective
is
no
doubt
to
leverage
the
modern
tool
chain
and
open
source
on
the
lake
of
a
in
quotes
legacy
environments
because
I
wouldn't
actually
consider
chevonne
2016's
lake
of
the
environment
of
such.
But
man,
then
again
it
slightly
depends
on
on
what
we
mean
a
flag
of
thing,
and
the
idea
is
that
if
you
start
moving
into
the
core
start
using
SharePoint
favorite
in
SharePoint
2016,
you
get
a
head
start.
B
If
your
deployment
is
going
to
move
to
sharepoint
online
at
some
point,
so
it's
no
doubt
a
good
practice
actually
to
do
the
stuff
in
a
way
that
it's
already
aligned
within
the
cloud
deployment-
and
please
do
remember
me
to
yourself
in
this
coat
so
I
can
hear
some
background.
Noise
Santa,
on
the
background
like
mentions
we're
targeting
sharepoint
2015
during
the
calendar
year,
2017
I'm
going
to
meet
some
people
here,
sorry
for
not
so
they're,
avoiding
the
background
noise
as
well
now
the
other
stuff.
B
So,
let's
move
on
on
the
list
of
topics
with
parts
atoms
and
the
future.
So
we
want
to
make
sure
that
we
are
supporting
more
complex
than
areas
and
interactions
with
web
parts.
So
with
part
of
a
parte
communications,
it's
a
classic
request
and
absolutely
we
know
that
request.
We
wanna
address
done
javascript
framework
isolation.
B
So
how
do
we
make
sure
that
the
JavaScript
frameworks
and
styles
do
not
collide
on
the
on
the
pages
if
there's
multiple
different
ways,
parts
which
are
used
in
different
frameworks
and
all
that
absolutely
aware
of
that
and
we're
looking
into
addressing
that
we're?
Also
looking
into
look
at
the
address.
B
The
citizen
developer
model
essentially
means
the
classic
model,
where
hey
I'm,
not
a
resource
to
do
Chi
I'm,
not
a
chava
script,
developer,
guy
and
but
I
want
to
actually
embed
the
small
javascript
widget
on
my
page
as
easy
as
possible,
or
to
my
field
as
a
chase
link
without
the
fact
that
I
need
to
open
to
a
resource
area
code
or
visual
studio.
To
make
that
happen.
So
we
do
have
some
plans
on
that.
One
I
cannot
disclose
all
of
those
plans
at
this
point
of
just
letting.
B
You
know
that
absolutely
aware
of
to
ask,
and
we
want
to
make
sure
that
that
that's
a
task
is
being
addressed
in
the
future
as
well.
If
we
can
address
that,
but
we're
looking
into
that
one
as
well
bringing
adding
models
to
the
modern
world.
So
essentially,
we
want
to
make
sure
that
the
existing
added
model
will
be
aware.
People
have
made
a
lot
of
investments
from
a
implementation
perspective.
They
would
play
nicer
with
the
new
UX
as
well.
B
So
so,
let's
go
through
the
topics
and
then
we
can
concentrate
on
the
Q&A
section
code
type
and
arbitrary
code
and
again
future
stuff
with
this
in
our
backlog.
So
we're
looking
into
addressing
chase
link
actress
in
the
field
throw
an
interview
level.
The
whole
point
is
that
this
is
a
relatively
common
scenario,
how
people
are
customizing,
sharepoint,
online
or
SharePoint,
2016
or
on-premises.
B
Currently,
we
know
that's
what,
when
I
address,
that
we
don't
want
to
have
it
in
the
way
like
it
is
right
now,
essentially,
maturity
of
the
user
user
custom
action
such
as
main
customizations
work
in
a
way
to
pay,
use
our
cooking
a
JavaScript
on
the
page,
which
is
great
and
it's
flexible,
and
we
do
not
do
show
how
to
make
that
happen
in
BMP.
The
challenge,
however,
is
that
when
we
change
the
dates
dome
structure,
those
customizations
fail.
So
in
the
future.
B
What
we're
going
to
do
is
that
we
want
to
keep
you
a
cabron
te
related
on
areas
and
sections
on
the
pages.
As
long
as
to
hit
certain
ID,
it
will
be
current
e
to
be
on
the
page
or
as
long
as
you
do,
the
certain
modifications
which
we
tell
you
what
you
can
do
and
how
do
you
hook
in
your
JavaScript
on
those
things?
B
We
will
current
data
that
functionality
will
be
there
with
countless
if
we
change
the
whole
UI
example,
and
that's
really
the
advantage
and
the
World
why
we
want
to
invest
on
building
days
and
Shere
Khan
framework
for
the
modern
science
and
the
classic
version,
as
well
so
currenty
that
your
ex
customizations
do
not
create
whenever
we
modify
the
pages,
what
they
might
do
writing,
but
the
SharePoint
framework
upon
0.
That
is
really
focus
a
quick
one.
B
So
all
of
these
additional
things,
our
roadmap
and
we
keep
on
then
release
and
then
gradually
after
the
the
1.0
comes
out
with
the
contract
by
parts,
then
first
proper
place
will
be
to
chase
link
capability
then
later
on,
use
the
custom
action
scenarios
and
more
for
more
additional
flexibility
on
that
one
as
well
I
missing
something
from
polish
points:
aquafina,
nothing
special
and
you
can
ask
question
after
I
cultures,
few
more
slides
on
what
I
was
planning
to
do
application,
lifecycle
management.
And
what
are
we
planning
to
do
on
that
side?
B
So
this
is
a
relatively
kind
of
a
hard
topic.
It
means
different
things
for
different
people.
So
it's
not
a
specific
term
such,
but
what
we
want
to
make
sure
is
that
we
make
significant
improvements
on
this
side
as
well.
One
of
the
classic
scenario
is
ok.
I
want
to
deploy
my
ad
in
or
client-side
web
part
to
be
available
in
a
tenancy
using
automatic
api's.
Yes,
we're
looking
into
doing
that.
B
So
a
llamar
rest
api
is
for
deploying
packages
activating
a
nap
deleting
a
nap
of
creating
a
nap
and
that's
essentially
for
sharepoint
framework
up
packages
or
then
for
a
dense
as
well.
So
that
would
be
them
available
at
some
point
whenever
we
get
there
to
be
available,
just
joking,
the
truth,
sita
and
hosting
for
the
code.
So
obviously
we
already
right
now
we
have
an
office
365
public
CDN
as
a
one
of
the
options
for
stadiums.
B
That's
in
the
Developer
Preview
that's
going
to
go
ta
quite
soon,
we're
looking
into
getting
Def
Con
natively
supported
as
well,
and
having
more
support
on
that
one.
So
you
can
more
easily
in
your
SharePoint
rain
work
packages
define
how
the
files
are
getting
shared
and
distributed
using
your
office,
365
public
or
private
CDN,
which
will
be
available
quite
soon
as
well,
and
that's
being
done
by
a
slightly
different
people
than
the
ship
on
frameworks
for
this
climbing
challenges
and
making
sure
that
every
feature
is
working
properly.
B
B
Teach
developer
experience
the
future
on
that
one
over
the
workbench
2.0,
so
we're
looking
into
having
a
development
story
now
beyond
the
web
parts
because
we're
looking
into
having
the
code
parts,
aka
user,
custom
actions
absent
ages
and
all
that
available
we
need
to
enhance
the
existing
workbench
to
a
new
version
as
well
and
then
having
something
simple
like
connector
SharePoint.
So
you
would
be
able
to
configure
you
in
your
solution.
B
What
is
my
tenant
and
then
in
the
local
workbench
click
a
button
and
you'll
pay
sweats
with
the
sharepoint
online
and
in
a
sharepoint
online.
You
can
easily
slip
back
on
the
on
the
local
workbench.
Don't
have
to
remember
those
urls,
but
that's
a
simple
fix.
Having
the
support
for
adding
some
code
parts
or
full
page
apps
is
it's
much
more
complicated,
fixed,
slow
to
change
components,
and
you
know
yeoman
templates
and
so
toolchain
components
more
flexibility
on
how
do
you?
What
can
you
do
whenever
we
actually
built
a
tooling
or
the
apps?
B
So,
what's
going
to
happen,
you
can
do
more
flexibly
code
tasks
or
whatever
and
then
also
additional
yeoman
templates.
So
right
now,
by
default
in
the
SharePoint
framework
human
templates,
we
have
the
no
library,
react
library
and
the
clock
library
templates
available,
which,
by
the
way,
does
not
mean
that
you
wouldn't
be
able
to
do
use
any
other
libraries
to
stay
a
predefined
project
template
so,
but
we're
looking
into
having
additional
project
and
placed
and
available
in
the
Yom
on
by
default,
as
well
short
and
I.
Think
that's
the
final
slide
on
this
one.
B
Then
we
can
open
up
and
this
one
for
Q&A.
It
is
probably
missed.
Quite
a
few
questions
and
so
food
plates
apps.
It's
a
one
thing
with
kind
of
a
mention.
This
will
be
mentioned
in
this
back
in
Atlanta
in
September
as
well.
It
is
still
in
our
roadmap,
and
the
whole
idea
is
that
we
would
be
if
you
would
be
able
to
have
a
full
pace
app
rather
than
one
single
client-side
web
board.
B
With
this
understandable
ask-
and
we
have
some
designs
on
this
one
as
well,
and
we've
been
playing
around
with
the
concepts
inside
of
the
engineering
as
well.
So
the
ask
absolutely
understandable,
but
it's
interview
of
getting
moving
whenever
we
get
there
and
would
add
people
to
meet
their
self
there
we
go.
So
it's
not
background
noise
page
so
before
we
actually
close
up
and
I
know
that
the
lot
of
questions
are
get
back
on
the
questions
in
a
second
one
thing.
B
What
I
wanted
to
do
is
so
that
was
kind
of
what
we
want
to
do
in
the
future
and
most
likely
the
following
spawn
and
slide
is
still
intact
in
the
flight
deck
with
good.
So
I
know
that
they
have
a
lot
of
questions
on
the
future
roadmap
or
Chevonne
framework.
But
if
we
concentrate
right
now,
still
on
the
version,
1.0
and
I've
been
asking
this
and
every
single
special
interest
group
goal
since
November,
the
ga
of
contact
is
coming
pretty
soon.
What
are
you
guys
need?
B
And
if
the
answer
is
well,
I,
don't
know
maybe
getting
the
documentation
up
to
date
and
that's
an
also
mention
answer
as
well:
more
guidance,
more
samples.
What
kind
of
documentation
is
really
the
question,
and
we
don't
have
to
spend
so
much
time
on
this
one,
but
it's
kind
of
an
interesting
topic,
because
obviously
we
want
to
address
whatever
might
be.
It's
working
you
to
adapt,
Chevron
framework
samples,
at
least
from
Ralph
and
Kieran.
B
We
have
35
samples
in
the
sample
gallery
around
35
samples
in
SharePoint
framework
already,
which
is
good,
make
sure
that
all
samples
up
to
date
here
or
with
you,
there
Nigel
and
that's
no
doubt
to
plan
as
well
jocks
and
guidance.
Now
on
the
dogs
and
guidance.
What
dogs
and
what
items
is
really
the
key
on.
B
David's
points
the
info,
how
a
link
here
user
custom
actions
are
going
to
be
updated.
It's
very
helpful.
We
don't
have
that
info
yet
so
that's
in
the
back
row,
Clark
nation,
that's
in
our
roadmap
and
yes,
whenever
we
are
planning
to
release
stuck
on
the
casing,
can
use
the
custom
actions.
Ii
guess
we'll
address
them
right
now.
The
GA
is
for
client-side
web
course
and
that's
going
to
happen
relatively
soon.
B
Perhaps
a
a
sample
with
native
JavaScript
is
not
over.
There
I
think
already
has
angular.
We
do
have
a
native
samples
for
without
any
framework
or
sofa
couch
operations,
more
risks.
Examples,
yes
and
that's
a
fair
point:
we've
been
trying
to
address
the
rest
api
documentation
internally,
we
are
I,
wouldn't
say
that
we
looked
at
what
we're
trying
to
address
that
still
as
much
as
possible,
because
the
existing
rest,
api
documentation
is
pretty
much
horrible
and
we
do
get
that
man
and
we're
trying
to
get
that
unplugged
a
unique
testing.
B
Cute
yeah
the
whole
point
of
showing
actually
our
roadmap
and
kind
of
a
slightly
covering
through
what
are
they
planning
to
do
in
the
future,
without
timeline
state
and
schedule
commitments?
It's
really
to
let
you
everybody
know
that.
Yes,
we
are
aware
of
the
ask.
We
are
aware
of
the
need-
and
we
do
know
that
people
do
this
customization,
and
so
it's
only
non
backlog.
B
It's
just
matter
of
getting
it
them
simple
sample
samples
with
the
fair
comments
will
get
more
samples
in
and
where
to
first
class
support
us
that
it's
what
all
of
my
customers
are
moving
towards.
The
challenge
Mike
on
the
angular
2
is
actually
if
the
problem
is
not
on
the
SharePoint
framework,
the
problem
is
actually
on
the
angular
2
side
and
we
are
working
together
with
Google
on
addressing
them,
because
angular
2
assumes
to
be
a
single
beta.
B
Well,
you
can.
There
are
ways
to
work
around
on
that
one,
but
that's
really.
The
challenge
angular
assumes
to
be
a
single
based
application
and
therefore
we
need
to
have
some
modification
on
the
angular
design
and
we
are
actually
working
with
Google
on
that.
With
this,
some
super
weird
much
of
engineering
working
with
Google
to
address
something
together,
but
it's
the
new
world
samples
it's
on
web
part
from
some
shared
code
between
them
kind
of
a
full
solution.
Absolutely
that's
a
good
one
Lewis!
Thank
you.
Unit-Testing
plus
one
is,
for
example,
out
around
localization.
B
Yes,
angular
assumes
it's
a
single
instance.
That's
what
it
actually
means.
Yes,
indeed
so,
but
it
kind
of
assumes
it's
a
single
based
application
where
it's
hosted.
So
it's
not
hosted
in
the
page
where
you
might
have
25
other
client
site
reports,
some
of
them
using
our,
and
we
are
one
point,
take
some
of
them
angular.
To
sum
up
and
using
something
else,
it's
a
slightly
challenging
scenario,
motivational
videos
to
learn
conscripts.
Yes,
all
with
you,
there
angler
to
comment
as
well.
B
B
And
service
is
built
using
angular
2
so
right
now,
yes,
so
it
again
did
the
means
what're.
We
managed
services
in
this
context,
but
angular
to
support
in
general
and
the
guidance
on
that
one.
Yes,
yes,
we're
now:
that's
I
have
all
the
typing
spin
off
creditors,
the
effects
to
use
typing's.
They
have
so
and
we
find
it
for
any
provision
of
a
default.
Clyde
pari.
B
You
can't
actually
still
typing
folder,
but
it
has
like
two
files
and
unloads
that
that's
kind
of
getting
obviously
cleared
and
gone
when
I
get
to
the
today,
so
it
will
be
absolutely
in
sightings
and
the
release
candidate
11
is
already
using
a
piping
properly
with
seducing.
Now
I
probably
missed
quite
a
few
questions
above
when
I
was
quickly
running
through
the
list
of
things.
I'm
going
to
quickly
go
back,
maybe
on
there.
Unless
we
have
some
other
things.
B
Ralph
has
some
good
idea
from
the
entire
window.
That's
always
good,
I'm
not
sure
if
I
like
piña
colada,
I'm
a
certified
support
as
an
inhuman
template
generator
and
where
we
entered
smash
the
effects
methylated
the
module
on
component
compile
to
the
more
powerful.
I
know
it's
going
to
dominate
and
the
price.
Yet
that's
a
fair
point
we'll
see
which
of
the
right
areas
will
win.
Absolutely
so
I'm
going
to
might
be.
No
doubt
one
of
the
big
winners.
B
B
And
mike
is
saying
that
it's
not
going
to
be
a
competition
that
script-
I
don't
have.
Statistics
or
insights
and
and
I
know
that
across
the
world
feasibility
on
the
metrics
of
actually
something
else,
that's
fine
and
okay.
So
who
knows
where
we
are
in
23
years?
It
might
be
completely
new
library
which
will
overcome
everything
else.
So
I
react
is
going
to
be.
Unprofor
react
properly,
Cambridge,
honking
future-focused.
Yes,
that's
one.
B
Okay,
cool
so
I'm
going
to
go
back
up
slightly
back
on
the
up
off
the
things,
because
I
don't
have
anything
else
to
cover.
I
know
that
I
went
through
super
super
hope.
These
are
old
fights
and
there's
a
month
actually
clean
from
the
link
we
went
to.
This
would
be
fast
on
the
on
the
roadmap
slides
and
if
there's
any
questions
related
on
those
feel
free
to
ask,
and
what
like
mention
that
I
want
to
be
super
super
clear.
B
The
whole
point
of
going
through
those
slides
in
this
presentation
is
to
let
everybody
know
that
we
are
absolutely
aware
of
the
requirements
for
user
custom
action
as
an
example,
all
the
scenarios,
which
typically
are
at
risk
using
the
use
of
connections
or
the
tears
link,
and
we
want
to
address
those
scenarios
and,
in
general,
we're
more
interested
on.
Why
did
you
need
to
use
them
rather
than
I
want
to
attach
whatever
JavaScript?
On
my
page
cool,
you
want
to
attach
the
JavaScript
on
your
page.
For
what
reason?
B
B
B
Can
you
share
the
list
of
web
parts
that
much
so
that
they
providing,
unfortunately,
no
I,
can't
and
that's
a
moving
target
as
well,
and
although
I
will
provide
some
web
parts
first
and
then
additional
web
parts
and
our
report
roadmap
or
back
lock,
is
like
hundreds
of
ways
pods
and
now
we
just
and
we
will
actually
deliver.
That's
a
different
discussion.
B
Is
there
a
skeleton
webpart
available
which
looking
at
our
functionality,
if,
whenever
you
provision,
whenever
you
turn
the
yeoman
template,
that's
essentially
the
skeleton
want
to
help
right
now,
I'm
going
to
scroll
back
down
and
see
if
I'm
actually
missing
any
any
points.
Can
you
provide
more
insights
about
custom
actions,
navigation,
so
aunt
of
the
big
queer?
The
flight
deck
will
be
shirt
in
the
cockscombs
last
office
death
pretty
soon
as
well,
not
together
with
the
whenever
the
video
goes
live.
So
let's
actually
start
with
that
one.
B
So
all
of
the
the
BMP
slides
typically
are
shared
using
our
dorko
mattress,
so
you
can
actually
come
in
here.
The
200
fly
pics
and
a
lot
of
slides
on
different
topics,
and
this
stick
there
will
be
six
slides
will
be
shared
there
as
well.
Go
do
some
cleaning
on
the
decks
because
there
were
some
leftovers
from
the
previous
session.
B
Now
on
the
on
the
other
topics,
the
theme
is
saying:
can
you
provide
any
more
insights
about
the
user,
custom
and
navigation
now,
like
mentioned
what
we
want
to
do
in
the
future?
So
let's
go
one
step
at
the
user.
Custom
actions.
Awesome
scenario-
and
you
can
actually
do
whatever
you
like
in
the
inner
SharePoint
in
a
SharePoint
on
premises
or
sharepoint
online
by
attaching
your
JavaScript
under
the
page,
and
then
you
do
you
go
to
the
dome
level
off
the
base
and
you
start
doing
modification.
You
can
even
check
custom
controls.
B
B
So
the
really
good
challenge
what
we
want
to
enter
s
in
the
feature
related
on
the
Travis,
Tritt,
customizations,
related
on
user
custom
action
or
the
modern
I
use
a
custom
action,
implementation,
instant.
We
will
Karen
p
certain
sections
in
the
site
or
in
the
pages
or
in
the
layout,
which
will
be
there,
and
then
you
can
modify
those
sections.
You
can
imagine
that
in
a
simplistic
scenario,
and
thus
oversimplifying
everything,
we
will
give
you
unique
IDs
of
certain
sections
in
a
page
and
will
say
that
ID
will
be
always
a
new
page
will.
B
Apparently
the
ideas
on
the
page
will
currently
that
that
is
called
the
navigation.
When
will
currently
that
you're
able
to
add
additional
stuff
on
on
that
ID
now,
that
would
be
a
relatively
simple
istic
way
of
doing
customization.
So
what
we
want
to
do
with
SharePoint
framework
is
that
we
want
to
keep
you
additional
benefits.
So,
yes,
with
an
ID
on
a
div
ID
on
a
page,
you
can
actually
interact
in
navigation
elements
of
to
a
certain
section
of
the
page,
but
food.
B
B
B
Hopefully
that
it
makes
some
level
of
a
sense
simulated,
but
back
on
the
PMP,
if
you
say
the
template
for
provisioning,
can
you
change
the
language
provisioning
time?
Well,
that's
more!
On
the
on
the
front,
elevational
template
and
provisioning
temp
right
side.
You
can
absolutely
well
the
MP
provisioning
engine
works
in
a
way
that
you
are
applying
customizations
and
configuration.
You
will
still
need
the
provision,
the
site
you
can
provision
the
site
using
a
one,
API
call
and
doing
that
API
call
it
and
change
whatever
language
you
want
actually
going
to
use
class.
B
That
approach
sounds
great
exactly.
Thank
you.
Excellent
thanks,
good.
My
explanation
hopefully
did
may
have
seemed
to
have
make
sense
for
the
future
and
trust
me
everybody
in
engineering.
They
understand.
We
do
know
that
you
would
like
to
have
all
of
these
goodies.
What
we're
looking
for
should
be
available
right
now.
Trust
me
I
would
love
to
have
them
available
as
well,
and
everything
takes
time.
The
chalice
of
us
releasing
something
for
you
guys
is
that
we
need
to
actually
support.
B
We
if
we
release
something
today,
for
example,
the
client
side
with
parts
will
go,
live
relatively
soon
well,
not
today,
but
relatively
soon,
and
we
will
need
to
support
that.
We
will
need
to
have
a
backward
compatibility
for
the
API.
We
cannot
go
and
say
whoopsie
we're
going
to
do
a
breaking
change
for
your
AP
is
because,
whatever
clients
are
big
parts
for
gluten
developed,
this
would
all
hit
program.
B
So
the
reason
why
it
takes
slightly
longer-
and
it
takes
time
for
us
to
do
this-
let's
say
a
long-term
implementations-
is
that
we
really
really
want
to
make
sure
that
we
do
minimize
the
need
for
breaking
any
breaking
changes
in
the
future.
Well,
we
cannot
actually
do
those
and
we
want
to
make
sure
that
you're
still
able
to
do
whatever
is
needed
to
be
done
in
the
share
points
in
the
in
the
future
as
well.
That's
why
it
actually
takes
time.
B
Rose
has
a
comment:
it's
okay
take
the
time
to
get
a
fight,
at
least
in
my
case,
we're
talking
clients
in
the
letting
us
use
this
stuff,
which
is
six
months
yet.
Can
we
multi
try
to
be
impaired?
Provisioning
I'm
asking
because
we
need
to
provision
the
sub-sites
synchronously,
but
it's
taking
five
to
ten
minutes
to
provision
answer
is
actually
yes
and
you
stain
is
occurring
with
cross
yeah
and
it
we,
it
would
be
like
mention
it.
B
It
would
be
great
to
have
all
of
this
ready
already,
but
we're
in
a
different
group
and
one
thing
what
you
need
to
learn
as
a
sharepoint
people,
I
used
to
be
a
filtered
person
in
SharePoint
as
well
and
I
fix
consultant
from
NPS
and
also
so
the
world
is
changing.
We
can
that
we
we're
releasing
new
capabilities
in
a
month
of
Ages,
or
there
will
be
actually
there's
a
new
beliefs
or
for
sharepoint
online
in
every
single
week,
which
is
actually
super
crazy.
B
Considering
the
fact
that
in
the
past
we
were
releasing
a
new
SharePoint
versioning
to
every
three
years
when
we
list
every
three
years,
we
in
engineering
actually
have
a
lot
of
time
to
polish
and
make
sure
the
baby
as
our
are
valid,
and
everything
is
up
to
date,
and
now
that
we
are
in
this
new
world
with
sharepoint
online.
We
want
to
push
you
guys
additional
goodies
faster
than
that,
and
they
will
be
much
faster
than
isn't
to
the
three
years
I
kept
seeing.
B
One
example
using
natural
functions
would
be
useful
and
thats
related
on
the
sample
discussion.
I
shall
function.
Let's
see,
we
do
have
examples
using
asha
functions.
We
do
have
a
for
example,
for
the
web
hook
handling.
We
do
have
other
samples
in
the
B&B
in
general.
The
Asha
function
is
definite
for
extent
well
with
SharePoint
framework,
specifically
because
SharePoint
framework
is
UI
layer
and
right
now.
Currently,
you
cannot
call
a
sure
usher
security
assets
from
a
client-side
web
part
without
authentication
requirements
which
we
are
looking
interesting
as
well.
B
Tim
I
understand
your
concerns.
We
are
asking
for
both
new
stuff
and
all
the
time,
but
also
asking
it
to
be
stable
and
be
supported
in
long
term.
I
appreciate
your
prudence
in
ruling
things
out.
Even
the
adsorber
I
want
to
all
yeah
I
know
that,
wouldn't
it
make
sense
the
converse
Department
back
to
you.
Sasha
functions,
oh
yeah,
yeah,
that's
a
fair
point.
We
could
so
on
that
particular
topic.
So
the
PNP
part
in
fact,
is
showing
kind
of
a
classic
B&B.
B
Well
customization
story
around
managed
code
and
use
a
probably
earthside
provisioning
everything
else.
One
of
the
things
like
that,
what
it's
using
is
an
usher
with
job
for
the
back
end
processing,
and
we
could
no
doubt,
as
which
step
as
you're,
with
a
chance
to
be
an
usher
function,
so
that
or
do
an
alternative
site
implementation.
So
you
could
choose
if
we
want
to
do
a
not
share
function
or
if
you
do
want
to
do
a
national
with
job.
B
Would
that
would
be
actually
really
nice
implementation
as
well,
so
that
you
can
compare
the
costs
na
implementation
and
everything
else?
What
does
it
actually
mean?
Aysha
functions
is
the
call
me
dude
in
the
clock.
Everybody
wants
to
play
with
us,
your
functions
so
kind
of
make
sense,
but
to
be
fair,
it's
the
same
objectives.
You
put
an
irq
bit
of
requesting
a
shell
first
few
and
then
you
fire
either
usher
with
job
or
an
usher
function.
Then
the
function
is
doing
something
to
work
sharepoint
online.
B
So
the
scenario
itself
is
exactly
the
same
with
with
element
in
the
usher.
It's
doing
that
difference,
but
that
your
function
is
still
cheaper,
so
it
would
probably
make
sense
to
have
such
kind
of
a
sample
cute.
Another
question,
so
she
open
framework
feature
questions
comments,
concerns
I,
don't
want
to
use
it
because
of.
Let
us
know
if
there's
any
concerns.
If
there's
any
doubts,
we
we
do
understand
that
it
takes
one
to
learn
the
new
ways
of
doing
development,
learning
to
type
script
and
everything
else
and
and
that
challenge
is
no
doubt
there.
B
But
if
there
are
specific
requirements
and
requests
towards
us,
we
are
trying
to
help
on
those
days
rock
app
store
and
the
SharePoint
framework.
We
don't
have
a
specific
story
on
that
phone
right
now,
because
SharePoint
framework
client-side
web
bots
are
always
running
in
the
context
of
the
page
so
in
quotes.
They
are
focused
now
hopes
of
customizations.
We
are
looking
into
on
the
story
on
that
one,
so
it
is
in
our
backlog.
There
are,
there,
isn't
a
fine
person
who
is
looking
into
that,
but
we
can
actually
share
any
details
on
that.
B
B
Good,
we
have
four
minutes
until
we
are
heading
to
our,
but
if
there
isn't
any
massive
additional
questions
or
suggestions
or
comments
that
we
can
absolutely
close
up
for
today,
we
didn't
have
any
live
demos
today,
but
I
was
hoping
and
we
were
hoping
together
with
Patrick,
that
having
some
visibility
for
the
additional
things,
what
are
we
considering
for
the
future
will
be
highly
beneficial
for
you.
People
and
obviously
the
video
is
recorded
with
this-
will
go,
live
with
again
be
youtube
channel
within
24
hours.
B
B
B
Oh
there
are,
there
are
some
comments.
I
can
actually
access
this
in
the
second.
You
have
about
a
link
for
scenarios.
Is
there
something
to
provide
those
to
you?
So
we
don't
specifically,
probably
the
easiest
way
to
do
that
is
to
have
just
open
discussion
in
our
community
channel,
so
I'm
gonna
actually
have
the
community
channel
URL
in
a
window.
B
A
preset
logo
features
effects
an
allotted
amount
of
the
questions.
Thank
you.
One
more
thing
to
have
to
show
how
to
construct
an
SPF,
X,
sweat
part.
So
for
that,
one,
if
you're
looking
in
the
guidance
on
the
on
the
web
parts
or
I,
would
actually
have
a
look
on
the
our
tutorials,
because
these
are
showing
how
to
construct
an
SPF
x,
work
or
so
step
by
step,
including
also
video
on
how
to
set
up
your
development
environment
but
I
think
that's
it
we're
hitting
our.
Thank
you
everybody
for
joining.
Thank
you
for
your
questions.