►
From YouTube: SPFx JavaScript SIG 20170105
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello,
this
is
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting
for
January
fifth
2017.
Thank
you
all
for
joining
a
happy
New
Year
to
everybody.
I
hope
folks
got
some
time
off
around
the
new
year
and
welcome
everybody
to
our
first
meeting
of
this
new
year.
So
let's
jump
right
in
and
serve
those
of
you
that
might
be
new
or
first
time
joining
the
meeting.
What
is
the
SharePoint
framework
and
the
JavaScript
special
interest
group?
A
There
was
just
too
much
to
cover
so
we
broke
things
out
in
the
special
interest
groups.
We
started
how
or
coming
up
probably
on
almost
a
year
ago,
well
probably
februari
a
year
for
the
special
interest
group
for
client-side
development
or
the
first
there's
now
also
a
power
shell
and
core
special
interest
groups.
But
the
idea
is
to
allow
folks
that
have
injured
certain
area
to
join
in
and
focus
on
that
area
and
really
be
able
to
kind
of
get
more
feedback
and
have
more
of
a
community
around
those
certain
areas
of
interest.
A
You
could,
of
course,
join
as
many
of
the
special
interest
group
calls
as
you
like,
but
they
are
a
little
bit
more
topical
and
then
the
monthly
update,
of
course,
then
rolls
up
what's
happening
in
the
entire
program.
So
on
this
call
generally
what
we're
going
to
be
doing-
and
this
varies
a
little
bit
from
call
to
call,
but
in
general
we
have
an
open
discussion
about
sharepoint
framework.
The
development
on
the
SharePoint
framework
using
the
SharePoint
framework
latest
releases.
A
We've
got
some
exciting
news
coming
from
basa
on
that
today
and
just
sort
of
client-side
development
patterns
in
general,
and
we
also
talked
about
building
the
JavaScript
core
component,
the
core
library,
which
is
there
to
help
folks,
if
they'd
like
to
use
it
with
their
clients,
live
development
or
their
no
development,
if
you're
developing
directly
on
node
itself,
and
it
can
also
be
used
with
the
SharePoint
framework.
So
the
idea
is
like
there's
the
managed
code
core
component.
We
also
have
the
JavaScript
core
component.
A
A
That
goes
to
the
microsoft
tech
community,
which
is
a
great
place
to
post
questions
and
get
help
from
both
Microsoft
folks
and
then
folks,
generally
out
in
the
community,
and
then,
of
course,
you've
also
got
dev
office,
calm,
/
SharePoint,
which
is
your
one
stop
for
all
sharepoint
development,
so
SharePoint
framework,
if
you're
looking
to
get
into
that
lots
of
resources
on
that.
But
if
you're,
if
you're
doing
ad
in
development,
if
you're
doing
server
side,
sharepoint
development
resources
for
that
as
well,
so
those
are
still
obviously
valid
and
supported
development
technologies.
A
His
face
is
gonna
walk
us
through
some
of
the
upcoming
changes
for
the
SharePoint
framework
release
candidate,
which
is
not
quite
out
yet,
but
we're
going
to
be
able
to
show
you
guys
a
little
bit
of
a
preview
of
some
of
the
things
that
are
going
to
be
included,
switch
I,
which
I'm
looking
forward
to
and
is
going
to
be
really
exciting
and
then
also
got
an
open
discussion
at
the
end.
B
As
long
as
I
get,
I
can
say
that
as
well
now
I
can
say
that
so
shape
on
framework,
just
an
updates
on
this
one.
So
I've
slightly
change
the
format,
so
the
release
candidate
is
coming
really
soon.
We
already
kind
of
a
early
December
or
in
the
center.
We
were
kind
of
hoping
that
it
would
we
be
able
to
get
it
out
before
the
holidays.
B
Unfortunately,
though,
slightly
delayed,
but
now
we're
getting
pretty
close
on
on
getting
the
release
candidate
out
so
right
now
still
in
the
production,
we
are
in
the
deaf
previous
studies,
which
means
that
it's
working
in
the
first
released
tenants
and
then
in
the
developer,
tenants
and
now
we're
moving
into
the
release
candidate.
The
release
candidate
is
already
relatively
close
to
GA.
B
Other
things
related
on
SharePoint
framework.
You
might
have
seen
this
in
a
social
media
communications
as
well.
So
right
now
we
have
already
more
than
well
close
to
30
different
client-side
web
parts,
samples
available
within
a
Kiton.
So
if
you're
using
a
KMS
SPF
examples,
you
land
in
the
deathbed
of
com
search
q
I,
we
can
then
actually
filter
down
inserts
individual
web
parts
which
are
available
using
the
SharePoint
framework,
and
those
are
really
really
super
samples
to
learn
the
basics
as
well,
so
some
of
them
might
be
complex.
B
Some
of
them
are
intentionally
super
simple,
so
that
so
that
you
can
easily
adapt
the
actual
concept
and
then
start
learning
to
building
more
complex
stuff
by
yourself
as
well.
Whenever
the
release
candidate
actually
goes
out
the
release
candidate,
we
will
start
updating
these
samples
as
well.
So
it
will
take
few
days
until
all
of
the
samples
will
be
in
the
release.
B
Candidate
status
will
bring
the
individual
persons
who
implement
at
the
sample
if
they
want
to
actually
do
the
upgrade
the
release
candidate
or
not,
and
if
they
decline
on
doing
that,
we
can
do
that
for
behalf
of
them.
I
can
see
some
of
the
guys
in
this
call
as
well.
Now
so
I'll
will
be
pinging
you
guys
in
the
key
top
for
asking
if
you
are
interested
on
upgrading
your
stuff
for
now.
B
So
let's
try
to
get
that
one
up
two
up
to
date,
relatively
fast,
so
that
all
of
the
samples
which
are
available
in
a
key
tough
are
actually
using
the
release,
candidates,
question
and
then
one
thing
what
we
have
already
done
during
this
week,
we
used
to
have
to
guidance
articles
in
the
death
pedals,
calm,
/,
a
point.
So
if
you
go
to
drift
off,
that
comes
the
sharepoint
SPF
x,
webparts
and
guidance
tag.
There's
now,
six
or
seven
individual
articles
there,
and
some
of
that
them
are
really
knew
from
this
week
as
well.
B
I
think
we
pushed
three
new
articles
in
here,
and
one
is
spending
for
me
to
actually
get
it
merged
with
the
lifter
of
system,
so
new
guidance
stuff
how
to
do
stuff,
how
to
do
certain
customization
or
steps
or
requirements
or
whatever
is
needs
to
be
done
in
a
SharePoint
frameworks
line
and
we're
looking
into,
for
example,
right
now,
we're
building
guidance
around
the
localization.
So
how
to
do
localization
would
ship
on
framework.
B
Clients
are
big
pots,
which
no
doubt
is
a
really
really
important
thing
for
enterprise
customers
as
well,
but
please
do
have
a
go
and
have
a
look
on
those
and
we
keep
on
evolving
this
site
as
we
move
forward
already
right
now.
If
you
find
an
issue,
for
example,
in
any
of
this
guidance,
any
of
these
articles,
you
can
go
to
a
key
top
there's
a
link
with
in
that
article
to
go
to
the
key
top
and
you
can
submit
a
pull
request.
B
So
we
can
get
all
of
the
stuff
updating
and
at
least
submit
an
issue
and
we'll
get
it
fixed
in
the
end
articles,
if
you
run
in
any
random
issues
with
this.
Some
of
these
articles
are
still,
let's
say,
older
versions
of
the
SharePoint
framework,
because
we've
been
having
six
drops
before
the
upcoming
release
candidate,
so
there
might
have
been
some
changes
as
we
move
along,
but
for
these
months
as
well
we're
working
on
getting
them
upgraded
on
the
release
candidate
level
immediately
when
to
release
candidate
is
available.
B
That's
a
really
high
priority
for
everybody
or
everybody
working
on
the
document
side
right.
It's
just
kind
of
a
walking
through
that
one.
So,
right
now
the
documentation
and
labs
are
currently
in
the
top
six
level.
Some
of
our
samples
are
older.
In
the
samples
we
are
actually
indicating.
The
version
which
they
have
been
built
in
the
sample
rate
may
fall,
so
you
know
exactly
had
what's
the
version
of
done
when
we
start
off.
B
Creating
those
samples
to
the
release
candidate
will
update
that
tag
to
match
that
it's
actually
release
candidate
as
well
release
candidate
coming
really
soon
so
early
January.
It's
now
already!
Well,
fifth,
that's
pretty
early
yeah
this
January
and
like
mention
we
can
update
the
tutorials
and
they
are
going
to
be
released
at
the
same
time
as
the
release
candidate.
So
those
five
relatively
simple
tutorials
getting
started
tutorials
so
that
they
are
matching
what
they
have
released
within
the
nbm
side.
B
So
you
can
easily
actually
start
learning
views
to
release
candidate
because
there
are
some
changes
within
the
release:
candidate
0.
These
are
not
a
significant
changes
from
a
fundamental
perspective,
but
there
are
some
API
changes
and
some
interface
changes
from
a
code
perspective
and
we
will
like
mention,
update
the
existing
examples
as
we
move
along
and
we
will
start
also
publishing
updated
with
videos
for
some
of
the
stuff.
B
What
we
have
done
in
the
past
fall
within
the
PMP
video
channel
so
because
some
of
the
stuff
is
actually
from
May
last
year,
so
we
need
to
do
a
refresh
and
explaining
where
we
are
and
what
are
the
steps
and
kind
of
a
refreshed
at
that
situation.
Now
that
we
are
heading
to
the
release
candidate,
we're
so
close
to
the
ga
from
a
code
perspective
and
that
this
will
be
lots
more
aligned
in
a
longer
run
as
well
Kinnick
started
with
SharePoint
framework
training.
B
We
talked
about
this
one
in
the
previous
special
interest
group
call
on
the
twenty-third
of
December.
We
include
the
car
Nevada
chinden.
What's
coming,
this
is
getting
closer
and
closer
most
likely
it's
going
to
be
released
around
end
of
January,
so
we
do
have
a
vendor
working
on
this
one,
and
then
we
from
BG
on
engineering
side
are
reviewing
that
stuff
and
all
of
that
right
now
we're
bending
for
release
candidate
0
for
that
one
as
well.
B
So
we
get
all
of
the
existing
Maps
updated
on
the
on
the
release
candidate
level,
and
then
we
can
push
that
material
to
be
available
and
that's
really
target
to
be
reusable
modules
for
anybody
to
redeliver
or
modules
that
material
for
you
to
learn
from.
So
there
will
be
presentations,
videos,
labs
and
demos
as
part
of
those
modules
so
that
they
are
easily
adaptable.
B
Huge
more
samples
under
key
top
organization
showing
different
aspects,
so
the
sample
site
is
growing
quite
nicely,
which
is
a
great
thing,
and
some
of
these
are
in
older
versions
like
mention
we
will
keep
on
updating
them
as
well.
Your
contributions
on
the
on
the
key
top
side
on
the
sample
calorie
is
more
than
welcome.
All
of
these
samples
are
getting
credited
in
our
monthly
communications
and
then
they're
getting
pushed
out
from
the
left
of
circum
as
well.
So
you
will
then
gain
some
visibility
on
on
based
on
your
contribution
right
now.
B
Some
of
the
samples
are
super
simple,
like
mentioned
as
well,
but
they
are
super
simple
for
a
reason,
because
we
want
the
people
to
have
simplistic
stepping
stones
so
that
they
know
how
to
get
started,
and
then
we
keep
on,
let's
say,
increasing
the
complexity
level
of
the
samples
further
on
during
springtime,
so
huge
OOP,
you
don't
have
the
latest
version
of
the
presentation
uploaded
or
maybe
my
saving
actually
and
didn't
go
through.
So
what
I
wanted
to
quickly
do
and
let
me
share
my
screen.
B
A
B
Got
it
here,
we
got
it
excellent,
brilliant.
Somebody
actually
said
it
exactly
what
I
requested,
which
is
awesome
so,
and
this
is
a
release
candidate
version
of
the
SharePoint
framework
and
double
you
can
actually
see
that
from
the
package.json.
So
I'm
actually
running
a
internal
versions
right
now,
so
these
are
versions
which
are
not
yet
available
externally,
but
they
will
be
released
relative
assume.
So
you
are
able
to
start
working
on
things
and
one
of
the
key
things
which
are
making
things
slightly
cleaner,
at
least
from
a
development
perspective.
B
Let
me
slightly
zoom
that
up
is
that,
for
example,
the
config
chasing
and
does
no
longer
have
any
entries
for
the
SPF
X
elements,
because
there
are
no
longer
considered
as
X
journals
because
their
internal,
their
sharepoint
stuff
they're
coming
from
sharepoint
online.
If
you
have
any
external
javascript
libraries,
you
would
still
list
them
here,
for
example,
in
my
jquery
sample
site.
Let's
go
in
here
if
I
have
a
reference
on
external
javascript
files
like
check.
Very,
I
can
reference
them
in
here,
but
you
don't.
B
We
don't
see
any
more
references
to
the
ship
and
frameworks,
specific
libraries,
which
is
a
good
thing,
and
the
other
thing
if
I
go
back
on
the
most
simplistic
web
port-
and
this
will
be
really
fast
for
untrue.
I'm
not
going
to
deep
dive
on
all
of
the
chances
is
that
we
have
simplified
that
the
basic
web
part
as
slightly
as
well
so
there's
no
longer
a
constructor
needed
for
the
web
parts.
B
That's
all
done
automatically
from
my
face
one
side
webpart
this
from
a
base
class
perspective
and
then,
if
you
need
to
overwrite
the
constructor,
you
can
still
do
that
and
you
need
to
do
that.
For
example,
if
you
are
one
unload
dynamically
external
CSS
files
like
in
the
one
of
our
lamps,
which
is
for
jquery,
where
we
actually
download
ace
or
make
a
reference
to
the
CSS
file,
which
we
then
we're
going
to
use
within
our
web
part,
what
else
there's
few
additional
properties
like
data
version.
B
So
this
is
relating
on
the
on
the
handling
of
of
versioning
changes
within
our
web
part.
So
if
you
are,
for
example,
as
part
of
your
new
version
of
the
web
part,
you
need
to
switch
between
a
versions
or
do
you
need
to
modify
the
data
which
the
web
part
has
a
dependency
on.
You
can
actually
do
that
based
on
this
information,
but
other
than
that.
Nothing
super
super
major.
From
that
perspective,
it
looks
pretty
much
like
it
was.
B
B
One
thing,
what's
most
likely
you
will
run
into
is
that
the
module
loader
is
nowadays
called
SP
loader
and
that's
really
kind
of
a
most
impact
being
practical
chains,
most
likely
and
there's
an
SP
component
loader,
which
is
then
can
be
used
for
loading,
JavaScript
files
and
CSS
files
from
external
location.
In
this
case,
we
have
a
reference
to
the
CSS
file,
and
then
we
are
using
that
jQuery
UI
within
our
rendering
relatively
simple
stuff.
B
Obviously,
if
you
missed
it,
the
workbench
is
nowadays
available
in
every
single
sharepoint
site,
which
is
a
big
chains
that
was
already
announced.
I
can
drop
five,
but
now
in
the
in
the
release
candidate.
We
actually
have
this
nice
warning,
so
the
the
workbench
sharepoint
online
version
of
work
pants
actually
realizes
that
hey
by
the
way
you
you're
not
actually
running
your
web
part
locally.
So,
therefore,
if
you,
if
you
are
looking
into
adding
that
web
part
on
this
page,
it
won't
be
available
smoking.
B
But
I
think
that
will
be
slightly
helpful
and
because
every
now
and
then
you
you
forgot
the
Duke
of
serve,
guess,
there's
no
pros
or
whatever
in
your
comment
line
and
then
a
sec
where's,
my
web
part,
why
isn't
available?
So
it
is
recognizing
that
as
well
as
other
than
that,
there's
really
no
changes
from
a
workbench
perspective
side.
There's
some
small
adjustments
and
changes
also
on
the
under.
How
do
we
actually
called
HTTP
requests
and
how
do
the
puter
HTTP
requests,
but
we'll
get
all
of
those
and
documented
in
readme
files?
B
So
you'll
know
exactly
how
to
do
that,
but
right
now
it
seems
to
be
well
it's
it's
over.
Is
it
available
what
how
complex
your
existing
web
parts
are?
So
if
you
build
anything,
do
you
rather
want
to
start
from
scratch?
So
you
have
a
clean
table,
or
do
you
actually
going
to
start
converting
them
to
use
the
latest
version?
Maybe
actually
one
thing
what
I
wanted
to
quickly
mention
is
that
we're
moving
into
the
types,
a
handling
so
using
the
MPN
to
installing
the
types
rather
than
using
the
pipes
typing?
B
So
super
super
fast
explanation
and
nothing
really.
New
I
didn't
work
through
all
of
the
details,
but
you
get
some
sort
of
an
idea
where
we
are
and
what
are
the
key
changes.
May
a
webpart
implementation
perspective
and,
let's
switch
back
on
the
slides
Patrick
you
can
actually
take
it
over
and
I
can
have
a
look
on
the
IM
discussion.
If
there's
anything
interesting,
let's
actually
stop
sharing
before
you
want
to
do
that.
A
Somebody
could
just
confirm
for
me
real,
quick
yep.
Thank
you
cool,
so
quick
updates
here
on
the
JavaScript
core
component
and
will
show
off
a
little
bit
the
documentation
that
we've
been
working
on
first
off
couple
links
at
the
bottom
I
still
have
not
updated.
The
github
link
so
note
to
self
you've
got
the
NPM
package
and
then
as
well
the
git
er
discussion,
which
is
a
great
place.
If
you
have
quick
questions
or
things
like
that,
so
we've
gone
over
that
for
again
thank
you
to
everybody
that
has
contributed.
A
Think
it'd
be
really
helpful
for
everybody
to
see
what
other
folks
in
the
community
or
building
and
how
they're
building
it
the
various
techniques
I
know
we're
learning
a
lot
from
everybody
out
there.
So
it's
really
exciting
to
see
what
you
all
are
building
and
in
some
cases,
it's
stuff
that
we
had
never
even
imagined
folks
would
build
with
the
SharePoint
framework,
so
very
exciting.
A
A
Then,
of
course,
you
can
also
contribute
on
github
either
by
submitting
code
reporting
issues
or
just
general
feedback,
always
really
appreciate
that,
and
you
can
also
contribute
to
the
wiki,
which
is
what
we'll
talk
about
here
in
a
little
bit
and
then
providing
feedback.
So
just
general
feedback
on
this
call
or
through
any
of
the
various
social
channels
we've
talked
about
throughout
the
call,
so
either
the
tech
community
get
er.
You
know
those
sorts
of
things.
You
can
even
find
this
on
twitter
if
you
have
feedback
and
want
to
get
at
us
that
way.
A
So
next
thing
I
wanted
to
mention
is
we
talked
last
call
about
the
growth
of
the
library
and
so
I,
look
at
the
numbers
for
December
and
wanted
to
share
them
as
I.
Think
it's
really
exciting
to
see.
A
We've
only
got
a
hundred
and
ninety
seven
million
requests
a
month
to
go
to
catch
or
no
997
requests
a
month
to
go
to
catch
the
core
library,
but
we
will
not
too
much.
We
will
overtake
them
and
but
anyway
it
all
seriousness.
It's
very
exciting.
Growth
and
I
just
wanted
to
share
that
with
all
of
you,
because
it's
something
we're
all
doing
as
part
of
this
community
is
the
seen
this
growth.
It's
not
something
you
know
we're
driving
from
engineering,
it's
something
you
all
are
driving
out
there
in
the
field.
A
So
some
updates
we're
moving
very
much
closer
to
the
two
down
over
least
like
I
said
we
had
lots
of
updates
over
the
holiday
he's
got
some
great
feedback
from
folks.
Russell
was
very
active
in
a
couple
others
and
getting
us
some
feedback
Mauricio
as
well.
I
remember,
got
some
stuff
out
there
over
the
holiday.
So
it's
really
great
to
see
that
I
think
we've
got
a
solid
code
base.
A
Here
in
a
second,
the
other
thing,
I've
spent
a
lot
of
time
recently
working
on
is
improving
our
Docs
and
examples
ahead
of
this
2
dot,
0
release,
and
so
one
thing
we'll
look
at
those
here
in
a
second
and
kind
of
want
to
show
you
guys
what
I've
been
doing
and
also
I
want
to
talk
a
little
bit
about
Doc's.
One
of
the
things
we
hear
a
lot
is
you
need
more
documentation,
and
so
that's
kind
of
always
going
to
be
true,
but
I
want
to
mention
two
things
about
that.
A
The
first
is,
if
you
see
a
gap
in
documentation,
we
absolutely
welcome
contributions
to
help
with
that.
That's
a
great
place
to
help
contribute
and
it's
a
great
place
to
really
help
out
the
community.
So
if
you
see
a
place
where
our
docs
are
lacking-
and
you
have
a
little
bit
of
time,
I
certainly
invite
you
to
write
a
wiki
article
that
be
very
welcome,
and
the
other
thing
I
wanted
to
mention
around
documentation
is
a
sort
of
it's
a
two-part
thing,
and
the
first
is
we're
getting
some
questions
around.
A
A
Well,
we'd,
certainly
invite
if
you
were
to
create
a
sample
once
you
solve
that
problem
for
your
customer
and
roll
that
back
out
to
the
community,
we
would
love
to
get
that
included
and
involved
to
help
everybody
else,
but
the
other
part
is
just
saying
or
asking
for
more
documentation
it
as
helpful
as
telling
us.
A
You
know,
having
a
more
specific
ask
around
I
wish
you
were,
you
had
documentation
on
how
to
add
list
items,
for
example
write
something
you
know
very
specific,
and
that
helps
us
kind
of
track
that,
and
we
can
actually
build
an
issue
around
that
and
work
to
resolve
that,
as
opposed
to
just
sort
of
this
overarching
more
documentation.
But
we've
taken
that
to
heart
and
I
want
to
show
you
some
of
the
stuff.
We've
been
working
on
to
help
with
the
documentation
story
here
very
shortly.
A
So,
two
months
at
the
bottom
again,
the
community
and
the
the
guitar
great
places
again
for
feedback
and
giving
back
to
the
community.
So
a
quick
demo
from
me
on
documentation,
which
is
always,
I
think
I
can
get
the
thing
to
go
there.
We
go
one
of
the
more
exciting
topics
to
discuss,
so
somebody
just
mentioned
to
me.
It
looks
like
it's
up
for
me
or
other
folks,
seen
my
desktop
at
this
point.
A
Yep,
okay
cool,
so
the
folks
are
seeing
that
so
I
want
to
jump
over
here.
So
this
is
our
repo,
and
the
first
thing
I
want
to
mention
is,
like
I
said
in
the
dev
branch.
This
is
essentially
the
two
dot
o
release
candidate.
So
if
you
want
to
pull
down
and
play
with
this
and
give
us
feedback,
would
very
much
appreciate
that
as
we
move
towards
releasing
it
we'd,
like
obviously
the
20
release
to
be
as
solid
as
possible.
A
But
what
I
wanted
to
really
talk
about
is
some
stuff
we've
been
doing
in
the
wiki
sort
of
help
with
this
idea
of
needing
more
documentation.
So
until
the
two
da
no
release,
we
have
not
updated
the
menu
here
on
the
right,
but
you
can
get
to
the
pages
using
this
little
pages,
toggle
thing,
and
so
you
can
see,
we've
added
a
whole
bunch
of
articles,
and
I
want
to
show
you.
We've
got
one
from
moving
for
10
to
20,
so
talking
about
some
of
the
changes
there
and
then
so
trying
to
be.
A
You
know
a
little
bit
more
explicit
about
this,
but
we've
also
are
starting
to
add.
Instead
of
making
folks
go
out
to
the
samples
or
go
look
at
the
blog
posts,
things
like
that
we're
pulling
these
things
into
the
wiki
to
talk
about.
You
know:
here's
how
to
use
this
so,
hopefully
again
helping
folks
who
are
coming
to
the
library
or
a
new
to
the
library
or
have
been
using
it
and
have
questions.
A
So
we've
got
an
article
now
on
basic
operations,
so
how
to
read
data:
how
to
use
some
of
these
Oh
data
operations
such
as
filter
and
skip,
and
how
to
add
an
update
values
to
doing
some
very
basic
operations.
We've
got
pages
now
talking
about
how
to
use
the
batching
and
how
the
batching
works
as
well
with
caching,
so
we're
building
that
out.
We've
got
pages
on
some
more
advanced
topics.
This
was
a
piece
of
the
feedback
that
came
in
over
the
holidays
is
maybe
I
need
to
write.
A
My
own
fetch
client,
essentially,
so
we've
got
an
article
here
on
writing
your
own
fetch
client,
something
you
know
so
trying
to
help.
A
Folks,
again,
we've
got
more
detailed
articles
on
debugging
and
so
how
to
do
actual
debugging,
both
individual
studio
code
and
then
in
browser,
so
trying
to
really
help
folks
walk
through
some
of
this
stuff
and
then
let's
see
and
so
and
then
we've
got
the
last
article
I'll
sort
of
show
you
I'm
not
going
to
go
through
all
of
these,
but
we've
got
an
article
here
on
the
response,
parsers
sort
of
how
they
work
and
then,
if
you
need
to
create
a
custom
one
how
to
go
about
that
so
again
we're
trying
to
get
that
documentation
out
there
we're
trying
to
be
responsive
to
that
feedback.
A
But
my
asked
to
all
of
you
is:
if
you
have
a
need
for
a
piece
of
documentation,
let
us
know
but
be
as
specific
as
possible.
So
you
know
something
around.
If
we
had
documentation
for
one
of
the
questions
that
came
in
is
not
actually
over
the
holidays.
I
goes
this
week.
Is
there's
no
documentation
on
how
to
configure
the
library-
and
there
actually
was,
but
it
was
off
on
a
blog
post.
A
A
We
really
are
trying
to
make
it
easier
and
trying
to
get
the
more
docs
out
there,
but
so
my
two
asks
if
you
have
a
need,
be
as
specific
as
possible,
if
you
have
some
time
I
believe
everybody
can
edit
the
wiki
or
add
pages
to
the
wiki.
If
that's
not
true
somebody
just
let
me
know
and
we'll
check
the
permissions
since
we
moved
repositories.
The
permissions
might
have
reset,
but
so
definitely
welcome
help
on
writing
these
articles
and
that
just
helps
all
of
us
in
the
community.
A
So
we'll
jump
back
to
the
slides
I
know
my
mind:
wasn't
as
cool
as
vases,
because
documentation
is
always
fun
but
I
think
it's
very
valuable
and
I
think
it's
trying
to
meet
a
need
and
respond
to
some
feedback
from
folks
out
in
the
community.
So
we'll
just
kind
of
open
things
up
now
and
we'll
head
I've
got
plenty
of
time
for
discussion.
A
So
folks
have
questions
or
comments.
Welcome
those
here
in
the
call
was
SPX
SP
FX
covered
at
the
start
of
the
call.
Yes,
specifically,
this
question:
let's
go
look
at
this
question:
I
isono
clarification
on
SP,
FX,
dependent
library,
versioning
and
roll
out
policy.
Well,
this
is
a
very
long
question.
I
would
not
be
the
one
to
answer
that
that
would
be
visa
and
or
probably
hat
and
team
on
that
one
so
I
don't
know
if
they.
A
So
if
you've
had
a
chance
to
look
at
that
one
or
you
know
something
have
any
feedback.
Yeah.
B
B
B
C
C
So
it
it
base
it's
a
question,
I
see
coming
up
a
bunch
and
it's
really
just
not
just
about
the
dependency
on
the
versions.
But
it's
you
know
to
understand.
When,
when
developers
are
taking
a
dependency
on
what
Microsoft
is
putting
on
the
page,
then
you
know:
how
are
we
to
know
when
you
roll
out
a
new
version
of
react
or
if
we're
using
an
existing?
If
we
are
mitigating
an
issue,
that's
already
out
there
or
something
like
that,
and
then
it
because
it's
a
it
ends
up
being
something
that
you
know.
C
We
kind
of
have
to
need
to
know
if,
like
when
you
roll
out
an
update,
if
we're
addressing
a
workaround
and
the
role
I,
the
rollout
comes
out
without
us
really,
knowing
that
it's
coming
out,
then
all
the
sudden,
our
stuff
can
break
without
really
knowing
in
the
whole
classic
of
some
tenants
get
at
some
tenants.
Don't
I
get
that
you
know
we're
still
in
the
dev
preview
and
you
guys
don't
may
not
have
the
policy
yet,
but
is
there?
Is
there
something
that
we
can
a
timeline
that
we
can
expect
to
see?
C
B
Would
say
that
most
likely,
we
need
to
unfortunately
wait
this
for
chie.
We
said:
let's
put
it
this
way.
This
problem
exists
even
for
us
in
the
engineering
side
because
to
react
this
evolving
so
fast
as
well.
So
we
need
to
tackle
that
first
in
engineering
and
then
we
need
to
figure
out
a
noble
to
share
the
police,
for
you
guys
and
ISVs,
and
customers
and
partners
and
everybody
else,
and
we
need
to
get
it
solved,
but
just
being
realistic.
B
On
the
current
situation
from
an
engineering
perspective,
the
release
candidate
is
coming
out
relatively
soon,
like
mentioned
in
earlier
of
the
call.
But
then
everybody
wants
to
concentrate
on
a
chie,
and
that
means
that
priorities
are
during
that
time,
targeting
the
chie
of
so
I
would
be
highly
surprised
if
we
can
tackle
this
question
and
the
challenge
before
the
g8
elf.
But
we
need
to
tackle
that
by
GA.
C
B
Absolutely
absolutely
because
otherwise
we
would
lose
the
credibility
of
the
platform.
So
it's
it's
super
clear
that
it
has
to
be
there
it's
one
of
them.
Once
again,
it's
one
of
those
things,
tasted,
it's
a
matter
of
resources
and
getting
things
done
and
even
though
we're
Microsoft,
we
don't
have
been
a
feeling
that
resource
list
and
I
know
that
people
have
heard
this
story,
but
many
times
before,
but
that's
realities
of
life.
So
no.
B
B
B
And
that
has
a
list
of
kids
applications
that
have
a
which
are
including
the
sharepoint
framer
of
stuff,
including
also
the
classic
PMP
stuff,
including
also,
even
though
some
of
these
addresses
are
in
quotes
old
because
removed
from
office
type
organization.
The
shipment
organization,
github,
is
magical
and
it
sa
a
full
redirection
functionality.
So
you'll
find
the
right
location
from
there
and
then
the
YouTube
videos
are
shared
by
David
as
well.
B
Any
other
other
questions
discussions
one
thing
but
I
wanted
to
quickly
ask
I,
don't
know
how
many
of
you
actually
noticed.
We
pushed
the
webcast.
Was
it
last
Monday
or
monday
before
that
one
around
how
to
do
modern
web
stack
development
in
on
premises
as
well,
so
using
the
to
react
using
the
gulp
using
the
modern
way
of
doing
stuff,
we
didn't
go
on
premises
using
them
script,
a
little
bit,
part
in
a
sharepoint,
2013
or
2016,
or
even
content
editor
web
part
in
ship
on
2010
and
time
frame.
B
We
know
that
that
was
slightly
confusing
in
the
European
sharepoint
conference.
In
a
keynote
we
showed
that
originally
Emma,
for,
unfortunately,
we
even
used
the
same
colors.
So
then
we've
got
Twitter
tweets,
which
were
saying
sharepoint
rain,
where
it
goes
to
sharepoint
2010,
and
it's
like.
No,
that's
not
what
we
showed
up
fair
point,
fair
point.
B
B
The
Cortana
demo
was
epic
as
well
in
that
european
sharepoint
conference,
oh
yeah,
the
head
that
was
pretty
critical.
Indeed,
I
got
a
very
good
reaction,
I
think
yeah
that
yeah
that
got
really
good
reaction.
Unfortunately,
even
though
europe
and
sharepoint
conference,
they
got
the
keynotes
recorded,
but
the
recording
of
the
keynotes
only
shows
us
in
the
stage
they
don't
actually
show
what
we
showed
with
this
ridiculous,
so
pretty
much
useless.
Unfortunately,.
B
B
So
you're
honest
is
asking
if
the
PowerPoint
bi
web
part
coming
back
on
the
release
candidate
or
ga.
So
there
was
a
power
PR
web
part
available
for
the
modern
pages
and
I'm
not
actually
sure
where
we
are
that
one,
because
technically
it's
not
part
of
the
ship
on
framework,
it's
a
a
feature
which
is
being
developed
by
a
completely
different
feature,
crew,
which
are
then
using
the
ship
on
framework
to
make
that
happen,
but
just
out
of
careers
that
I
can
actually
have
a
quick
look,
maybe
from
our
edik.
B
B
B
B
B
B
B
B
Any
other
random
discussion
points
for
feedback.
What
am
I
missing
from
a
shape
on
framework
perspective?
That's
actually
always
an
interesting
discussion,
so
we've
been
working
on
the
guidance
and
the
certain
MVPs
we've
been
working
with
MVPs
on
getting
some
of
the
stuff
available
and
it's
moving
along
nicely
and
obviously
there
might
be
much
much
more
material
and
all
of
that,
but
that's
again
matter
of
resources,
know
what's
missing,
is
the
key
point
and
are
we
missing
some
clear
scenario,
clear
documentation?
Obviously,
but
AC
said
already,
it
should
be
clear.
B
We
need
to
make
sure
that
we
have
a
clear
strategy
and
process
how
to
tackle
the
versioning
so
that
that's
clear
then
that's
absolutely
needed
to
anybody
to
the
build.prop,
a
production-ready
stuff.
What
else
would
be
missing?
Production
version?
Absolutely
yes,
and
we're
expecting
and
hoping
that
immediately
when
we
are
heading
to
the
ga,
there
will
be
much
more
interest
on
the
ship
on
framework
as
well.
B
Yeah
I
need
to
find
the
original
how
the
provision
aired
if
environment
for
PMP
work,
video
stare
point.
It
depends
on
what
the
MP
area
are.
We
explicitly
talking
about.
That's
the
challenge.
Obviously,
now
on
the
ship
on
framework
side,
the
left
office
that
comes
the
SharePoint,
we
do
have
that
getting
started
steps
over
there.
But
then,
if
it's
something
else
than
that,
then
do
we
have
an
exact
steps
somewhere,
I,
don't
even
think
so.
Now
we
have
too
many
materials
on
of
the
two
different
areas
of
the
empty.
B
So
probably
the
ignite
ignite
one
is
showing
kind
of
a
walk
through
the
Atlanta
ignite.
The
PMP
session
at
least
was
kind
of
a
walkthrough,
and
this
is
what
we
are
doing,
and
this
is
what
you
can
do.
There
was
a
lot
of
demos
on
that
session.
That's
pretty
close,
but
it
doesn't
explicitly
tell
watching
it
in
stock
and
to
get
started
or
might
have
mentioned
that
during
the
presentation,
I
I
can't
remember,
I,
barely
remember
what
I
did
yesterday,
so
remembering
something
what
I
did
in
September
ya
can
can't
remember
that.
B
And
and
obviously,
if
there
isn't
any
questions,
we
don't
have
to
hang
on
the
line.
So
that's
absolutely
fine.
If
there's
any
questions
for
the
PM
pjs
core,
oh
by
the
way,
maybe
a
one
related
to
side
discussion
in
the
VMP
team.
We've
been
chit
chatting
on
the
on
the
name
of
the
PM
pjs
core
and
we
don't
think
that's
super
cool.
B
B
We
should
maybe
do
a
a
competition
on
on
the
naming
like
mango
chase
no
Apple
to
know
we
can
to
support
anyway,
not
quite
a
question,
but
I've
been
following
the
PMP
courgettes
library
for
a
while,
but
only
being
just
able
to
approach
it
and
have
been
impressed-
and
these
are
patching
alone-
is
a
killer
and
that's
great
feedback.
No
doubt
okay
is
if
we
don't
rename
well
how
much
is
yeah.
That's
that's
a
good
suggestion.
B
Yeah
renaming
is
always
bad
over
sleep,
because
when
somebody
is
getting
slightly
more
attention
than
people
rename
and
poof,
then
you
can't
find
it
anymore.
So
to
be
fair,
the
name
isn't
meaningful
as
long
as
people
are
finding
stuff
useful,
that's
really
the
key.
So
if
it's
available
who
keep
on
and
people
keep
on
using
them.
A
B
Fair
sounds
good
cool
I.
Don't
think
we
have
anything
special
at
this
point,
but
like
mention
the
release
candidate
super
soon
coming
out,
please
follow
the
record
of
circumstance,
blocks
and
our
Twitter
accounts.
We
will
push
out
communications
immediate
and
then
the
imperatives
have
been
updated
and
then
we're
already
relatively
close
on
the
on
the
ga,
which
is
a
good
thing,
and
we
will
release
the
release
notes
as
well
in
the
in
the
typical
location.
So
you
know
how
to
adapt
your
existing
projects,
but
this
is
a
a
relatively
big
change.
B
So,
let's
see
if
you
can
adapt
your
existing
projects
or
will
you
have
to
let's
say
rebuilds
some
of
the
stuff,
which
is
we
know
that
it's
painful,
but
we
rather
do
it
right
now,
rather
than
waiting
for
GA
and
then
do
a
a
full
reshuffling
at
that
point,
but
next
seek
for
JavaScript,
correll,
SP,
FX
and
JavaScript.
Coral
is
done
19th
of
January
and
let's
make
sure
that
we
have
a
few
live
demos
on
new
stuff.