►
From YouTube: SPFx JavaScript SIG 8th of June, 2017
Description
No description was provided for this meeting.
If this is YOUR meeting, an easy way to fix this is to add a description to your video, wherever mtngs.io found it (probably YouTube).
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
meeting
is
june.
8Th
2017
got
a
couple
really
cool
demos
here
for
you
today
and
want
to
jump
right
into
it,
but
first
as
always,
we
want
to
start
with
what
are
we
all
about?
What
are
we
doing
on
the
calls
and
kind
of
what's
the
purpose
of
this?
A
So
we
are
a
subset
of
the
SharePoint
patterns
and
practices
program
and
we
focus
on
client-side
development,
very
specifically
around
SharePoint
framework
and
is
well
around
building
this
JavaScript
core
component
to
help
folks
with
their
client-side
development.
So
that's
kind
of
why
we
were
started
is
to
give
folks
interested
in
client-side
development
a
little
more
of
a
focused
session,
whereas
you
know
kind
of
we
weren't
able
to
cover
in
a
lot
of
detail
and
sort
of
a
monthly
community
calls,
and
we've
done
the
same
thing.
A
So
if
you're
interested
as
well
in
the
core
component
or
the
PowerShell
component,
please
do
check
out
there's
a
special
interest
group
for
those
as
well.
You
can,
of
course,
attend
as
many
of
these
calls
as
you
like.
We're
always
happy
to
see.
Folks,
on
the
calls
so
down
at
the
bottom,
we've
got
two
links
to
aka.ms/offweb.
A
Development,
specific
development
questions
best
practices,
things
like
that.
The
bottom
link
dev
office,
comm,
slash
SharePoint-
is
your
one-stop
shop
for
all
things:
SharePoint
development,
so
whether
you
are
new
to
and
want
to
learn
about
the
SharePoint
framework,
whether
you're
doing
add-in
development
or
whether
you're
doing
full
trust
code
solution
development.
You
can
find
resources
for
that
at
that
link.
So
we've
got
all
we
it's
not
completely
done.
A
A
A
Pardon
me
so
I
cheated
a
little
bit
told
you
some
of
what's
coming
up,
but
we'll
have
a
quick
update
on
the
JavaScript
core
component
base,
so
we'll
go
over
the
SharePoint
framework
latest
news
as
well
as
some
some
news
about
those
four
work.
Extensions
base
is
going
to
show
those
off
and
we've
got
Andrew
Colt
chakal.
A
A
We
definitely
welcome
and
encourage
and
are
looking
for
folks
in
the
community
who
want
to
demo
a
SharePoint
framework
web
part
or
or
now
a
SharePoint
framework
extensions
project
that
they've
worked
on
something
you
know,
cool
that
you've
worked
on.
You
just
want
to
show
it
off,
it
can
be
production
ready
or
it
can
be
kind
of
just
a
sort
of
proof
of
concept
as
well
anything
involving
the
JavaScript
core
library
or,
in
general
anything
around
client-side
development.
A
Happy
to
have
demos.
Discussions
on
that
as
well.
We've
had
some
really
neat
stuff
on
different
frameworks.
Other
you
know
different
techniques,
people
use
it
for
general
client-side
development,
which
I
think
is
really
exciting,
contribute
on
github.
So
for
the
JavaScript
core
component
or
any
of
the
other
repos
for
the
SharePoint
framework
stuff
and
provide
feedback
so
that
contributed
on
github
is
part
of
the
feedback,
so
submitting
issues
submitting
issues
around
the
SharePoint
framework
or
any
of
the
other
patterns
and
practices
stuff.
A
That
feedback
really
drives
one
of
getting
issues
fixed
and
to
development
of
new
features.
So
when
we
hear
somebody's
like
can
we
do
X
and
we
look
at
it
and
we
say
well
yeah.
We
can
help
with
that.
That
absolutely
is
feedback
we
want
and
we're
excited
to
help
bring
those
new
features
in
you
know
as
possible
as
its
supported
by
the
underlying
api's
and
as
well
matches.
A
You
know
with
our
ability
to
deliver
that
so
great
opportunities
to
contribute
again,
if
you
ever
want
a
demo
open
invitation
to
anybody
either
on
the
call
today
or
watching
the
video
in
the
future
just
get
in
touch
with
us.
We'd
love
to
have
you
demo
so
reach
out.
So
quick
updates
here
on
the
JavaScript
core
component,
we're
going
to
release
206,
Monday,
June,
12th
and
I'm
holding
off.
Originally,
it
was
scheduled
for
tomorrow
Friday,
but
I
did
want
to
give
folks
one
more
chance.
A
There's
a
I'm
not
going
to
say
a
lot
of
issues,
but
there's
some
issues
that
have
been
reported,
that
we
had
follow-up
questions
on,
that
we
couldn't
necessarily
reproduce
or
it
wasn't
clear
to
us
what
necessarily
the
issue
was
so
I
wanted
to
give
folks
one
last
chance
to
follow
up.
You
know
give
us
some
more
details,
answer
our
questions,
because
we
would
love
to
fix
these
issues
or
unblock
folks
or
or
solve
whatever.
The
problem
is,
but
we
need
a
little
bit
more
information
on
some
of
the
stuff.
A
That's
out
there
just
a
reminder
if,
if
you've
submitted
an
issue-
and
we
think
we've
answered
it
and
we've
closed
it,
please
do
reopen
that
issue.
If
you,
if
you
need
to
continue
the
conversation
or
have
additional
questions,
it's
very
easy
for
us
to
miss
things
when
they're
not
reopened.
So
please
do
reopen
it.
We're
very
happy
to
continue
helping.
You
know
if
you
keep
having
problems
or
additional
questions
or
need
some
clarification.
We
really
do
want
to
help,
but
it's
just
very
easy
for
us
to
miss
stuff
if
it's
not
reopened.
A
So
please
do
reopen
those
issues.
I
also
want
to
don't
be
afraid
to
mark
issues
as
a
question.
We've
got
different
categories
there
we're
not
going
to
ignore
it.
If
it's
a
question,
we
do
again
want
to
help
very
much,
but
it
helps
us
just
understand.
What's
coming
in
and
track
it
a
little
better.
So
if
you
found
a
bug
with
the
library
feel
free
to
mark
it
as
a
bug,
we'd
love
that
we'd
love
to
get
it
fixed.
But
if
you
have
more
of
a
question,
please
do
mark
it
as
a
question.
A
It
just
helps
us.
You
know
kind
of
categorize
things
and
see
what's
coming
in
a
little
bit
and
it's
definitely
not
going
to
get
ignored
if
you
don't
mark
it
as
a
bug.
So
just
a
quick
note
there,
so
I
did
want
to
give
a
little
bit
of
update
on
graph.
So
some
of
you
have
heard
or
seen
that
the
graph
httpclient
is
part
of
is
going
to
be
part
or
is
part
depending
on,
if
you're
in
the
dev
preview
or
not
of
the
SharePoint
framework.
A
So
we're
going
to
start
there
because
that's
going
to
simplify
all
sort
of
the
authentication,
plumbing
and
those
sorts
of
things.
So
we
can
sort
of
build
our
fluent
API
around
that.
What
that
doesn't
solve
is
wanting
to
call
graph,
for
example,
from
nodejs
or
from
well
anywhere
outside
of
the
SharePoint
framework.
So
my
thinking
there
is,
let's
do
it
one
step
at
a
time.
A
At
all,
I
can
node
and
another
comment
on
graph.
What
will
probably
end
up
doing
is
producing
X
stro
files
and
what
I
mean
by
that
is
so
right
now,
there's
like
pee
and
PJs,
we're
probably
going
to
end
up
with
something
like
pee
and
PJs
will
be
everything
and
we
might
have
PNP
gracias
and
PNP
s
PJs
as
all
part
of
the
dist
folder
for
folks
that,
if
you're
not
doing
anything
with
Graff,
maybe
you
don't
need
that
extra
weight
in
your
project,
so
we're
gonna
be
mindful
of
that.
We'll
look
at
that
again.
A
A
I
would
do
it
differently
from
everybody
in
the
call,
and
everybody
in
the
call
would
likely
do
it
different
for
me.
So
I
would
hate
to
have
a
solution
that
5%
of
the
people,
love
and
95%
of
the
people,
hate
that
seems
lame
and
there's
no
way
we
could
support
everything.
Everyone
wants
to
do
right,
it's
there's
no
way
to
be
that
generic
at
that
level,
like
a
level
above
what
we're
already
providing.
A
So
you
know
those
are
kind
of
the
reasons
and
I'm
also
not
sure
it
would
be
appropriate
for
us
coming
back
that
everybody
would
do
it
differently
and
everybody
wants
to
use
different
frameworks
that
all
work
a
little
bit
differently.
You
know,
for
example,
react
kind
of
handles
binding
a
little
bit
differently
than
say
angular,
then
against
a
knockout
it'd
be
really
hard
to
match.
All
that,
and
it's
also
I
want
to
say
a
perfect
opportunity
for
a
community
project.
A
You
know
us
from
sort
of
a
core
perspective
dictating
this
is
how
we
believe
you
should
create
your
objects
and
manage
your
objects,
because
again
I
don't
think
I
can
solve
that
problem
in
a
way
that
everyone
would
be
happy
with,
or
that
will
even
solve
the
problem
forever.
You
know
everybody's
needs,
so
I
think
it's
a
great
chance
for
a
community
project.
I
know,
there's
a
few
folks
out
there
already
working
on
things
like
this
and
I
would
very
much
encourage
you
to
do
that.
A
Let
us
know
how
it's
going
keep
us
in
the
loop.
If
there's
things
we
can
do
in
the
core
to
make
that
better
easier.
Please
do
let
us
know
again,
I
think
it's
very
valid
pursuit,
but
not
something
we're
going
to
pursue
and
push
out
from
kind
of
the
core
team
perspective,
at
least
at
this
point.
So
I
just
wanted
to
comment
on
that
a
little
bit.
So
in
line
with
all
that,
please
keep
all
the
amazing
feedback
coming.
A
There's
two
links
down
there
at
the
bottom
again
for
the
SharePoint
PNP
community
that
goes
to
the
same
Microsoft
community
and
then
our
git
er,
which
is
specific
to
the
JavaScript
core
library.
If
you
have
comments,
questions
around
the
core
library,
please
do
hit
us
up
on
get
er
so
now
pass
things
over
to
VAE
CIL's.
So
he
can
give
us
an
update
on
the
SharePoint
framework.
B
B
So
there
is
an
updated
SharePoint
framework
devel
for
training
packets
available,
including
like
30
different
videos,
where
we
wear
patent
ski
all.
I
do
few
videos
interpreting
skills
during
rest
is
explaining
different
functionalities,
different
ways
of
eating
stuff
in
SharePoint
framework.
That's
only
for
client-side
web
parts
right
now
and
it's
going
to
be
updated
at
some
point.
Really
the
key
point
of
this
one,
just
wanna
in-phase,
that's
in
the
messaging
as
well.
This
is
meant
to
be
for
you
to
use
any
way
you
want.
B
So
if
you're
looking
into
delivering
a
local-
let's
say
trading
in
your
region
or
within
your
countries
now,
if
you
can
pull
down
the
material,
you
can
modify
that
in
a
way
you
want,
and
you
can
do
that
and
deliver
done
or
if
you
want
to
just
use
the
slides
in
a
conference.
Presentation
feel
free
to
do
that
as
well.
So
there's
a
lot
of
value
within
the
package:
go
cool
on
the
SharePoint
frameworks,
so
the
SharePoint
framework
extensions.
B
So
let's
actually
add
coats
this
true
with
few
slides
and
then
I'm
going
to
do
a
live
demo
and
I'll
be
watching
the
I
am
window.
If
there's
any
live
questions
around
this
one,
but
SharePoint
framework
extensions
is
now
available
in
that
preview.
It
is
available
in
death
tenants.
So
if
you're
using
a
first
release
tenants
or
a
normal
production
tenants,
it
is
not
available
there
yet.
So
you
need
to
have
a
deaf
talent.
B
Just
going
to
test
a
URL
and
paste
that
one
in
yes,
so
you
can
sign
up
on
the
office,
365
developer
program
and
you'll
get
a
free
office.
365
developer,
tenant
with
25
accounts,
so
you're
able
to
then
test
different
accounts.
Different
permissions
on
author
at
some
point,
I,
wouldn't
say
pretty
soon.
At
some
point
the
instance
will
go
in-depth
preview
in
first
release
dance
as
well,
so
we
will
so.
You
will
be
able
to
test
them
with
your
life
content,
but
they
will
be
still
in
deaf
preview.
B
B
My
understanding
actually,
unfortunately,
attested
that
and
I
saw
at
least
my
really
old
stiff
tenant
Alma
has
a
one
account
so
I,
don't
apparently
it's
not
activated
on
there.
Maybe
we
should
report
that
somewhere,
but
I'm
a
wrong
person
for
that
now
coming
back
on
the
extensions.
So
what
for
step-
and
we
think
going
through
this
a
lot
in
the
past
special
interest
group
course
as
well-
there's
three
different
extensions
to
start
with,
and
this
is
just
a
spark
for
looking
into
having
additional
extensions
as
well.
B
These
are
just
free
which
were
released
right
now
to
dev
preview.
We
saw
the
application
customizer
and
Lisa
come
on
set
and
Phil's
customizer.
The
application
customizer
is
there
to
extend
the
UI
or
n-bit
color
spring,
there's
two
kind
of
a
different,
distinct
scenarios.
So
you
can
modify
you
can
embed.
Let's
say
we
tetes
and
functionalities
and
Nick
you
make
footers
on
the
on
the
pages
using
the
application.
Customizer
or
your
JavaScript
might
be
just
running
on
a
page
without
actually
having
a
UI,
so
it
could
be
lets,
say
app
analytics
as
your
app
analytics.
B
B
When
somebody
clicks
a
button
and
there's
additional
intelligence
there,
so
you're
able
to,
for
example,
light
up
your
book
whenever
multiple
items
has
been
select
them
and
we
were
able
to
target
the
tool
or
the
context
menu
of
an
individual
item,
and
then
the
third
one
is
to
fill
customizer
to
modify
the
rendering
of
the
field
and
that's
right
now
in
the
read-only
mode.
We're
looking
into
extending
that
to
the
edit
mode
as
well,
but
those
are
the
three
different
distinct
models.
B
Give
me
one.
Second,
oh
yes,
so
sorry
for
sleeping
slightly
on
the
slides
I
needed
to
check
with
just
a
slight
sigh
I
took
for
this
community,
so
all
of
these
can
be
now
developed
in
the
dev
tenants.
We
do
have
a
special
debugging
experience,
I'm
going
to
show
that
one
in
practice
as
well.
If
you
want
to
deploy
them
truly
and
then
there's
a
few
things
which
need
to
happen,
so
you
need
to
deploy
the
SharePoint
solution
to
that
catalog.
B
You
need
to
update
it,
put
the
Chaves
key
files
on
the
CDN
and
then
install
the
application
to
an
individual
SharePoint
site.
All
this
is
actually
included
in
our
tutorials.
So
if
you
run
through,
for
example,
tutorial
for
field
customizer,
I
stop
scratch
us
send
to
code
you'll
modify
that
in
a
debug
mode.
Then
you
package
the
code.
Then
you
deploy
the
code
and
put
it
hosting
and
you
can
put
it
hosting
in
the
CDN.
So
you
understand
essentially
how
the
whole
flow
actually
works.
Personally,
I'm
pretty
pretty
happy
with
the
tutorials.
B
Quick
there's
already
a
clip
question
and
thank
you,
can
further
feedback
and
thanks
Chris
and
thanks
Chris
for
fixing
simulcram
ratios
and
so
on,
and
there's
a
good
question
from
Darren
around
the
sps
exams.
How
do
I
deploy
my
SPF
x2,
let's
say
100,000
site
collections
or
200
site
collections
or
whatever
pretty
soon.
There
will
be
a
capability
to
Quandt,
to
set
a
configuration
in
your
JSON
files
and
in
the
for
able
to
say
that
this
particular
customization
is
it
a
client-side
web
board
or
an
extension
should
be
automatically
available
across
all
the
sites.
B
So
you
do
not
have
to
explicitly
install
the
SPF
X
solution,
that's
like
by
site
basis.
So
that's
the
step
number
one.
The
step
number
two
will
be
API.
It
also
enable
installing
SPF,
X
solutions
or
add-ins
to
individual
sites
and
that's
being
expect
as
well.
So
we
absolutely
understand
the
requirement.
We
absolutely
understand
how
how
it
has
to
work
and
we
need
to
make
it
simple
and
it's
all
roadmap.
Some
of
that
has
been
already
developed.
It's
just
a
matter
of
getting
it
out
and
document
them
so
we're
getting
there.
B
B
This
is
kind
of
an
interesting
thing
around
the
extensions
and
I
think
we
didn't
show
this
one
in
the
last
special
interest
group
call
either,
but
to
be
able
to
debug
ship
on
framer
stations.
We
have
to
do
some
additional
things
and
the
SharePoint
framework
of
workbench,
the
local
documents
or
the
online
reference
currently
only
supports
webparts.
B
So
there's
no
way
of
s
the
D
button
altering
your
extensions
using
the
workbench
and
to
access
that
we
have
introduced
this
debugging
query
parameters.
So
essentially,
what
you
can
do
is
debug
against
live
SharePoint
site
with
your
content
and
loading,
essentially
the
code
localhost,
but
you
need
to
apply
a
nofollow
on
the
specific
query
parameters
and
put
them
on
a
URL
and
that
will
then
essentially
tell
sharepoint
okay.
B
It
is
fine
that
for
loading
this
manifest
files
from
a
local
host
and
loads,
this
particular
client
component
ID
and
then
it's
being
executed
and
applied
on
the
on
the
page
and
I'll
show
that
one
in
practice
in
the
demo.
So
it's
a
slightly
different
experience
as
with
client
side
with
pods
we're
looking
into
having
a
extension
support
in
the
workbench
as
well.
Now
that
is
in
the
roadmap.
But
because
do
you
thing
about
this
approach?
Is
that
you're
able
the
debugging
and
testing
on
top
of
your
existing
data
and
that's
really
a
creasing?
B
B
The
internal
it's
asking
good
sleeper
contains
before
GA
will
be
get
frequent,
debugging,
both
online
and
local,
for
the
I'm,
not
sure
if
we
can
get
it
by
GA.
But
to
be
honest,
even
though
we
would
have
deep
for
extensions,
we
will
keep
the
debugging
URLs
debugging
query
parameters.
They
are
able
to
just
against
the
live
data,
because
that
makes
a
lot
of
sense,
you're
able
to
run
it
properly.
B
B
And
this
is
really
killing
usefulness
of
the
work
plants
as
a
whole.
That's
where
we
disappointed,
if
not
in
g8,
all
with
you
there
AC,
so
most
likely
will
get
it
by
the
GA.
It
really
depends
when
the
TA
happens
and
that
really
is
dependent
on
what
kind
of
information
and
input
we're
getting
for
you
guys
so
we'll
see
it
should
be
there,
but
there's
quite
a
lot
of
butter
of
items
with
map,
although
as
if
that
has
been,
that
is
a
high-priority
thing,
but
there's
a
lot
of
high
priority
other
things
as
well.
B
That's
always
the
challenge.
Good
I
think
my
following
is
find
this.
Actually,
the
demos
right,
no,
it
isn't
deployment
of
an
extension
so
quickly
to
covering
this
one
as
well.
So
we
can
do
the
deep
arcing
against
the
live
data,
which
is
great
because
if
you
would
be
doing
debugging
against
workmanship,
wouldn't
actually
have
you're
unable
to
configure
let's
say
lists
and
fields
and
all
stats,
and
you
can't
really
have
the
exact
same
experience
as
with
the
live
data
about.
B
So
you
can
do
that.
Then
you
need
to
decide
over
so
where
the
customization
will
be
hosted.
That's
CDN
technically
could
build
the
document
Piper
in
SharePoint,
which
is
not
a
CDN,
but
you
can
enable
that
to
PC
in
so
there's
multiple
options,
updating
target
hosting
URL
in
the
solution,
which
is
updating
the
right
manifest.json
file
in
the
config
folder,
and
then
you
essentially
do
package
solution
and
you
copy
your
assets
to
the
CDN
and
at
that
point
we'll
add
the
solution
packets
to
the
amp
catalog.
B
But
for
the
time
being,
the
step
number
five
has
to
happen
to
be
able
to
get
the
extension
work
in
the
sign
and
step
number
six
has
to
happen
as
well,
because
step
number
six
is
essentially
making
sure
that
you
are
associating
your
extension
to
the
right
scope
and
its
right
object.
People
now
in
our
tutorials
we're
using
feature
framework
inside
of
the
SharePoint
framework.
To
do
that,
you
can
absolutely
do
exactly
the
same
using
Caesar
or
using
the
REST.
B
It's
simply
because
for
there's,
no
support
for
powershell
as
an
example
in
a
non
Windows
machines
or
there
might
be-
or
there
will
be
in
the
future,
but
there's
no
BMP
power
shells
which
would
be
super
useful
to
associate
client-side
component
ID
to
do
some
actions
or
to
deal
but
I'll
show
you
that
one
in
practice,
by
showing
the
feature
xml's
in
the
solutions
in
the
tutorial
solutions
in
the
following
slide
or
in
the
demo
I
think
I
I
didn't
have
anything
else
here.
Go
because
we
need
to
have
some
time
for
entry
as
well.
B
B
Cool
somebody
needs
to
tell
me
when
the
sunrise,
eyelid,
X
and
if
you've
got
it,
then
everybody
else
cut
it
as
well.
So
we've
shown
this
one
before
in
the
special
interest
group
course.
So,
obviously,
if
you
have
the
latest
version
of
the
human
template,
there
is
a
new
selection
with
the
stay
extensions.
If
you
choose
that,
it's
going
to
ask
you:
do
you
want
to
create
an
application,
customers,
ideal
customers,
or
at
least
your
common
sense?
B
And
after
that,
it's
going
to
then
request
additional
details
and
I
just
because
we
all
know
that
scaffolding
takes
a
while.
So
there's
no
point
for
doing
that.
What
I'm
using
is
our
tutorial
samples
tutorial
samples
are
the
ones
which
you
will
end
up
having
if
you
follow
up
on
the
tutorials
which
are
released
in
our
depth
of
circumcircle
occasion.
These
are
also
available
in
github,
so
sharepoint
as
a
data
effects,
and
that
was
not
right.
B
B
Extensions
there
we
go
so
in
key
taps,
SharePoint
SPD,
FFX
extensions.
We
already
have
a
one
community
contribution
here
is
very
well
from
Alex
from
yesterday
showing
react
based
built
a
slider
presentation.
But
if
you
go
to
the
tutorials
folder,
you
can
actually
download
or
have
a
look
on
the
outcome
of
the
tutorials.
So
if
you
for
some
reason,
you
can
make
the
tutorials
work
or
there's
some
issues
on
the
on
the
guidance.
B
You
can
always
pull
this
down,
and
this
has
been
tested
in
multiple
machines
and
then
compare
your
solution
against
these
and
then
figure
out.
What's
wrong,
maybe
dimension.
Technically,
all
of
these
three
could
have
been
in
a
one
solution
as
well,
so
you
can
absolutely
have
a
one
complex
as
basic
solution,
including
multiple
different
component
types,
so
absolutely
doable,
and
that's
really
the
intention
as
well.
B
Now,
let's
come
in
here
and
let
me
start
the
studio
code,
which
apparently
already
had
an
opening
here
cool,
so
the
business
studio
code
solution
for
the
extensions
is
exactly
the
same.
So
the
shell
of
solution
is
exactly
the
same
and
you
can
see
the
files
which
are
familiar
if
you've
done
a
client-side
back
part
development,
so
packet
solution,
and
all
of
that
all
of
these
are
exactly
working
exactly
like
client-side
solution.
B
What
we
essentially
have
a
small
difference,
the
classes
and
implementations
of
the
actual
extensions
and
in
here,
because
this
is
an
application
extension
we're
inheriting
that
from
a
pair
base
class
customizer-
and
this
is
the
outcome
of
the
tutorial
where
we
also
use
the
placeholders
from
a
page.
So
essentially,
we
are
outputting
outputting.
B
Our
HTML
directly
from
our
own
render
the
placeholder
with
scald
space
hitter
Oh.
So
there
are
few
placement
right
now
in
the
dev
preview.
There's
two
placeholders
with
the
space
hitter
and
page
scooter
and
in
future
there
will
be
more
placeholders.
So
they
look
up
where
you
can
actually
attach
your
things.
So.
B
Now
in
here
the
implementation
style,
everything
else
is
pretty
much
almost
like
within
the
client-side
web
part,
so
you
can
say
that
we're
just
injecting
injecting
maybe
wrong.
Word
we're
adding
HTML
in
the
inner
HTML
out
which
we're
doing
in
this.
What
we're
doing
for
this
implementation-
and
the
same
applies
for
the
footer
now
when
the
implementation
is
done,
then
we
get
the
depth.
The
implementations
part
is
obviously
dependent
on
what
we
wanna
do
now
so,
but
how
do
we
actually
do
debugging?
So
let
me
show
that
one
in
practice
we
need
few
things.
B
We
need
to
have
the
unique
ID
off
top
of
the
extension
now
so
when
we
are
hooking
up
to
debugging
using
the
debugging
query
parameters,
we
are
actually
associating
to
the
right
application
or
exile,
and
we
need
to
have
wizards
to
the
ass
or
a
sharepoint
online
tenant,
which
is
the
developer
tenant
right
now
in
the
future,
obviously
will
be
supported
in
other
tenants
as
well.
I
will
use
this
document
library,
as
my
hosting
point
really
doesn't
matter
where
you
want
to
do
the
debugging
or
well.
B
Obviously,
if
you
are
writing
a
field
customizer,
then
you
have
to
use
the
list.
If,
if
you're
writing
an
application
customizer,
you
can
use
any
other
locations
as
well.
Now
this
is
a
small
as
tricky
thing,
so
in
our
tutorials
and
in
the
sample.
Documentation
will
actually
explaining
this
one
as
well.
We're
writing
additional
documentation
where
all
of
this
is
pain
clarifying,
but
basically
what
we
need
to
do,
because
we
want
to
test
application
customizer.
B
We
need
to
use
specific
debugging,
X,
query
parameter
and
in
here,
and
that's
essentially
means
that
a
SharePoint
load
pfx.
It
is
not
on
the
page,
hey
SharePoint
load
to
manifest
flume
localhost.
Do
not
so
that's
fine
load
them
from
a
local
host,
not
from
a
central
location,
a
custom
action.
This
is
a
custom
action
implementation,
and
this
is
the
ID
unique
ID
of
my
customization.
B
What
you're
passing
passing
in
now,
let
me
update
that
I
took
notice
that
that's
not
actually
the
property
set,
what
I'm
going
to
use.
So
let
me
get
that
one
right
for
my
particular
extension.
If
you're
wondering
on
the
URLs
it
is
like
mentioned.
This
is
mentioned
the
tutorials
and
also
in
the
tutorial
samples
were
also
pinpointing.
What's
the
query
parameters
and
how
that
should
be
working
within
your
channel
now,
let's
get
back
on
on
the
page
and
on
the
notepad
and
I'm
going
to
copy
that
query
parameter.
B
There's
my
document
library,
adding
that
query
parameter
tariff
and
yes
get
slightly
messy,
but
a
clicking
enter.
What's
going
to
happen
is
that
the
SharePoint
realizes
the
tail
you
want
to
load
that
from
on-premises
into
the
book
strings.
Now,
in
this
case,
I
just
realized
that
I'm
not
actually
running
my
local
first.
So
obviously
it's
going
to
say
well,
I
can't
load.
There
was
nothing
hosted
there.
B
So
let's
say
dismiss:
let's
fix
the
situation
get
here
and
do
cult
serve
no
browser
because
there's
no
point
of
starting
the
local
workbench,
because
there's
no
value
in
a
local
girl.
Friends
in
this
scenario,
so
that's
why
there's
no
Krauser
switch.
What
I'm
using
cool,
localhost
warning
I
can
go
back
into
your
rail
refresh,
do
an
enter
there.
It's
going
to
again
request
or
ask
me:
do
I
want
to
load
those
deeper
scripts,
and
the
answer
is
in
this
case:
yes,
and
we
can
see
the
page
to
behave
differently
and
no
it
didn't
wonder.
B
Request
is
getting
in
its
my
interesting
well,
let's
actually
do
some
debugging,
then
we
have
plenty
of
time
right.
Custom
actions,
URL,
clear
parameters
is
improperly
formatted:
okay,
cool.
Let's
fix
that.
So
let
me
actually
get
there's
pretty
okay
exception
and
descriptions
in
the
console.
So
let's
close
that
one,
let's
get
back
in
our
here-
let's
actually
take
that
one
which
is
now
not
just
copied
by
me.
So
I
could
have
mistake,
probably
under
on
the
formatting
and
let's
actually
get
rid
of
that
and
paste
that
one
in
and
load
debug
scripts.
B
Then
we
can
actually
gets
it
there
on
the
page
injected
apply
our
customization,
which
is
running
from
on
premises.
That
was
a
good
debugging
exercise
as
well.
So
you
can
see
that
the
information
is
actually
quite
nicely
within
the
console
window,
but
in
this
case,
so
we
were
not
doing
anything
else
than
outputting
outputting,
header
and
footer
on
the
page
and
then
I
can
obviously
the
the
proper
parameters
here.
B
Properties
which
have
path
to
the
station
I
can
modify
them
sick,
ball
and
demo,
and
we
can
say
that
the
food
riah
will
be
chains
when
I
load.
The
scripts-
and
it
is
now
saying
sick
call
demo,
so
I
can
program
exercise.
The
implementation
based
on
the
again
on
the
business
requirements
may
be
a
small
point
kind
of
a
clarifying
that
one.
B
So
let
me
come
back
on
the
application
customizer
and
clarify
that
one
here
as
well,
so
the
current
implementation
is
that
we're
looking
into
placeholder
on
the
page,
just
my
looking
in
the
potato
placeholder
and
then
we
are
looking
into
have
a
property
called
header
and
so,
in
my
case,
I
actually
provided
the
property
called
header
in
the
query
parameters.
So
this
one
actually
will
have
value
in
all
of
this
d.
Civilizations.
The
realization
will
happen
automatically.
B
So
you
don't
have
to
worry
about
that
as
long
as
the
string
matches
the
property
name,
which
is
being
used
in
property
in
the
query
parameters,
good,
that's
pretty
much
what
I
was
planning
to
actually
show,
because
I
don't
want
to
eat
up
too
much
time
from
entry
and
also
making
sure
that
they
have
time
for
Q&A.
In
the
end,
we
will
release
a
webcast
which
will
talk
about
the
debugging
and
deployment
and
everything
else
on
Monday.
So
that's
coming
out
live
on
Monday
as
well.
B
Now
what
are
the
any
plans
for
additional,
well-known
divs
on
the
page,
so
we're
looking
into
having
absolutely
additional
placeholders
right
now,
technically,
both
age?
So
let
me
show
you
that
one
in
practice,
you
can
actually
see
that
the
available
placeholders
are
page
header
and
page
footer,
even
in
our
console
application
writing
looking
into
having
additional
place
dates,
placeholders
in
a
page
for
navigation
for
additional
controls
and
all
of
that
and
that's
really
good
feedback
as
well.
B
So
we
can
actually
understand
the
business
requirement
and
what
kind
of
things
people
wanted
to
and
get
that
input
into
engineering
taking
french-kiss
there.
So
it's
matter
for
us
for
exposing
you
guys
additional
security
placeholders,
which
will
be
then
taking
which
will
be
then
have
to
be
implemented
into
listviews
and
libraries
and
pages,
and
all
of
that
one
thing,
maybe
to
notice
I'm
going
to
take
two
minutes
on
the
on
the
debugging
experience.
So
if
I
do
the
same,
let
me
actually
steal
that
query
parameter
because
that's
fine.
B
If
I
go
to
my
home
page
I've
more,
oh
there
we
go.
Let
me
do
the
query
parameter
in
the
home
page.
Well,
you
can
see
that
the
loading
the
page
and
into
pages
current
implementation
of
the
modern
pages
and
to
be
honest,
personally
I,
don't
know
why,
looking
into
this
one
as
well,
we
do
not
have
a
footer
at
this
one.
B
Answering
Asus
comments
keep
up
issueless.
Yes,
please
questions
get
a
facialist,
especially
now
that
we
are
in
dev
preview,
github
issue
list
if
it's
something
related
on
client-side
web
parts
and
it's
a
new
feature
such
as
and
then
user
voice,
but
right
now
around
the
extensions.
Please
add
those
things
to
the
github
issue
list
and
let
me
actually
share
that
location
as
well.
B
So
if
there
are
missing
things,
missing,
values
or
scenarios
which
are
not
missing
or
documentation
is
not
good
enough
or
whatever.
Please
use
this
issue
list.
All
of
these
issues
are
getting
automatic
listings
to
our
resource
to
the
online
and
we
can
assign
them
internally
to
engineering
on
top
of
the
things.
So
please
let
us
let
us
know
you
don't
like
something
tell
us
we'll
try
to
fix
it
if
it's
possible,
so
please
be
active
and
share.
B
What's
now
the
one
thing
before
we
go
to
the
Aunt
Rose
demo,
this
is
slightly
weird
I
would
say,
but
within
the
site
contents
you
can
absolutely
to
similar
kind
of
testing,
as
with
the
other
pages
in
a
second
I'm,
just
going
to
copy
every
parameter
in
the
site
contents
and
to
stop
all
checking
that
the
query
parameter
was
properly
done.
Yes,
it
is
now
if
I
load
this
and
I
load
my
debug
scripts.
B
It
actually
does
work
right
now
they
were
slightly
different
currently
because
we're
in
a
deaf
preview
and
we'll
fix
this
in
the
in
the
future,
in
the
site,
contents
page
and
do
reasons
or
another-
and
personally
not
aware.
Yes,
why
investigating
on
this
one
I
do
not
own
this
page
and
we
are
HTTP
address,
is
getting
encoded,
so
don't
get
hope
and
don't
get
fooled
by
this
I
want
to
get
this
one
recorded.
B
So
you
are
aware
of
this
and
you'll
avoid
the
situation
and
you
don't
bang
your
head
against
the
wall
like
this
one,
so
the
debug
manifest
file
HTTP
address
HTTP
address
is
getting
inserted.
The
problem
of
this
that
right
now
with
the
current
implementation.
If
I
refresh
this
page
with
those
values,
things
do
not
work,
it's
going
to
actually
fail,
do
it
in
coding.
So
this
is
only
in
the
site
contents
page,
if
you're
doing
testing
in
the
modern
pages
or
in
the
lists
and
libraries.
This
doesn't
happen.
So
we
need
to.
B
We
need
to
make
sure,
and
that
will
fix
this
in
the
site
content
Paige
sooner
or
later
it
requires
most
likely
of
server-side
updating,
but
that's
a
kind
of
a
hint,
a
tip
when
you're
doing
two
on
their
extensions.
So
don't
get
fooled
by
this
business
way
to
to
fix
that
is
actually
do
testing
in
the
document
library
or
in
the
list.
These
do
not
have
this
in
white
coloration,
so
putting
that
same
query
parameter
here.
No
encoding
and
everything
is
fine,
took
awhile
to
figure
out,
what's
actually
happening
here.
B
Good
I
think
that's
it
for
the
extensions
and
we'll
continue
a
number
on
the
releasing
new
stuff
on
their
extensions
videos
with
documentation
scratch
early.
Let
us
know
if
something
is
missing
and
let
us
know
you
might
be
thinking
that
it
might
be.
It
should
be
obvious
that
they're
telling
x
and
y
and
z
around
the
destinations
go
to
the
issue
list
at
an
entry.
Trust
me
we're
watching
that
issue
is
pretty
closely
and
I'll
carry
the
sign,
we'll
work
on
the
documentation
as
well.
B
C
So
I'm
going
to
show
a
couple
of
slides
and
then
six
different
examples
with
the
library
so
pallet
there.
My
name
is
Andrew
Celtic
off
I'm,
a
SharePoint
developer
and
council
comes
at
our
assistance
and
I'm
going
to
talk
about
how
to
master,
pin
PJs
core
library
in
no
GS
before
I
kick
off.
Let
me
say
a
few
words
about
myself
on
the
first
place:
I'm
a
SharePoint
guy
I've,
been
in
SharePoint
projects
for
around
seven
years,
developing
and
implementing
solutions
for
medium
and
large
businesses,
also
I'm
a
person
8no
Dias
and
JavaScript
developer.
C
The
last
year
was
so
saturated
with
open
source
projects
on
github.
Some
of
them
found
active
users
who
already
reported
positive
feedback
from
time
to
time.
I'm
logging
with
the
posts
about
SharePoint
and
notice.
We
will
in
some
use
cases
which
I
experienced
and
you
can
reach
me
in
Twitter
LinkedIn
Peter,
but
let's
get
started
with
today's
topic.
C
First
off,
let
me
mention
that
no
GS
advised
huge
place
in
modern
development
and
it
really
deserves
attention.
It's
a
holy
word
topic
in
some
way,
so
I'm
not
going
declaring
JavaScript
better
than
any
other
technologies
which
can
actually
link
together
in
peace
and
complete
each
other,
but
applications
in
odious
are
capable
for
awesome
things,
especially
when
one
should
deal
with
the
FBI's
micro
services,
cross-platform
applications
or
and
build
pipelines.
C
Automation,
node.js
infrastructure
provides
wonderful
feature
than
working
with
the
rest
of
the
eyes,
especially
when
we
come
to
understanding
that
the
same
codebase
can
be
used
in
browser
and
on
the
server
and
in
the
in
context
of
this
presentation.
By
running
on
the
server
I
mean
JavaScript
applications
outside
the
browser,
so
it
can
be
a
natural
server
or
a
client
machine
as
well.
C
Applications
written
in
note
es
can
be
integrated
with
SharePoint
and
consumed
at
the
eyes,
including
even
a
legacy
you
like
SOP
web
services,
to
make
an
odious
application
capable
talking
to
an
AI.
It
should
be
authenticated
and
I'm
not
going
to
cover
a
vindication
topic
here.
It
is
a
huge
one.
I
just
want
to
say
that
for
most
syndication
promotes
authentication
routines
can
be
simplified,
simplified
using
AWS
libraries,
in
my
case
I,
would
recommend
to
notice
views
by
Sergei
Sergei,
which
supports
a
variety
of
different
authentication
strategies.
C
One
day
up,
there
is
a
tentacle
danger
point:
it
owns
us
headers,
it
should
be
merged
in
null
requests
to
the
server
and
after
these
applications
capable
sending
a
get
or
post
request
to
a
Dyson
box.
Let
me
switch
from
no
Diaz
to
another
zero,
the
topic
impedance
core
library
in
pintia
product
family.
There
is
a
number
of
different
technologies,
and
today
we're
talking
about
JavaScript
library,
wrap
around
SharePoint,
REST
API,
and
let
me
call
a
pimp
adjust
or
by
being
pressured
for
the
rest
of
this
demo
towards
about
PNP.
C
It
masters
rest
at
the
I
capabilities.
It
provides
the
fluent
syntax,
it
is
ready.
Anytime,
script
inspires
using
promises
and
null
cog,
callbacks
and
highly
recommended
for
front-end
projects
with
SharePoint
I
just
started
with
the
pimpy
for
around
a
year
ago,
in
September
2016
I
included
pimpy
as
a
dependency
to
the
first
production
project
within
peer.
Since
then,
more
and
more
front-end
applications
which
I
created
used
MV
after
next
half
a
year,
I
forgot
how
to
write
code
in
JSON
and
how
to
represent
I
just
kidding
but
a
year.
C
A
number
of
cases
when
B&T
was
referred
over
at
alternatives
was
growing
and
with
time
I
got
an
idea
to
reuse
some
code
for
no
Deus
environment.
It
was
a
requirement
for
development
of
flying.
This
top
line
for
some
complex
you
are
and
and
that
application
should
have
repeated
UI
layer
and
have
an
ability
to
receive
updates
without
physical
access
to
sharepoint
server
and
the
corporate
network,
and
it
can
imagine
how
many
reports
can
be
spent
on
such
a
task,
and
actually
it
had
been
done
less
than
a
week.
C
Electron
application
almost
completely
reused,
UI
layer,
node.js,
server,
side
code
was
in
sync
job
and
scheduled
tasks,
and
you
might
guess
what
was
in
charge
for
communication
level.
Yes,
it
was
the
first
implementation
of
in
PG,
asked
or
outside
browser
my
my
first
implementation
of
the
library.
After
this
there
were
other
tasks
with
a
pain
PDA
and
no
GS
and
some
more
on
the
horizon.
And
do
you
know
what
I
hate
to
repeat
myself
so
for
the
reusability
purposes,
I
created
a
drop-in
library.
C
The
library
is
named
as
peepin
keynote
for
pimpy
notes.
It
is
an
open
source
available
on
he
caught
up
and
published
to
NPM
pink
note
has
noticed
bios
integrated,
so
it
covers
all
the
syndications
in
there
is
the
library
provides
pindy
node
has
implemented
SharePoint,
aware
of
fetch
client
and,
as
a
result,
a
developer
can
add
dependency
for
pimpy
note
and
a
scorer
library
to
the
project
and
in
five
lines
away
literally
start
using
being
be
and
ng
score
in
note,
oh
dammit
I'm.
So
let's
get
our
hands
dirty
with
some
code.
C
C
C
C
C
C
C
Here
we
are:
oh,
we
got,
pin
PJs,
who
are
working
node
and
we
received
content,
types,
names
and
descriptions
and,
on
the
second
run
the
library.
Well,
it
won't
ask
for
any
credentials
any
parameters,
because
it
only
already
knows
that
and
the
parameters
are
saved
by
default
to
the
config
private
JSON
file.
And
here
we
are
what
we
provided
during
the
wizard
password
stores
in
cash
form,
which
can
be
decrypted
only
on
the
machine
there.
It
was
created
and
if
we
remove
something
that
file,
let's
say,
remove
the
passwords
and
for
user
credentials.
C
C
C
C
C
We
see
the
integers
course
top
here:
each
implementation
of
custom,
page
client
to
use
so
we
return
edge
client
factory
as
a
npm
node
with
parameters.
Let's
run
the
script,
awesome
yeah
and
after
they
set
up,
we
could
also
deal
with
the
pin
pts
core
code,
so
it
all
sorts
and
we
could
use
get
web
by
default.
One
or
two
use
explicit
creation.
All
new
web
based
on
urls,
okay,
so.
C
C
C
Let's
go
back
to
the
main
file.
This
example
two
lies:
modern
JavaScript
features
like
a
sink
a
weight
and
also
real
possibility
of
configuring
being
visits
up
with
additional
headers.
So
in
this
example,
we
use
light
out
data
mode
to
receive
only
no
no
metadata
mode,
so
it
can
make
such
application
faster,
especially
when
it
tries
to
receive
a
lot
of
different
data
from
the
server
okay.
C
Well.
But
the
code
here
actually
is
something
which
consumes
BMP
pretty
standard
for
any
integer
score
application,
and
you
could
even
reuse
the
same
one
which
I
used
on
the
client
side
and
after
such
setup
it
will
work
on
the
server
okay
will
be
on
the
server
with
a
pimping.
Note
is
definitely
testable.
C
C
That's
to
the
code.
So
before
running
a
testing
for
different
environments
or
using
different
settings,
we
need
to
reconfigure
pimpy
fetch
client
to
use
a
new
instance
of
pimping
note.
So
in
this
case,
in
this
logo
we
receive
different
authentications
different
site.
Urls
and
after
test
go,
go
through
different
reading
lines,
and
here
they
talk
into
SharePoint
2013,
another
form
with
four-point
2016
and
online
okay.
C
C
We
use
environment
variables
and
skewers
dreams
environment
where
mates
can
be
easily
reused
by
pro
tournament
and
the
name
of
the
parameter
and
secure
strings
are
passed
as
arguments
to
the
script.
So
when
we
define
in
a
task
with
pimpy,
we
could
set
up
it
to
execute
nodejs
and
passing
this
parameter
as
far
as
we
didn't
want
to
show
it
in
its
original
form.
Oh
hey!
C
Maybe
it's
time
so
we
are
almost
there:
okay,
okay,
so
yeah.
The
idea
of
the
script
was
to
bring
this
a
web
title
here,
so
nothing
connected
with
the
continuous
integration,
but
actually
it
shows
the
possibilities:
oh,
how
to
extend
build
process
on
interface,
to
use
some
robust
data,
manipulation,
use
of
being
PJs
for
okay,
and
the
last
example
is
deploying
a
products
you'll
deploy
about
using
proof
of
proof
of
using
being
peak
or
Jia's
in
a
asia
web
job.
C
C
C
C
C
Out
here,
all's
there,
okay,
so
it
is
completed
and
let's
refresh
the
pages-
and
here
we
are,
we
have
I
can
be
I
can
see
and
please
be,
and
the
same
is
here
in
site
a
and
all
of
these
has
been
done
with
you
so
for
being
Peters
core.
So
the
script
is
pretty
simple:
actually
pretty
small,
it
reads:
data
from
the
lists:
it
tries
data
to
the
lists
with
the
use
of
batches
and
during
the
initiation
it
passes
different
modes
for
OData.
C
C
Here
we
are
and
done
with
the
damage
which,
by
the
way,
are
available
on
a
github
there's
a
link
to
this
in
these
samples,
and
there
are
some
readme
files
and
feel
free
to
ask
any
questions
there
as
an
issue.
I
hope
that
that
was
interesting.
That
also
I
hope
that
some
of
you
will
start
using
BB
just
score
on
the
server
and
that
it
will
be
a
straightforward
process
now
with
notes
library.
Thank
you
so
much
for
inviting
me
to
the
talk,
and
if
there
are
any
questions,
I'll
try
to
answer
them.
A
You
know
bring
to
the
table
using
these
technologies
on
the
server,
so
we've
got
a
little
long,
we'll
switch
quickly
back
to
the
slides,
but
that
was
too
great
of
a
demo
to
really
try
and
cut
off
at
all
so
really
outstanding,
stuff
Andrew
thanks
for
doing
that,
vasa.
Thank
you
as
well,
of
course,
for
the
great
SharePoint
framework
extension
demo,
as
always
invite
folks,
if
you
have
a
demo
that
you
would
like
to
do
on
the
call
please
just
let
us
know
get
in
touch,
we
would
love
to
have
you.