►
From YouTube: SPFx JavaScript SIG 27th of April, 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
in
is
April
27th
2017
welcome
everybody
to
this
week's
call
got
some
great
demos
this
week,
some
exciting
stuff
to
talk
about
some
need,
updates
and
we'll
jump
right
into
that,
but
real,
quick
or
review
for
folks.
That
might
be
new
to
the
call
or
listening
to
these
recordings
for
the
first
time.
A
So
we
are
part
of
the
larger
SharePoint
patterns
and
practices
program
and,
as
the
program
grew,
we
saw
the
need
to
sort
of
have
a
more
focused
channel
for
certain
technologies
and
one
of
those
was
client-side
development
and
with
the
coming
up
of
the
SharePoint
framework
before
it
was
released.
We
needed
a
way
to
start
to
talk
to
folks
about
client-side
development
and
start
to
sort
of
highlight
that
to
a
lot
of
SharePoint
developers,
who
might
have
been
more
managed
code
focused
in
the
past,
and
so
we
started
the
special
interest
group
for
client-side
development.
A
There's
now
one
for
PowerShell,
as
well
as
the
core
component,
so
attend
as
many
as
you'd
like.
Thank
you
for
attending
this
call
today,
but
you're
certainly
welcome
to
attend,
as
many
of
the
special
interest
group
calls
as
you
want,
as
well
as
the
monthly
call,
but
we
wanted
a
more
focused
forum,
and
so
what
we
do
here
on
these
calls
is
talk
a
lot
about
SharePoint
framework.
What's
new,
with
the
SharePoint
framework
updates
to
the
framework
plan,
things
and
you
know
general
client-side
development
patterns
and
just
sort
of
client-side
development
stuff.
A
If
you're,
if
you're
doing
provider
hosted
or
SharePoint
hosted
add-in
development
or
if
you're
doing
manage
code
like
classic
WSP
deployed
right,
you
might
still
be
on
premises.
For
example,
all
that
is
now
covered
at
dev
dot
office,
comm
/
SharePoint,
and
encourage
you
to
check
that
out
for
all
your
development
needs
so
moving
on.
What's
our
agenda
specifically
for
this
week
we
got
quick
updates
on
the
JavaScript
core
component,
some
great
updates
or
on
the
SharePoint
framework,
and
we've
got
two
really
cool
demos.
A
The
first
one
base
is
going
to
do
a
demo
on
a
Visual,
Studio,
SharePoint
framework
extension.
This
is
built
on
work
from
the
community,
so
really
cool
to
see
it's
bringing
sort
of
a
more
GUI
based
experience
to
Visual
Studio,
so
you're
used
to
maybe
like
file
new
project
and
you
might
create
a
new
provider,
hosted
add-in
project.
This
is
working
to
bring
a
similar
experience
for
SharePoint
frameworks.
A
You
would
do
file
new
share
pod
framework
project
and
you
would
configure
it
there,
but
base
is
going
to
show
that
off
very
cool
and
then
Sebastian's
got
a
really
cool
demo
around
SharePoint
framework
with
riot
j/s.
So
righteous
is
another
framework
you
could
build
in
and
it's
one
I
personally
don't
know
a
ton
about
so
I'm
excited
to
see
when
he's
come
up
with
there.
So
that
should
be
really
neat
at
end
as
well.
A
Hopefully
have
time
at
the
end,
for
an
open
discussion
on
topics
then
interest
you
guys
quickly
how
to
opportunities
to
participate
in
the
special
interest
group,
a
demo
of
SharePoint
framework
report
or
anything
related
to
client-side
development,
so
keep
encouraging
that
I
want
to
provide
folks
out
there
in
the
community
a
great
platform.
So,
if
you're
doing
cool
work,
please
do
a
you
know
demo,
these
things
out
to
us.
Let
us
know
we'd
love
to
get
you
on
here,
give
you
a
forum,
so
that
could
be
a
SharePoint
framework
web
part.
A
That
could
be
something
around
the
the
JavaScript
core
library
that
could
be
just
something:
client-side,
SharePoint
development
related
we've
had
a
couple
great
demos
on
just
using
jail
in
canned
things
like
that.
The
last
couple
weeks
contribute
on
github
get
involved
and
then
lastly,
provide
feedback.
Like
I
said
everything
we
do
is
really
driven
by
feedback
from
you
guys
in
the
community.
So
we
really
want
to
hear
from
you
both
positive.
A
We
love
to
hear
positive
feedback,
but
also,
if
you've
got
things
that
we
could
be
doing
a
little
bit
better
or
things
that
would
help
you
out
in
your
job.
Please
just
let
us
know
so
a
quick
update
here
on
the
JavaScript
core
library
we
released
2.4,
so
that
was
released
out-of-band,
but
that
was
to
fix
a
blocking
bug
with
SharePoint
framework.
So
obviously
that's
important
enough.
We
wanted
to
get
a
release
out
for
that.
So
I've
been
talking
in
the
past
about
the
next
release
will
be
204
well
now.
A
The
next
release
will
just
be
205,
no
big
change
there,
but
did
want
to
highlight
that.
So,
if
you
are
having
trouble
in
SharePoint
framework,
please
do
pick
up.
The
latest
release
should
be
all
fixed
there
and
do
want
to
apologize
I'm,
honestly,
not
sure
how
that
bug
got
out
because
I
swear
I
tested
it,
but
thank
you
to
the
folks
in
the
community
to
found
that
and
reported
it,
and
actually
that
was
fixed
by
someone
in
the
community.
So
thank
you
for
that
and
we
got
that
release
out.
So
please
do
check
that
out.
A
Feedback
continues
to
drive
updates,
like
I
said.
If
you
follow
the
issues
list
at
all,
we
get
a
lot
of.
The
new
features
are
suggested
by
folks
in
the
community.
So
if
you
have
something
you'd
like
to
see
No
and
we'll
see,
if
we
can
work
it
in
I
can't
guarantee
it
will
get
in
right
away,
but
we'll
do
our
best
just
a
reminder.
We
are
doing
beta
releases
now.
So
that's
a
great
way
to
see
kind
of
the
stuff.
A
A
I'll,
say
it'll
be
available
in
beta,
whatever,
whatever
number
right
be
part
of
a
great
conversation
on
graph
thanks,
everybody
is
contributed
to
that
thread,
for
the
thoughts
definitely
welcome
more
thoughts
from
folks
out
there
in
the
community
so
again
taking
that
feedback
from
everybody
I
think
we've
got
a
great
base
like
I,
said
all
more
thoughts.
More
ideas
are
absolutely
welcome
and
I
think
it's
it's
starting
to
help
at
least
crystallize.
My
thinking
on
it
so
I
think
that's
great
and
let's
continue
moving
forward.
A
Like
I
said,
more
voices
are
welcome
and
then
we
will
take
a
look
at
maybe
how
to
move
forward
on
that
service,
trying
to
start
to
make
some
long-range
planning
around
our
graph
capabilities.
Just
reminder:
please
check
out
the
wiki
and
the
developer
guide.
I
keep
getting
asked.
You
know
why
don't
we
have
any
documentation
and
I'll
be
the
first
to
say
our
documentation
is
not
perfect,
but
we
do
have
documentation,
so
please
check
it
out
and
if
you
have
a
specific
question
that
isn't
covered,
let
us
know
what
I've
been
handling.
A
That
is
taking
the
you
know
if
somebody
asks
a
question
and
we
don't
have
a
wiki
article
about
it.
I'll
write
up
a
wiki
article
and
post
it
there
as
the
answer
to
that
question
that
why
other
folks
can
get
the
answer
easily
and
of
course,
contributions
are
welcome
in
the
wiki
as
well.
So
we
did
in
the
beta
there's
some
search
improvements.
The
latest
beta,
if
you
want
to
check
that
out,
so
some
search
improvements,
there's
some
support
for
paging
and
as
well
as
a
lot
more
interfaces
to
help
type.
A
The
search
results
that
are
coming
back,
give
you
a
little
bit
more
information
about
what's
actually
there
and
we
did
actually
also
as
part
of
to
dotto,
for
it
snuck
out
as
part
of
that
release,
there
was
a
fix
for
there's
a
batch
ordering,
so
the
execute
promise
was
resolving
before
the
sub
promises,
which
is
obviously
the
wrong
order,
not
what
we
intended.
So
that's
actually
fixed
in
204
and
as
part
of
that,
we've
been
adding
tests
to
cover
these
things.
A
So
if
we
do
break
it
in
the
future,
we'll
catch
it
with
tests
so
trying
to
try
to
do
more
of
that
trying
to
be
better
about
writing
tests
and,
of
course,
help
writing
tests
again
is
another
area
you
can
help,
contribute
always
welcome
there.
Our
test
coverage,
like
our
documentation
coverage,
not
at
100%
but
working
to
make
it
better
as
we
go.
We
did
also
update
the
generic
react,
SharePoint
framework
sample
to
the
latest
SharePoint
framework
release
code.
A
So
there
is
some
reports
that
it
did
not
work
with
the
SPP
and
PJs
library,
as
well
as
a
couple
others,
and
so
that's
fixed
now.
So
if
you
pull
that
sample
back
down,
you
should
be
all
set
to
use
it
with
the
SPP
and
PJs
or
many
other
libraries
out
there.
So
that
was
just
a
quick
update
to
the
latest
stuff
and
then
just
reminder.
Please
do
report
issues
to
the
issues
list.
On
the
last
few
weeks,
we've
had
a
couple
people
who've
posted
stuff
in
communities
and
places
like
that
and
I
apologize.
A
But
it's
just
it's
a
lot
of
streams
to
try
and
track
so
stuff
gets
missed.
But
if
you
get
it
an
issues
list,
we
definitely
won't
miss.
It
we'll
definitely
see
it.
So
apologies
to
the
folks
that
responses
were
a
little
bit
delayed
getting
there,
but
you
know
so
issues
list.
Definitely,
if
you
have
an
issue,
please
drop
it
in
there
and
also
reminder.
Please
do
provide
us
enough
details
to
understand
the
issue.
A
Things
like
item
added
failed
is
really
hard
for
us
to
help
you
so
two
links
down
there
at
the
bottom
again
to
the
community
and
again
that's
the
git
er
Channel
get
her
page
for
the
PNP
j/s
core
and
do
check
those
out
do
be
part
of
the
conversation
love
to
hear
from
folks
love
to
get
the
feedback.
If
you
have
time,
can
you
summarize
the
grass
conversation,
so
real,
quick
I
won't
take
a
ton
of
time
on
this.
A
There's
an
issue
thread
in
there
on
what
we're
thinking,
but
the
general
thinking
is
so
we
have
like
PMT,
ESP
and
then
dot
coverage
for
the
SharePoint
API
doing
something
similar
for
graph,
which
is
something
I
support.
I
think
we
all
support
it's
just
figuring
out
the
best
way
to
do
it
and
not
duplicating
a
ton
of
work.
There's
going
to
be
some
graph
support
coming
in
SharePoint
framework
and
so
kind
of
waiting
to
see
what
shape
that
takes
and
how
we
can
leverage
that,
because
that'll
take
care
of
a
lot
of
off.
A
But
then
we
also
have
the
situation
if
you're
trying
to
use
the
the
JavaScript
core
library
outside
of
SharePoint
framework.
So,
for
example,
in
like
an
electron
app
just
as
an
example,
it
would
be
really
cool
if
we
handle
the
auth
and
folks
could
just
use
the
library
there
seamlessly
as
well.
So
no
hard
decisions
but,
like
I,
said
I
think
we're
starting
to
get.
You
know
some
good
ideas
together
and
we'd
love
to
hear
other
folks
ideas
and
that
issue.
B
Let
me
unmute
myself
so
a
few
updates
on
on
the
SharePoint
framework
side
and
the
resources
on
that
side
as
well,
not
that
I'm
packing
coal
on
in
class
time
I
have
a
section
on
family
vacation,
so
not
a
massive
amount
of
actions,
because
obviously
we
g8
there
was
GA
back
in
mid
February.
There
has
been
actually
an
updated
package
after
that
which
we
would
encourage
to
people
to
actually
start
using.
B
It
is
containing
some
of
some
fixes
related
on,
for
example,
you
office,
you
are
Patrick
integration
and
how
they
work
together
from
a
guidance
perspective,
there's
new
guidance
which
was
released
earlier
today,
late
this
week
with
the
debugging
solutions
with
resource
to
recode,
with
an
f5
support,
and
all
of
that
which
is
pretty
nice
set
up.
So
you
can
actually
easily
do
development
in
Visual
Studio
code.
B
Just
by
doing
an
f5
and
putting
a
Craig
points
in
your
code,
then
then,
there's
has
been
updates
on
the
existing
documents,
for
example
the
localization
story
and
the
property
being
validation.
Guidance
has
been
updated
at
domestic
ta
version,
where
kind
of
a
still
slipping,
slides
behind
of
updating
all
of
our
documentation
to
the
GA.
B
But
that's
going
to
happen
pretty
soon,
so
we
will
have
all
of
this
updated
problem
and
obviously,
if
there's
any
issues
within
the
guidance
in
the
depth
of
stock
ownership
plan,
please
do
submit
an
issue
that
being
us
in
tech,
community
and
whatever,
because
that
way
we
will
know
that
we
need
to
fix
the
documentation
as
well
or
even
better.
If
you
know
how
to
fix
it,
you
can
always
provide
a
pull
request
and
submit
a
pull
request
against
the
repo
as
well
on
the
video
side.
So
I'm
gonna
actually
move
forward
on
this
one.
B
So
there's
a
two
new
webcasts
since
our
last
meet
up
I
think
these
are
both
new
after
that
which
are
what
your
SharePoint
administrators
know
about
Japan
framework.
So
this
is
more
for
architects,
NHK
point
administrators
kind
of
a
considerations
on
on
the
fact
that
okay,
now
that
we're
planning
to
deploy
our
SharePoint
framework
solution,
what
does
it
actually
mean?
B
What
are
the
considerations
and
all
that,
and
also
comparison
between
SharePoint
framework,
from
an
admin
perspective
between
the
different
other
options
like
add-ins
and
sandbox
solutions
and
all
Stan,
and
then
there's
a
SharePoint
framework
and
organizational
considerations
which
is
more
around?
How
do
we
create
these
solutions?
How
do
we
get
requirements?
What
we
should
be
thinking
around
the
requirements
and
all
of
that
and
both
of
these
are
available
in
the
dev
tariffs
that
come
/
blocks
or
in
our
YouTube
channel
as
a
discussion,
and
both
of
them
are
with
me
and
Waldeck.
B
Yes,
also,
tomorrow
with
me
and
Waldeck
having
that
discussion,
good
moving
on
on
things
and
one
point
before
I
actually
move
on.
So
if
there's
any
suggestions
related
on
hey,
this
is
what
I
would
like
to
see.
This
is
guide
and
process
missing.
Please
let
us
know
we
absolutely
want
to
address
any
open
questions,
any
open
issues,
any
open
topics.
We
can
do
videos,
we
can
do
by
dance.
B
We
can
do
documentation
and
all
that,
so
we
just
need
to
know
what
you
need
to
be
successful
within
SharePoint
framework
implementation,
except
the
time
and
time
to
learn
the
new
stuff
which
is
kind
of
given
that's
understandable
on
the
kind
of
a
new
stuff
which
is
a
bubbling
under
and
coming
pretty
soon.
So
this
is
something
super
super
exciting
which
is
actually
coming
from
a
work.
B
What
Eric
chops
and
polish
Schieffelin
well
mainly
Eric
for
coding
and
Paul,
for
helping
on
the
documentation
sign,
helping
on
making
the
SharePoint
framework
more
easily,
in
the
credit
with
Visual,
Studio,
2015
or
2017,
and
I'm
going
to
show
this
one
in
practice
as
well.
But
this
is
really
really
super
early
at
this
point,
and
so
you
need
to
still
wait
for
a
while
to
make
all
of
this
stuff
fully
fully
integrated
and
fully
well.
B
It
is
already
working,
but
it
can
always
be
there,
but
because
the
Visual
Studio
organization
decided
that
they're
not
going
to
play
with
us
that
well,
we
kind
of
moving
on
on
this
direction.
So
we
kind
of
work
together
with
community.
We
from
SharePoint
engineering
we're
going
to
work
together
with
community
and
build
this
kind
of
a
tooling,
which
will
then
help
adapting
SharePoint
framework,
also
using
classic
Visual,
Studio,
2015
or
2070.
B
If
you
do
AKMs
SPF
xvs
extension,
that's
the
easiest
URL
to
remember
on
this
one
that
will
redirect
you
to
the
repo
where
the
code
is.
There
is
already
an
early
call
for
release
available,
so
you
can
actually
pay
to
lay
around
and
then
there's
documentation
in
the
weakest
section,
which
requires
still
some
polishing
and
all
that,
but
that's
kind
of
given,
but
Eric
and
Paul
has
done
an
awesome
job
around
this
one.
I'm
not
actually
even
I,
haven't
checked
out
participant
people,
but
I
don't
think
either.
One
of
the
guys
are
in
the
code.
B
Maybe
Eric
is
on
the
call.
I
can
see
Eric
Eric,
Young,
okay,
Eric
jobs,
okay,
you
know,
so
this
is
an
early
thing
I'm
going
to
show
that
one
in
a
practice
after
a
next
slide.
So
quick
summary
on
to
what
the
SharePoint
engineering
or
the
splat
team,
which
is
responsable,
hasta
SharePoint
framework,
so
but
I'll
be
right.
B
Now
we're
working
on
and
obviously
we
haven't
actually
changed
the
slide
too
much
since
last
time
we
went
that's
true,
but
we're
looking
into
having
new
capabilities
on
webpart
webpart
connections
so
sending
events
across
the
web
pods,
and
it
might
be
that
in
the
first
phase
it's
only
based
on
code
and
then
in
a
future
phases.
It
will
be
a
UI
capability,
we're
looking
into
having
more
than
UI
extensions,
so
essentially
modern,
chase,
link
and
user
custom
actions.
B
We
absolutely
are
aware
that
this
has
to
be
there
for
modern
sites
and
also
for
classic
sites,
and
they
are
in
the
development,
and
these
will
then
bring
additional
yeoman
templates
as
well.
There's
improvements
for
the
workbench
which
are
in
the
queue
as
well
and
then
generally
improvements
in
the
in
the
shape
and
framework
and
also
various
other
topics
for
both
online
and
on
premises.
On
the
on-premises
side,
we've
been
pretty
vocal
and
open
on
that
one.
B
We're
looking
looking
to
relationship
on
framework
in
on-premises
during
this
calendar
year,
and
that
is
absolutely
our
in
our
intention
and
still
orientation
and
that's
going
to
be
SharePoint
2016,
not
SharePoint
2013,
at
least.
First
and
then,
depending
on
an
input
and
depending
on
depending
on
a
demand,
these
things
might
actually
change
at
some
point.
B
Good
other
stuff,
SharePoint,
documentation
and
I
would
ask
people
to
please
lose
yourself,
there's
quite
a
lot
of
background
noise,
because
somebody
seemed
to
have
dropped
their
phone
I
can't
even
find
a
person
who
has
a
cone
in
it
and
so
on
the
other
topics.
Thank
you
thanks
Patrick
and
so
the
other
topics.
We
are
looking
into
consolidating
the
SharePoint
documentation,
because,
right
now
the
SharePoint
documentation
is
partly
in
MST
and
partly
in
multiple
MSA
and
locations,
partly
interested
of
stuff
home,
slash,
SharePoint
and
all
that.
B
So
eventually,
all
of
the
SharePoint
document
we'll
be
in
the
docks
of
microsoft.com
slash
upon
so
MSDN
will
actually
going
to
go
away,
and
that's
because
of
the
MSDN
platform
is
super.
Super
super
super
old
and
it's
super
hard.
It's.
It
requires
a
PhD
level
training
to
actually
get
anything
update
there.
B
Unfortunately,
there
are
certain
challenges
which
we
need
to
tackle,
so
all
of
the
active
development
documentation
will
be
moved
to
desktops,
accomplish
a
point
and
then
eventually
the
doctor's
wife
storm,
slash
airport,
and
I
do
know
we
understand
that
it's
it's
a
pity
that
there
will
be
do
jumps,
but
it
is
just
something
what
we
need
to
do.
Unfortunately,.
B
Cute
moving
on
on
things,
so
what
I
wanted
to
quickly
do
is
show
to
the
source
to
do
20
knots
to
205
2015
extension.
There
we
go
I've
been
having
pretty
busy
day
today,
so
I'm
mister
one
number
over
there,
and
so
let
me
share
my
screen
and
I
want
to
show
this
one
in
practice.
Where
is
it?
How
does
it
actually
work
right
now
as
an
alpha
version,
and
so
you
can
actually
understand
the
behavior?
B
Yes,
we
saw
studio
205,
but
let's
start
sharing,
and
somebody
can
actually
confirm
that
you're
just
checking
I
got.
A
B
On
your
side
as
well,
Oh
Patrick,
King,
Khan
excellent.
If
you
got
it
in
the
middle
of
nowhere
and
probably
many
of
the
others
work
at
it
as
well
good.
So
this
is
the
location.
If
you
go
a
thesis
way
to
remember
this,
a
kms,
SPF
X
VX
extension
is
the
URL.
Some
can
actually
zoom
in
there
and
that's
actually
redirecting
directly
to
the
repo.
B
So,
if
I'm
hitting
an
enter
it's
going
to
redirect
to
the
right
repo
in
the
shipment
organization-
and
this
one
has
the
code,
if
you
scroll
down
here,
there
is
a
getting
started
guide
which
is
actually
in
the
wiki
of
this
repo.
This
is
actually
having
screenshots
and
what
I
need
to
do
and
how
do
you
actually
get
started
on
things
and
how
things
actually
work
I'm,
going
to
show
that
one
in
practice
in
a
second
and
one
of
the
great
benefits
out
of
this
one
is
that
this
is
actually
still
using
the
yeoman.
Now.
B
What
it
means
is
that
whenever
we
assign
shape
on
the
engineering
will
release
a
new
version,
you
will
still
an
update
that
then
get
the
updated
version
from
from
the
NPM.
But
then
the
visitors
to
the
extension
is
taking
advantage
of
the
latest
in
spell
version,
and
then
maybe
what
I
was
supposed
to
actually
show
here.
Oh
if
you
want
to
test
this
one
at
this
point,
you
can
already
download
a
release.
This
is
early
alpha
version
of
the
author
extension
nine
days
ago.
Paul
actually
gets
a
one
version.
B
B
But
let's
have
a
look
on
that
so
when
you
have
installed
the
via
the
extension,
what
it
means
is
that
I
find
start
creating
a
project
in
my
visual
studio,
underneath
the
visual
studio
space
or
bug
I
can
see
of
a
SharePoint
and
underneath
there
I
can
say
SharePoint
framework
and
SPF
XY
Park
prototype.
So
let's
actually
do
this
I'm
going
to
put
that
one
in
a
random
location.
Let's
call
this
PM
PHA
at
is
sick
demo
I'm
going
to
copy
that
and
create
the
project.
B
What
it
actually
does
is
that
it
starts
this
wizard,
which
is
then
requesting
the
needed
information
to
provision,
essentially
the
structure
for
the
for
the
SharePoint
framework
solution.
So
let's
keep
the
solution
name
the
same.
We
can
do
framework
none
or
two,
because
the
selection,
as
we
have
in
the
yeoman
templates
for
SharePoint
framework.
Let's
call
this
hello
world
doesn't
really
matter
hello,
we're
from
sick,
and
this
is
going
to
be
cool
webpart
for
us
to
play
with
and
what
actually
happens
here.
B
B
Npm
install
comment
after
scaffolding
of
the
project
and
then
I
can
run
click
generate
and
what's
going
to
happen
is
that
it?
The
solution,
is
now
doing
the
actual
scaffolding.
There
was
an
option
for
me
to
also
show
the
command
line
window,
so
it
would
actually
show
me
the
command
line
window.
Has
it's
executing
what's
actually
happening,
but
creating
the
initial
structure
without
the
installation
and
doesn't
take
too
long,
and
we
will
get
that
available
in
a
second.
B
Unless
my
visual
studio
just
crashed,
let's
see
it
is
not
responding
status
and
if
I
would
only
be
able
to
play
hardware
in
this
case.
That
would
pick
it
that
shouldn't
take
too
long
and
I
do
have
a
a
pre-configured
solution,
already
waiting
on
the
site
and
still
actually
creating
that
creating
project.
But
while
it's
doing
that,
I
can
actually
flip
on
the
other
side
as
well.
So
I
created
this
solution
before
and
what
you
essentially,
what
you
get
is
a
basic,
so
visitors
to
resolution
structure,
which
is
obviously
looking
exactly
like
the
typical.
B
So
when
we
underwear
run
the
omen,
template
as
well,
so
you'll
find
the
conflicts,
the
source,
folder
and
all
of
the
other
typical
folders
here
you're
able
to
play
with
that
with
the
files
as
well.
What's
cool
around
this
one
is
that
the
templating
or
the
extension
also
adds
additional
capabilities.
So
I
can
actually
add
a
new
item
and,
I
can
say,
add,
wave,
sorry,
Office
SharePoint
and
this
our
SharePoint
framework
and
I'm
going
to
add
a
new
quick
part.
B
Second,
with
port
into
VP
and
description
and
adding
a
second
web
part
does
only
take
a
few
seconds
because
the
solution
is
already
there,
but
I'm
not
going
to
I'm
going
to
save
some
time.
I'm
not
going
to
do
that
right
now,
stuff,
but
critical
functionality
as
well,
and
what's
really
cool
around
this
one
as
well,
can
actually
take
that
one
away.
So
I
can
OOP.
Yes,
yes,
kind
of
cancel
there.
B
We
go
so
I'm
going
to
do
an
f5
and
what
happens
is
that
it
actually
starts
the
solution
in
the
same
way
as
you
would
be
doing
called
serve
within
the
command
line
and
there's
my
window
with
spoked
on
another
screen,
so
I'm
going
to
track
and
drop
that
one
there
and
there
we
go.
It
actually
starts
compiling
and
serving
the
structure
from
that
particular
folder.
B
B
Right
back
three
seconds
come
on:
I
just
want
to
show
you
the
browser,
and
that
is
actually
problem
after
problem.
So
let's
say
on
which
window
that
that's
going
to
actually
come,
wanted
it
actually
open
that
lock
or
not.
Already
in
here
there.
We
go
now
to
open
up
the
process
on
a
new
tab,
and
we
can
actually
see
that
custom
web
part
which
I
just
created
using
the
extension
being
hosted
in
here.
B
Apparently,
my
machine
is
having
a
slightly
hard
time.
So
let's
say
I
am
requesting
that
one
more
time
there
we
go.
There's
my
custom
web
part
and
it's
working
obviously
like
it
would
be
from
a
yeoman
template,
because
the
whole
extension
is
taking
advantage
of
the
existing
yeoman
templates.
It
is
not
introducing
any
new
templates.
It
is
just
calling
the
yeoman
using
the
human
generator
using
the
right
templates
on
the
background.
So
now
this
is
missing
still
some
some
functionalities
from
missing
some
advantages,
so
it
doesn't
actually
have
a
native
debugging.
B
At
this
point
we
can
prove
figure
it
out
at
some
point,
but
the
whole
point
is
that
this
is
getting
there.
It
is
an
alpha
release
and
I
think
the
initiative
is
really
great
and
you
can
already
today
to
the
start,
testing
and
providing
an
input
and
such
as
turns
to
run
this
one
as
well.
This
doesn't
mean
that
you
need
to
do
Visual,
Studio
IDE.
B
You
can
still
do
Visual
Studio
code
I
personally
use
Visual
Studio
code,
but
there's
a
lot
of
people
who
would
like
to
use
this
to
the
IDE,
which
is
understandable
as
well.
So
this
will
essentially
enable
that
capability
as
well
so
create
work
from
Eric's,
Epson
and
pull
shuffling
roam.
Does
this
thinking
cute
but
I
think
that's
it
from
my
side?
So,
let's
sleep
do
we
want
to
flip
directly
to
next
demo,
Patrick
yeah.
A
C
You
are
awesome,
so
I'd
like
to
show
you
today
something
we
we've
been
experimenting
at
valo
in
the
last
couple
of
weeks
and
months
so
yeah.
So
you
got
currently
a
plain
SharePoint
screen.
I
want
to
show
you
what
we
did
so
we're
actually
migrating
Oliver,
a
fellow
internet
solution
from
a
classic
experience
to
the
modern
experience
using
the
modern
toolset.
So
we're
going
all
the
way
through
SharePoint
framework
and
one
of
the
framework
we're
using
the
most
is
right
at
Jas.
C
C
Evidently,
there
is
no
SharePoint
framework
implementation
for
Araya,
so
I've
been
working
with
the
team
for
the
last
couple
of
weeks
to
make
that
happen
and
to
add
some
kind
of
a
default
Rio
J's
web
part
that
can
be
leveraged
for
multiple
web
parts.
So
that's
what
I
will
show
you
today.
I
just
want
to
show
you
what
it
will
be
covering
so
I
created
a
very,
very
simple
list:
viewer
that
this
viewer
will
be
just
a
list
viewer,
so
you
select
the
list
and
then
you
see
the
content
of
that
place.
C
It
just
like
that
here
you
see,
I,
don't
have
anything
selected
here.
You
idiot
you
select
documents,
and
then
you
see
that
the
content
of
that
list
so
very,
very
simple
solution
that
I
want
to
show
you,
but
it
actually
want
to
show
you
the
all
the
all
the
fundamentals,
all.
How
is
that
built
in
the
framework
it's
also
available
on
github,
so
I
do
want
to
take
a
look
at
it.
It's
all
ear,
so
good
job
comm
slash
the
personalized
SPF
X
right
at
list.
So
all
the
code
in
documentation
is
absolutely
all
there.
C
So
now
to
the
code,
I
will
skip
the
part
where
we
could.
We
actually
create
a
SharePoint
framework
project.
Just
do
a
yo-yo
SharePoint
on
you
select
no
JavaScript
framework,
and
then
you
add
to
that
file.
You
add
to
that
package
that
JSON
file,
where
you
will
need
to
add
actually
only
two
different
packages,
one
which
is
riot
and
one
which
is
the
riot
typescript
implementation
of
riot,
so
you'll,
be
able
to
write
in
typescript
and
add
all
the
types
available
right
in
your
web
part
for
my
use
case.
C
So
for
me,
riot
is
a
lot
like
a
match
made
in
heaven
between
anvil
bar,
so
very,
very
simple
way
of
templating
your
code
and
completing
your
views
and
react
in
terms
of
component
in
terms
of
what
you're
doing
in
terms
of
a
simple
bundle
component
that
can
be
reused
in
multiple
other
components.
So
this
is
exactly
how
we
use
riot.
So
first
thing
you
need
to
do,
or
first
thing
you
need
to
understand-
is
that
you
will
add
your
basic
list
view
web
part
list
viewer
web
part.
C
That
is
here
that
will
extend
a
web
part
called
riot
client-side
web
part.
I'll
come
back
to
that
to
that
one
right
after,
but
that's
pretty
much
the
only
thing
you're
doing
in
that
class.
That
class
is
only
implementing
some
back-end
logic
that
exists
in
another
class.
That
will
do
everything
for
you.
So
in
terms
of
logic,
you
don't
add
a
lot
to
do
and
that's
right.
A
client-side
web
part
class
is
a
very
simple
one.
So
it's
more
of
an
abstract
of
some
tags
and
some
web
part
options
and
route
company
type.
C
That
will
in
fact,
do
the
rendering
for
you
and
the
mounting
of
that
web
part.
So
you
will
just
say
this
is
the
tag
that
I
want
to
register
on
my
page
right
here,
and
this
is
how
I
want
to
mount
my
object.
So
this
is
how
you
just
say
to
riot
hey
by
the
way:
here's
my
Dom
element,
so
that
is
being
passed
by
the
SharePoint
frameworks.
C
Here's
the
tag
that
I
want
to
mount
and
ears
the
web
part
options,
and
then
riots
will
take
care
of
bundling
everything
together,
making
sure
that
your
JavaScript
file
is
glued
to
your
your
templates
and
to
your
models
and
to
everything
you
need
and
there
you
go
you're
good
to
go
so,
for
example,
in
my
list,
viewer
web
part
I'm
using
one
tag,
which
is
called
the
list
viewer
and
my
root
component
type.
Is
that
this
your?
So,
let's
see
what's
in
that
list,
you
were
class,
so
I
have
here
my
lure.
C
C
Some
of
those
different
elements,
different
options,
and
then
the
only
thing
I
need
to
do
is
once
my
component
is
actually
mounted
one
once
the
riots
that
mount
happens
and
that
might
now
I'm
ready
to
write
to
run
code
I
just
I
can
use
the
async
await
async,
so
in
JavaScript
and
I
just
think
to
init
my
web
part
I'm
checking
if
there's
a
list
ID.
If
there's
a
list,
ID
I
just
go
and
I
actually
use
PN
pjs
to
get
those
those
list.
C
Elements
and
I
am
elements
right
here
and
I
can
automatically
map
them
to
my
business
objects.
My
business
objects
are
actually
very,
very
simple.
Those
are
my
a
very
simple
business
logic.
By
the
way
Patrick
on
that.
That
is
absolutely
awesome.
I
can
easily
see
that
happening
in
all
of
my
projects,
currently
so
very,
very
happy
to
see
that
in
the
in
the
in
the
framework
and
now
I
lost
my
file
and
then
I
just
floated
here.
This
is
one
of
the
key
of
the
right.
Is
you
need
to
instruct
that?
C
Okay,
all
of
the
components
and
subcomponents,
please
reload
yourselves,
and
then
it's
just
going
to
instruct
okay,
everyone
just
redraw
yourself,
because
something
changed
in
that
case
because
we're
using
Ajax
calls
we
need
to
do
the
update
by
ourselves
if
it
was
just
gyroscope
calls
right
is
also
able
to
understand
the
context
of
your
of
your
object
of
your
component
and
then
automatically
update
that
and
then
what's
in
that
component.
So
you
can
see
here.
I
have
a
component,
so
here
I
have
my
tag.
C
That
is
a
custom
tag
that
writers
will
understand
and
use
as
a
mount
point
for
everything
and
then
I
have
ear
a
very
simple
placeholder,
which
is
pretty
much
the
the
basic
one
that
exists
when
you
create
a
new
SharePoint
framework.
Webparts.
Nothing
very
sexy
in
here
I'm,
using
the
the
files
from
office
to
our
fabric
put
a
title,
and
this
is
where
riot
GS
comes
into
play,
and
this
is
where
I
think
it's
relooked,
similar
to
what
angular
or
what
anvil
bar
is
doing
in
terms
of
templating.
C
So
here
you
have,
for
example,
the
list.
So
if
I
add
a
list,
then
I
like
to
display
that
div,
if
I,
don't
add
a
list,
please
please
just
leave
this
one,
and
this
is
where
everything
happens.
This
is
where
I
can
add
some
UI
logic
living
in
my
templates
and
I
can
add
some
JavaScript
and
back-end
logic
living
in
my
typescript
files,
and
then
I
can
also
embed
or
nest
multiple
components.
C
So,
for
example,
here
as
an
office,
you
are
fabric
table
which
is
a
custom
component
I
built
on
top
of
the
office
right
fabric,
but
I
can
send
some
parameters.
I
can
sense
a
are
you
loading,
here's,
the
bunch
of
items
I
want
you
to
so
I.
Keep
that
office
UI
fabric
table
very,
very
specific.
There's
no
logic
in
there.
C
Just
displeased
stuff
here
are
their
Styles
I
want
you
to
use
it
all
come
back
to
this
one
and
I
want
it
to
be
displayed
only
if
there
is
a
list
so
meaning
that
if
there
is
no
list
selected,
I
don't
want
to
display
an
empty
table.
I
will
just
display
that
entire
component,
based
on
the
existence
of
lists,
then
that
table
file.
For
example,
if
I'm
going
right
here,
it's
actually
nothing,
there's
nothing
in
there
there's
one
sub
component
type,
which
is
a
spinner,
so
I'm
using
also
an
office.
C
You
are
fabric
spinner,
to
show
that
I
am
currently
loading
new
stuff,
but
it's
mainly
an
HTML
file,
and
this
is
where
I
can
say:
okay,
I
have
my
component
table.
What
are
the
titles
or
different
columns?
Then
I
can
play
with
that.
So
everything
that
is
being
brought
by
my
parent
component
is
being
pushed
to
my
sub
component,
and
everything
can
work
with
that
something.
You
need
to
note
here
to
make
sure
that
all
your
web
parts
are
actually
working
a
bit
like
independently
of
this
framework
they're
using
in
terms
of
UI.
C
You
cannot
just
use
ms
table
as
your
class.
You
need
to
use
the
styles
version,
so
the
modular
version
of
your
styles
that
is
built
automatically
by
Avaya
about
a
SharePoint
framework.
So
when
you
have
a
module,
CSS
file,
I
can
import
stuff
but
automatically
it
creates
a
type
script
file,
which
is
this
one,
which
adds
some
kind
of
a
short
apps
or
short
grid.
C
In
the
end,
that
will
allow
me
to
be
able
to
use
those
Styles,
because
those
are
the
one
that
are
mounted
in
my
web
pack
right
here,
and
this
is
how
it
actually
works
in
the
air
can
do
my
stuff
and
I
can
embed
more
and
more
of
of
my
components
or
air.
For
example,
I
have
an
office
John,
favorite
spinner.
What's
my
label
on
it
load
I
want
to
pass
in
my
style,
so
you
can
also
leverage
the
same
kind
of
styling
that
is
used
over
there
and
I
can
do
some
logic.
C
If
I'm
loading
I
want
to
show
the
spinner,
if
I'm,
not
loading
but
I,
don't
have
any
items.
I
want
to
show
no
record
found,
but
it's
not
I'll
just
push
in
all
my
items
to
be
shown
directly
in
my
in
my
screen
in
my
in
my
list.
So
that's
why?
When
I?
Actually,
if
I
delete
that
file
and
I
just
add
a
new
list,
viewer
I,
don't
have
any
list
so
I'm,
not
showing
anything.
Then
I
select
my
documents.
C
I
can
see
a
prices,
an
important
document,
a
super
document
because
I
have
those
documents.
But
if
I'm
changing,
for
example,
to
fern
templates,
you
will
see
the
loader
actually,
the
loader
stops
working
now,
but
anyway
now
you
will
see
that
and
you
will
see
that
it
says
no
record
found
when
you
have
nothing
in
there
or
whatever.
So
that
is
very,
very
simple,
SharePoint
framework
logic:
there's
no
magic
happening
in
there,
but
the
magic
is
really
on
the
actual
web
part
and
on
the
actual
component.
C
So,
for
example,
if
I'm
going
here,
keep
in
mind
that
I'm
actually
using
that
decorator
right
here
right
at
the
template,
you
can
put
it
here
directly,
your
string
or
your
template
literals
thanks
DC
for
correcting
me
on
that
earlier.
So
here
you
can
add
your
template
right
here.
So
I
love
to
keep
those
two
things
very
separate.
Just
because
it's
easier
for
me,
so
you
can
require
your
file
as
a
string
and
then
it's
going
to
download
or
package
that
list
your
HTML
file
from
that
file.
C
Air
is
going
to
embed
it
and,
in
the
end,
it's
going
to
actually
create
what
riot
is
expecting,
which
is
it's
just
a
big
mess
of
JavaScript
that
is
used
to
render
our
different
components.
So
the
basics
of
all
of
that
is
really
you
as
a
web
part
that
web
part
needs
to
enter
it
from
that
riot
GS,
client-side
web
part
and
automatically
that
riot
will
do
the
Mon
thing
that
you
asked
to
do
in
the
inner
areas
which
is
the
following.
So
it
will
do
that,
and
this
is
where
all
the
magic
actually
happens.
C
It
is
very
similar
to
how
the
prototype
of
anger
or
angular
for
SPF
fix
web
part
is
actually
working
a
just
in
that
it's
it's
so
much
simpler
and
so
much
lighter.
For
example,
we
are
talking
about
9k
nine
kilobytes
of
size
for
a
riot
if
we
compare
that
to,
for
example,
to
to
react,
which
is
like
forty
nine
kilobytes
and
just
don't
compare
that
to
to
angular
and
I
think
we
we
get
into
the
megabytes.
So
it's
a
very,
very
lightweight,
but
it
gets
the
job
done.
C
It's
all
available.
It's
on
github
I'll
try
to
connect
with
you
guys
at
PMP
two
to
see
if
there's
any
value
in
building
that
in
the
samples,
it's
all
it's
all
there
and
it
works
very
well,
and
we've
been
on
that
for
our
couple
of
next
components
as
we
as
we
do
at
hello.
We
also
already
started
to
do
that
kind
of
migration.
A
tour
is
very,
very
well.
It's
super
super
super
quick.
C
If
you
want
there's
also
a
router
available,
so
you
can
have
single
page
applications
that
is
built
with
Rio
GS
that
can
also
be
very,
very
easily
embedded
in
a
SharePoint
framework
web
part.
So
anything
you
want
to
do
with
that
kind
of
mechanism
work,
and
that
is
pretty
much
it
that's.
What
I
wanted
to
show
Patrick
also.
A
Very
cool
stuff,
like
I,
said
the
top
I
I
have
not
ever
really
used
much
riot,
but
it
looks
very
small
and
clean
and
I
think
that's
really
cool,
so
I
think
a
sample
for
this
would
be
very
valuable
for
folks
in
the
community
to
see
just
another
way
to
work
with
SharePoint
framework
again
trying
to
support
as
many
frameworks
you
know
as
possible
about
stop
the
current
presentation.
One
of
these
days,
I'm
going
to
learn
how
to
use
Skype.
A
Thank
you
very
much,
so
jumping
back
great
demo,
so
we
did
demo,
we
did
demo,
so
we've
got
a
good
15
or
so
minutes
for
open
discussion.
If
folks
have
questions
I
know,
we've
had
a
good
conversation
going
on
Adel
Jas
here
in
the
the
I
am
window,
but
this
is
the
part
of
the
call
where,
if
you
have
questions
or
comments,
you
want
to
come
off.
Mute
you're,
welcome
to
do
that
or
typing
there
in
the
IM
window
is
also
great.
It
looks
like
everything
got
pretty
much
answered
any
headway
with
gulf
support.
A
B
And
let's
be
clear
on
this:
one
we're
wrong
people,
don't,
sir,
on
this
one.
So
I'm
I'm
working
in
a
team
that
was
responsible
of
creating
to
SharePoint
framework
I
have
no
idea
of
who's.
Even
the
people
behind
of
the
government
form
support,
so
the
right
way
to
maybe
find
the
right
people
with
a
that,
if
you
have
a
governmental
customer
or
you
are
working
directly
with
the
Microsoft
in
a
governmental
side,
is
connect
those
people
who
are
providing
that
service.
B
Unfortunately,
we
in
the
engineering
in
the
actual
engineering,
not
in
the
in
the
service
engineering
into
actual
engineering,
we
don't
even
know
who's
managing
these
funds.
So
I
don't
know
if
the
people
even
responsible
of
the
governmental
service,
are
aware
of
the
demand
for
SharePoint
framework.
That's
the
problem.
So
if
you
would
you
if
I
would
encourage
people
to
use
those
channels
which
they
have
for
much
of
people
using
that
through.
A
A
Oh
yeah
AC
definitely
reach
out.
If
you
want
to
do
a
presentation,
let
us
know,
and
that
goes
for
everybody
as
well.
If
you
want
to
do
demo
something
present,
some
of
your
work
I
would
love
to
love
to
have
you
on
the
call
of
to
give
you
that
time
cool
well,
in
that
case,
I'm
gonna,
say
I,
don't
see
any
other
questions,
so
we
can
go
ahead
and
close
up
for
this
week.
Thank
you,
everybody,
as
always
for
joining
the
call.
Thank
you
visa
and
said
for
the
great
demos
really
cool
stuff.