►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 1st of March. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI and Reusable SPFx controls.
You can download an invite to this bi-weekly call from https://aka.ms/sppnp-js-sig-call.
A
Hello
and
welcome
to
the
SharePoint
framework
in
JavaScript
special
interest
group
bi-weekly
meeting.
It
is
March
15th
2018
I
am
Patrick
Rodgers
I'm
joined
by
vasive
Onan
as
well
as
all
of
you.
Thank
you,
everybody
for
joining
the
call
I
apologize.
My
voice
is
a
little
rough
I'm
getting
over
what
seems
like
a
month-long
cold.
A
A
Just
we
had
too
much
to
do
so.
The
idea
was,
we
will
start
and
was
going
through
and
meet
a
couple
folks
here.
The
idea
was,
we
would
create
these
forums.
So
we
have
this
one
for
client-side
development
and
SharePoint
framework.
We
also
have
one
for
C,
Psalm
and
PowerShell
development
that
we
create
these
specialized
forums.
So
we
can
have
a
little
bit
deeper
dive
on
those
particular
topics,
as
well
as
give
folks
a
way
to
participate
in
an
area
that
might
be
more
interesting
to
them.
A
But
you're,
of
course,
welcome
to
participate
in
all
of
these
calls.
If
you
would
like
to
do
so,
but
the
idea
being,
if
you're,
more
interested
in
client-side
development
or
PowerShell
development,
we've
got
a
little
bit
of
a
more
specialized
place
for
you
to
go
and
get
that
information,
and
here
we
try
and
foster
an
open
discussion
on
the
SharePoint
framework,
client-side
development
patterns
in
general
and
then
as
well.
A
We
talk
about
the
patterns
and
practices,
pjs
libraries
that
we're
working
on
together
as
a
group
to
links
down
there
at
the
bottom,
SP
P
and
P
community,
we'll
take
you
to
the
Microsoft
tech
community,
around
SharePoint
development
and
that's
SharePoint
development,
all
up
so
not
just
SharePoint
framework,
but
all
of
SharePoint
development.
That's
a
great
place.
If
you
have
general
questions,
how
do
I
design
my
application
things
like
that
that
aren't
necessarily
potentially
an
issue
with
a
specific
library.
A
That's
the
great
forum
to
ask
those
kind
of
questions.
We
have
an
awesome
active
community
there
so
check
that
out
and
then
as
well.
Sp
dev
Doc's
will
take
you
to
all
the
documentation
for
SharePoint
again
all
up,
so
it
and
Cindy's
Saints.
You
can't
see
my
screen
I'm
just
sharing
to
the
Skype
presentation,
so
I'm,
not
hopefully,
shouldn't
have
anything
to
do
with
my
particular
screen.
Okay,.
A
And
so
the
SP
dev
Docs
is
SharePoint
development
documentation
all
up
so
whether
you're
doing
SharePoint
framework
and
want
to
learn
how
to
do
that
and
get
started
with
that
or
classic
SharePoint
development
with
solutions.
That's
all
covered
in
the
dev
Doc's
there
and
we're
always
looking
to
improve
that
and,
of
course
welcome
your
feedback
on
the
documentation,
as
we
do
with
everything
we
do
our
agenda
for
this
week's
call
engineering
update
on
the
SharePoint
framework
p.m.
A
PJs,
client
library,
update
office,
365
CLI
update
an
update
on
the
P
and
P
reusable
client
controls,
and
then
we've
got
three
great
community
demos.
Today,
Eric
Skaggs
is
going
to
demo
docker
with
SPF
X
varam
on
Deshpande
is
going
to
do
it
as
your
Active
Directory
secure
as
your
functions
and
how
to
call
those
as
and
then
Sergei
Sergei
is
going
to
do.
A
My
favorite
way
to
get
folks
involved
is
to
do
a
demo
on
these
calls,
so
that
demo
could
be
a
SharePoint
framework
solution,
a
PM
pjs
based
solution,
whether
that's
inside
or
outside
of
SharePoint
framework,
or
it
could
be
just
client-side
development
in
SharePoint
in
general.
Right,
maybe
you've
done
something
on
a
script.
Editor
web
part
that
it's
you
know.
First,
a
2010
SharePoint
2010
that
you'd
like
to
show
off
or
some
other
kinds,
definitely
welcome
all
those
demos.
A
You
can
always
contribute
on
github,
so
whether
you
find
issues
and
report
those
whether
you're
giving
us
feedback
about
any
of
the
various
libraries
or
projects
excuse
me
or
whether
you
want
to
actually
do
contribute
some
code
through
a
pull
request,
really
welcome
and
thank
everybody
for
their
work
there
and
contributions
on
github
and
then,
generally
speaking,
the
final
way
to
participate
is
just
give
us
feedback.
How
are
we
doing?
How
are
these
calls
going?
How
are
the
samples
etc?
How
are
things
we
definitely
love
to
hear
that
feedback?
A
B
B
Since
the
documentation
guidance
Patrick
did
mention
this
already,
but
akms
espied,
abducts
or
endorsed
of
my
stuff.
That
comes
a
SharePoint.
You
will
land
into
our
dev
guidance
and
deaf
documentation
and
we're
looking
into
doing
quite
a
lot
of
updates
here.
Pretty
recently,
we
do
have
new
REST
API
documentation
coming
up.
We
do
have
your
other
documentation
and
scenario-based
guidance
coming
up
as
well
one
of
the
things
what
I
actually
did
a
well.
B
We
did
a
modification
here
yesterday
which
hopefully
didn't
shock
anybody
if
you
tried
this
already
and
but
the
commenting
system
in
the
rest
of
Microsoft
has
been
changed.
So
this
commenting
system
now
is
based
on
github.
So
if
you
open
up
a
comment
or
add
a
comment
on
a
document,
for
example,
pinpointing
that
there's
something
wrong
or
you
have
a
question
and
that
issue
or
that
comment
will
be
actually
an
issue
within
our
SPD
of
Docs
issuers.
B
You
know
this
actually
helps
us
to
track
all
of
your
questions
and
all
of
your
issues
and
comments,
so
we're
able
to
then
trace
back
on
what
actually
needs
to
be
done
on
the
engineering
side
and
also
you
can
then
follow
up
on
those
answers
from
a
key
table.
Issue
list
as
well.
I
think
it's
a
great
great,
great
great
improvement,
because
the
live
fire
which
we
used
here
in
the
past
was
completely
independent
and
isolated
solution
and
I
probably
should
have
been
saying
that.
B
But
it
was
surprisingly
hard
to
follow
up
on
on
the
comments
which
were
arriving
through
the
live
fire,
so
the
old
commenting
system.
So
now
that
they're
in
key
talk,
we
have
a
one
location
which
we
can
easily
then
trace
on
the
comments
and
follow
up
on
them
so
great
great
great
to
chase
the
kind
of
related
on
that
one.
B
It's
the
same
issue
list
which
we
now
we're
keeping
this
on
these
presentations
every
single
time,
because
please
please
please,
please,
when
you
find
an
issue
in
SharePoint
Online,
if
we
run
into
API
issues,
if
you
run
into
unexplainable
chortling
issues,
please
let
us
know
don't
go
and
run
in
Twitter.
Well
sure
you
can
absolutely
do
that
as
well.
But
on
top
of
that,
please
make
sure
that
you
report
the
issue
for
us,
so
were
able
to
fix
that
for
you
and
that
we're
aware
of
those
issues
which
are
happening.
B
So
a
chemist
SPF
issues
is
absolutely
the
rotation
where
you
can
go.
You
do
not
have
to
have
a
support.
A
premier
support
you
do
not
have
to
have
anything
we'll
try
to
help
you
as
fast
as
possible.
We
do
triage
incoming
issues
in
here
twice
a
week
at
least
typically
last
week
was
an
exception
to
the
MVP
summit
so
or
if
our
engineering
and
most
super
super
busy
so
we're
slightly
behind
off
the
schedule
we're
trying
to
catch
up
during
this
week.
B
So
we
have
an
extended
timing
for
this
triage,
for
example,
later
today,
together
with
my
engineers
now,
but
anyway,
run
into
an
issue
in
the
API
level
customizations
even
in
on-premises
customization,
please
let
us
know
submit
an
issue
here,
we'll
process
that
and
get
it
fixed.
There
has
been
quite
a
lot
of
nice
issue
well
in
quotes
nice
tissue
stuff
with
it,
which
we've
been
able
to
then
identify
and
in
the
underlying
services,
and
then
were
able
to
fix
them
so
pretty
reason.
B
Then,
for
example,
there
was
fixes
around
SharePoint
adding
model
and
ALM
api's
and
how
they
work
together
and
they
all
generated
from
discussions
in
this
issue.
So
this
is
super
important
for
us
to
you
to.
Let
us
know
if
you're
running
into
in
a
random
issues
now
on
the
SharePoint
framework
slide.
This
is
the
classic
slide
which
I
used
in
the
bi-weekly
course
as
well
around
the
SharePoint
framework,
but
it's
changed
slightly,
so
I
changed
the
scale,
so
I'm
not
gonna
show
the
quote
from
last
August.
B
This
is
now
growth
from
start
of
this
year,
so
I'm
gonna
probably
keep
this
one
I'm,
just
adding
the
the
updated
dates
there
in
the
future.
It
does
not
tell
you
what
is
the
metric,
because
I'm
not
allowed
I'm
not
allowed
to
actually
tell
you
that,
but
it
shows
you
the
growth
from
a
let's
say:
krav
metric
perspective.
B
So,
basically,
from
start
of
the
year,
we
almost
grove
we
crew,
already
almost
50%
from
a
chevron
framework
reduction
perspective,
which
is
really
if
the
assumption
is
that
will
double
easily
the
SharePoint
framework
usage
by
end
of
June
and
already
today
we
are
actually
doing
more
SharePoint,
there's
more
SharePoint
framework
uses
in
SharePoint
Online
in
a
day,
then
for
SharePoint
add-ins
in
a
month.
So
that
will
give
you
the
scale
of
adaption.
So
if
you're,
trying
to
figure
out
is,
are
people
actually
using
the
SharePoint
framework,
because
it's
very
for
our
starting
learning
dancers?
B
B
And
for
the
yellow,
yellow
line
is
not
about
the
fourth
4:29
but
related
on
4:29
stagnation.
If
you
run
into
those,
if
you
have
those
please
let
us
know,
we
need
to
understand
the
scale
of
those
4:29.
It's
stay.
Discussion
what's
happened,
for
example,
are
during
a
weekend
in
twitter,
so
I
just
want
to
make
sure
that
we
get
those
officially
register
now
and
on
actually
on
that
one
there's
a
good
comment
from
Vince
and
it
would
be
nice
to
have
a
met
request
by
FX
where's.
B
The
script
links
well
as
a
script
editor
web
part,
and
that's
a
that
shows
that
you
understand
the
the
biggest
competitor.
What
you
have
on
favorite
also
has
in
the
SharePoint
Online,
which
is
a
good
question.
I
cannot
give
you
the
numbers
on
that,
but
the
script
editor
usage
is
not
crowing.
So,
basically
right
now
we
do
accept
the
realities
of
life
so
that
there's
a
lot
of
tricky
editor
web
part,
customizations
and
SharePoint
Online,
but
usage
of
the
script
that
the
web
part
is
not
growing.
B
Even
though
the
users
of
SharePoint
Online
is
growing
and
sharepoint
favor
of
users
has
grown,
so
that
means
that
we
are
catching
which
SharePoint
framework
around
the
script
editor
web
part
based
customizations,
but
I
can't
give
you
the
exact
numbers,
because
we
don't
have
a
clearance
of
showing
those
numbers
huge.
So
quick
update
on
a
road
map
I
showed
this
one
already
in
Tuesday's
monthly
community
call
us
well
nothing
no
chances
since
Tuesday,
which
is
understandable.
Donations
comparing
to
the
two
weeks
ago,
from
a
SharePoint
framework
community
called
perspective.
B
Is
that
the
hop
sites
and
hop
a
is
in
rollout
in
progress
status,
and
this
one
you
will
see
more
announcements
on
that.
One
I
think
we'll
publish
out
the
API
documentation
for
that
one.
We
made
it
this
week,
potentially
tomorrow
or
then
on
Monday,
and
that
has
the
rest,
api
sand
and
other
details.
So
how
can
you
set
aside
to
a
hub
side
and
all
of
that
not
explicitly
related
on
SharePoint
favored
but
related,
absolutely
related
on
internship
and
online
development
cycles?
B
B
Is
asking
what
will
be
announced
in
May?
Let's
see
what
happens
in
May,
that's
a
good
question
so,
but
there's
cool
stuff,
new
core
stuff
coming
on
absolutely
ownership,
one
framework
platform
and
there's
I.
Can
let's
put
it
this
way.
The
MVP
summit
was
last
week
and
I
think
at
least
all
of
them.
It
pays
for
super
excited
on
what
we
had
on
the
pipeline,
so
I
think
we're
heading
in
the
right
direction.
B
A
Finally,
I
was
able
to
get
myself
off
mute,
so
quick
update
on
PJs
libraries
so
see
the
nsj
support
is
still
in
the
works
again.
We've
still
we've
been
approved,
but
they
just
have
so
much
to
process
over
there.
That
is
just
taking
some
time.
So
I
will
announce
when
that
is
released.
But
the
nice
thing
about
CD
MJS
is
once
you're
in
it.
Auto
updates
every
time,
there's
a
release,
so
a
very
cool
thing
they've
built
over
there,
but
getting
the
new
libraries
listed
is
still
coming
along.
A
So
the
a
ad
that
the
azure
active
directory
client
is
done.
So
that's
the
in
browser,
client
and
that's
actually
part
of
the
new
there's
a
beta
release
out
for
all
the
scoped
libraries.
You
know
check
that
stuff
out,
but
the
ad
client
is
done
and
there's
a
simple
basic
Doc's
page
there
and
we'll
look
to
improve
that
as
we
get
closer
to
actually
releasing
that
as
part
of
a
release.
A
So
folks
can
see
that
and
have
another
sample.
Looking
at
the
roadmap,
where
we're
heading
I
did
want
to
mention
I
know,
there's
some
stuff,
that's
built
up
on
the
issues
list
that
I
haven't
gotten
around
to
I
know.
There's
been
some
great
discussions
from
folks
on
there
promise
you
not
ignoring
it.
I've
just
been
quite
busy
with
other
responsibilities,
so
we'll
circle
back
to
that
stuff.
We'll
definitely
have
a
look
at
all
that
before
the
next
release
did
want
to
encourage
folks,
if
you
have
ideas,
there's
some
great
ideas
out
there
now.
A
But
if
you
have
your
own
ideas
for
enhancing
the
libraries,
I
definitely
want
to
hear
from
you.
So
please
post
those
just
go
ahead
and
post
them
in
the
issues
list
and
do
please
make
sure
to
include
enough
information.
We
can
understand
the
idea
and
then
do
kind
of
keep
an
eye
on
that.
In
case
we
have
some
follow-up
questions.
You
know
as
we
get
to
that
and
I
did
want
to
mention
and
we'll
have
much
more
publicity
around
this
when
it
happens.
A
So
we
will,
like
I,
said
much
more
publicity
around
that
when
it
happens,
it'll
change
the
URL
of
the
documentation
as
well
it'll
be
P
and
P
github,
io,
/,
p
and
PJs
will
be
in
the
the
new
documentation
URL.
But
so
that
is
a
change.
That's
upcoming
I!
Don't
think
it
should
be
too
disruptive.
We
don't
have
a
ton
of
Forks
there
yet,
but
did
want
to
let
folks
know
kind
of
announced
that
we
just
made
the
decision
earlier
this
week.
Npm
packages
will
not
change.
A
A
So
github
does
a
very
cool
thing
when
you
rename
something
it
actually
puts
in
place
redirects
for
you
and
their
system
is
so
sophisticated
that,
even
if
you
were
to
you,
know,
have
your
remotes
set
up
against
the
old
URL
and
things
you
would
still
be
able
to
actually
do
pools
against
the
old
URL,
but
you'll
get
a
little
message
comes
up
that
I
forget
says
something
along
the
lines
of
this
repository
is
moved.
You
should
update
your
settings,
so
nothing
should
really
break
for
anyone
initially,
but
did
want
to
sort
of.
A
So
I
am
going
to
cover
the
office
365
CLI
updates.
We
are
at
version
100
for
the
CL.
So
that's
a
always
a
cool
milestone
to
get
to
an
official
1.0
release.
So
that's
really
cool.
It's
got
new
SPO
commands,
so
SharePoint
Online
commands
around
managing
files,
lists
property
bags
sites
and
webs
support
for
Microsoft
graph
has
been
added
in
there,
as
well
as
the
first
set
of
commands
for
managing
groups
through
graph,
so
that
that
work
went
hand-in-hand
and
then
there
is
also
a
new
beta
release.
A
That's
out,
in
addition
to
the
1.0
release
that
has
some
commands
around
removing
groups,
managing
themes
and
applying
site
designs.
You
can
always
find
more
information
at
aaaa,
MS,
Office,
365
CLI,
and
for
those
of
you
that
haven't
tried
it
or
haven't,
had
a
chance
to
check
out
the
videos
you
can
always
install
it
and
play
with
it
with
NPM
I
at
PMP,
slash
office,
65
CLI
along
the
bottom
there.
If
you
have
questions
or
comments
around
the
CLI
waldek
is
following
around
the
office.
365
CLI
tag
on
Twitter
as
well.
A
A
Submissions
via
pull
request
so
really
appreciate
that
from
everybody
and
want
to
say
thank
you
next
up,
updates
on
the
SharePoint
framework
patterns
and
practices,
reusable
components.
So
there's
two
different
sets
of
things
here.
The
first
set
is
the
SPF
X
react
controls,
and
these
are
controls
obviously
meant
to
work
in
react
and
simplify
kind
of
some
of
the
basic
structures
you
might
want
to
reuse
and
react
so
giving
you
some
nice
reusable
controls
for
both
these
package
they've
optimized
the
telemetry.
So
it's
only
pushing
the
control
data
to
reduce
some
of
the
net
traffic.
A
That's
going
back
and
forth
and
then
as
well.
The
web
part
title
will
hide
the
control
completely
when
empty
will
hide
the
title
control
completely
when
empty.
So
those
are
updates
coming
back
from
issues
and
then
as
well
for
the
property
controls.
So
these
are
controls
that
you
might
use
in
the
property
pane.
So
when
you
edit
your
SharePoint
framework
control
on
the
page
and
adjust
its
properties,
these
are
a
set
of
reusable
ready
to
go
property
controls
to
help
you.
A
It
did
not
work
as
expected,
and
now
it
does
work
as
expected.
So
thank
you
to
the
folks
for
reporting
the
issues
and
great
work
getting
those
fixed.
If
you
haven't,
please
do
check
out
the
webcast
akms
SPF
x,
SP,
FX,
controls
webcast,
and
that
will
do
a
nice
introduction
to
both
of
these
things
both
of
these
projects
and
how
you
can
get
started
using
them
in
your
projects
that
you're
writing.
A
So
with
that
we've
got
three
demos
today,
so
I
want
to
make
sure
we
leave
plenty
of
time
and
I.
Think
we've
done
that
so
Eric.
If
you
are
on
the
call
and
ready
to
go
eric,
has
got
a
demo
around
working
with
SharePoint
framework
in
excuse
me
in
docker
yep.
Can
you
hear
me?
Yes,
hi
Eric,
so
our
presenter,
if
you
want
to
go
ahead
and
take
over
and
get
started
just.
C
Good,
the
lovely
blue
homepage
right
yep,
make
it
a
woman
cool.
Thank
you
very
much
thanks
for
having
me
so
it
my
name
is
Eric
Skaggs
I
work
for
catapult
systems,
and
you
can't
really
have
a
conversation
about
doctor
and
a
SharePoint
framework.
In
my
opinion,
without
talking
about
this
particular
article
and
our
good
friend
waldek.
C
This
is
this
articles.
What
I'm
everything
I'm
doing
is
based
on.
So,
if
you're
looking
for
a
ride
up
or
step
by
step
on
how
to
do
this
and
get
started,
wall
mix
article
here
really
covers
it.
He
talks
about
the
SharePoint
dev
tool
chain,
docker
101.
He
gives
you
a
sample.
Docker
file
you'll
see
a
several
copy
paper
versions
that
I
have
of
this
same
thing
and
in
particular,
there's
a
section
of
this
article.
C
C
So
we
we
really
need
to
be
cognizant
and
aware
of
how
long
it's
taking
developers
to
get
started
on
working
with
something,
and
so,
if
you're
not
familiar
with
the
SharePoint
framework
or
you're,
not
familiar
with
docker
or
even
if
you
are,
you
may
have
various
things
installed
on
your
machine
that
conflict
with
what
we
need
and
what
we're
using
inside
our
development
for
the
SharePoint
framework
solutions
where
we're
on
four
fuse.
So
that's
kind
of
the
the
business
problem
here
that
I'm
trying
to
solve
is
with
developers
coming
and
going.
C
How
do
I
minimize
the
overhead
of
troubleshooting
versions
of
node,
NPM,
gulp
yo,
the
Microsoft
SharePoint
generator
for
yo,
etc,
etc?
So
this
is
a
great
article
that
details
the
process
of
how
to
get
started
with
dr.
If
you
haven't
gone
through
this
and
you're
interested
in
docker
or
giving
that
a
shot.
This
is
definitely
the
article
for
you.
So
I've
got.
We
manage
our
work
in
VST
s
and
so
I've
put
together
some
developer
onboarding
documentation.
What
are
the
kinds
of
skills
that
we're
looking
for
for
fuse
development?
C
What
are
some
of
the
training
materials
lots
of
stuff,
pointing
right
out
to
PMP
so
kudos
for
putting
that
out
there
and
then
some
getting
started
guidance?
What
do
you
need
to
do
to
your
machine
and
I've
tried
to
minimize
this
as
much
as
possible?
So
if
you're
joining
the
fuse
team,
you're
gonna
be
working
on
a
fuse
effort
and
you're
gonna
be
working
on
a
SharePoint
framework
effort.
In
that
regard,
we
you
want
to
have
docker
installed.
C
Visual
Studio
code
is
recommended.
There's
a
couple
nice
extensions
here
that
help
with
that
and
then
there's
some
general
guidance
on
how
to
create
a
new
project.
How
did
it
work
with
an
existing
project,
and
so
the
idea
is
that
and
actually
let
me
take
you
through
the
scenario
here:
I
have
in
Visual
Studio
code.
You
see,
I
have
a
SharePoint
framework
solution.
That's
up
currently
and
right
now,
if
I
were
to
do
I
can
npm
version.
C
This
is
my
machine,
so
I've
got
5.6
installed
globally,
and
so
you
can
look
at
the
node
version,
8,
9,
4
and
so
on.
So
if
I
do
NPM
and
I
forget
the
commands
here,
gee
depth
equals
0.
I
think
this
should
show
what's
installed
globally
on
my
machine.
I
wish
in
this
case,
is
nothing
so
I
was
looking
inside
the
local
directory
globally.
I
have
nothing
installed
locally
in
this
directory.
I
do
have
those
versions
of
those
things
installed.
C
However,
I
do
have
a
docker
image
that
I
can
connect
to
a
docker
container
that
I
can
run,
and
so
what
I've
done
for
catapult
is?
We've
got
a
docker
hub
repository
out
here,
where
I
have
a
few
different
images
and
we've
we
sat
down.
We
talked
about
naming
conventions
and
kind
of
thought.
Well,
the
most
important
part
of
what
we're
going
to
put
into
our
docker
image
is
the
SharePoint
framework
generator.
C
We
also
now
have
a
one-for-one
a,
and
it
tells
you
which
versions
of
which
things
are
installed,
shows
you
the
docker
file.
I,
don't
worry
about
putting
the
docker
files
in
source
control
because
you
run
them.
You
build
the
image
it's
in
the
hub
and
then
that's
where
it's
maintained.
Don't
really
need
to
source
control,
the
the
docker
files
they're
pretty
short,
and
then
we've
got
one
for
1b,
in
which
case
I
do
have
an
issue
where
the
SharePoint
workbench
appears
to
be
failing
to
load.
C
The
only
difference
here,
I
believe
is
the
node
was
upgraded
at
894.
Everything
else
is
the
same,
and
then
a
recent
node
released
to
810
has
that
same
issue,
at
least
in
my
testing
in
these,
in
these
images.
So
what's
nice
is
if
you're
a
developer
and
you
go
through
the
onboarding
process
to
join
our
team
and
we've
got
a
two-week
sprints,
so
it's
Monday,
we've
done
our
planning,
and
now
we
know
what
our
tasks
are.
C
I
now
need
to
work
on
this
Microsoft
teams,
SharePoint
framework
webpart
well
I,
can
go
through
the
onboarding,
get
my
machine
set
up,
pull
down
the
latest
code
from
V
STS
and
then
run
the
command,
and
in
this
case
the
path
that
I
have
that
I
need
matches
what's
actually
in
here.
But
this
way
this
would
need
to
change
essentially
but
I'm,
using
the
one
for
one.
A
container
and
I've
already
pulled
the
gown
and
everything.
So
it's
speedy
and
everything
and
then
I
can
just
do
a
gulp
serve.
If
this
is.
C
This
was
the
very
first
time
I
were
doing
this
as
a
new
developer.
I
would
start
with
that.
Pull
down
the
image
wait
for
that
to
download
get
running
as
a
container
once
in
the
container
I
would
want
to
run
npm
install
to
pull
down
the
node
modules
and
everything,
and
then
once
I've
done
that,
though,
it's
a
gulp
serve
in
this
case,
because
it
is
an
existing
solution
with
an
existing
web
part.
So
we
can
actually
come
out
here
and
fire
up
the
sharepoint
workbench
and,
in
this
case,
pretty
simple.
C
It's
Microsoft
team's
web
parties
in
the
beta
endpoint
from
the
graph
API
that
just
pulls
down
and
shows
you
the
teams
that
you're
a
member
of
in
this
case
for
my
user
account
in
this
case.
So
pretty
simplistic
but
I
can
work
on
this.
I
can
work
on
this
web
part
now
make
any
changes
that
I
want
to
make,
and
let's
not
do
anything
significant,
of
course,
we'll
just
throw
in
a
comment
in
a
comment:
save
that
it
will
rebuild
and
do
its
thing
and
it's
the
normal
docker
process.
C
But
when
I'm
all
said
and
done,
I
can
stop
the
server
thanks
it.
The
container
and
my
files,
of
course,
are
persisted
locally.
So
when
I
go
to
my
git
I
can
see
the
one
change.
That's
out
here
on
this
item.
I
can
add
the
comments
stage.
It
committed
push
it
out
to
the
team
repo
and
then
another
developer
tomorrow
can
go
through
the
same
process
and
they
don't
have
to
install
anything
on
their
machine.
They
don't
have
to
worry
about
and
Visual
Studio
code.
C
They
don't
have
to
worry
about
which
version
of
node
or
NPM
or
gulp
or
yell,
or
the
Microsoft
SharePoint
generator,
and
so
on.
So
it's
much
cleaner
and
for
me,
as
the
person
who
manages
the
developers
coming
on,
you
can
imagine
if
there
was,
if
I
had
a
developer
coming
and
you
had
a
different
version
of
node
than
we
use
that
can
cause
a
problem
or
gulp
or
what
have
you?
C
So
all
these
different
versions
of
all
these
different
tools
are
can
be
problematic,
and
so
that's
kind
of
what
I'm
trying
to
avoid
is
give
the
developers
joining
the
team
a
consistently
similar
environment.
So
when
developer
a
writes,
their
ode
developer,
B
can
use
it
without
conflicts,
and
that's
really
the
demo.
A
Great
stuff,
thank
you.
Eric
and
I'm
gonna
jump
back
to
the
slides
jump
back
to
the
slides,
and
so
that's
really
great
stuff,
I
think
there's
a
few
questions
for
you
out
there
in
the
chat
window.
If
you
want
to
have
a
look
through
those,
but
this
is
a
using.
This
kind
of
a
pattern
is
really
great,
as
Eric
was
talking
about
on
bigger
teams
or
where
you
need
to
support
lots
of
different
environments
for
your
customers.
A
D
Cool,
so
thanks
thanks
Patrick,
so
I'm
what
a
man
one
day,
I
work
for
a
company
called
contacted
code
base
out
in
London
UK
and
today
we're
going
to
see
how
to
use
the
new
AAT,
HTTP
client
introduced
in
chevron
framework.
One
point
four
point:
one
to
actually
call
out
and
iet
secured
as
your
function.
Now.
The
main
difference
here
is
within
the
co
function.
We
would
be
able
to
have
the
context
of
the
current
user,
or
rather,
we
would
know
which
user
would
have
has
made
the
call.
D
There's
your
function
now
to
get
that
working.
We
need
to
do
a
couple
of
set
up
actions.
We'll
have
to
do
some
steps
in
a
zero,
we'll
have
to
build
the
SharePoint
framework
web
part.
So
that
would
take
a
lot
of
time.
So
I'm
just
going
to
walk,
walk,
do
a
walk
through
so
the
stuff
I've
already
got
set
up
over
here.
So,
let's,
let's
quickly
demo,
what
the
end
results
would
result
would
be.
D
So
that
would
be
this
shape
on
framework
web
part,
which
is
getting
some
details
about
the
currently
logged
in
user,
and
these
details
are
coming
from
an
SEO
function.
So
let's
see
how
to
achieve
that,
the
first,
the
first
step.
What
we
need
to
do
is
have
an
azure
ad,
a
prostrations
setup,
so
we
go
to
0
ad,
create
a
new
app
registration.
We
don't
need
to
do
anything
special
here
by
default.
The
app
registration
has
the
permission
on
windows
is
zero
Active
Directory,
it's
just
sign
in
and
radius
our
profile.
D
That's
the
only
thing
we
want
to
do
right
now.
We
don't
want
any
any
other
permissions.
We
only
just
want
to
sign
in
based
on
the
current
user
and
so
that,
just
so
that
all
users
don't
get
the
consent
prompt.
We
can
grant
permissions
as
an
admin
on
behalf
of
all
the
users,
so
once
the
app
registration
is
set
up,
will
click
on
grant
permissions
and
say
yes
on
behalf
of
all
the
users?
Now,
since
I've
already
done
that
I'm
not
going
to
do
that
again,
we
don't
need
to
do
anything.
D
Just
need
an
app
registration.
Maybe
note
the
client
ID
of
the
app
registration
as
we
will
be
using
it
later.
The
next
step
is
to
actually
setup
the
0
as
your
function.
I
won't
go
into
the
details
of
actually
creating
there's
your
function,
I'll
just
point
out
some
of
the
important
steps
we
need
to
do
so
once
the
function
app
is
created,
you
need
to
go
into
the
authentication
and
authorization
section
turn
on
the
app
service
authentication
in
the
action
to
take.
When
request
is
not
authenticated.
D
We'll
set
up
the
login
with
Azure
Active
Directory
authentication
provider
would
be
Azure
ad
and
in
the
Advanced
section,
we'll
actually
paste
the
client
ID
of
the
app
registration
we
created
earlier
once.
This
is
so
that
whenever
any
function
which
lives
in
the
function
app
needs
authentication,
it
will
use
this
particular
app
registration
for
authentication.
So
after
after
doing
that,
we
don't
need
to
set
up
any
client
secret
or
anything
right
now.
Everything
will
be
handled
by
the
SharePoint
framework.
So
once
this
this
is
set
up.
We
just
need
to
set
up
the
course.
D
D
That's
that's
it.
Basically,
in
terms
of
setting
up
that
is
your
function.
The
next
step
would
be
to
actually
write
the
code
for
the
function
now,
in
this
case,
I
have
created
us
I've
used
visual
studio
to
create
a
precompiled
dotnet
function
and
there's
not
a
lot
going
on
here.
I'm,
just
creating
a
dictionary.
I
am
adding
a
first
item
to
the
dictionary
to
just
show
that
whenever
the
jason
will
be
returned
from
there's
a
function
to
the
SharePoint
framework
web
part,
if
it
will,
it
will
contain
this
particular
key
and
value.
D
It
will
know
that
this
is
the
result
being
returned
from
as
a
function
and
then
whatever
are
the
current
claims,
or
rather
the
current
context
of
the
user
will
just
put
that
in
the
dictionary
and
then
return
return.
The
dictionary
as
it
is
when
there's
an
object
back
to
the
calling
calling
code.
Another
thing
is
the
individual
function.
Authorization
will
be
anonymous
since
we
are
setting
the
authentication
on
the
function
app.
We
don't
need
to
set
up
the
authentication
on
the
individual
function
basis
right.
D
So
that's
that's
it
in
terms
of
as
your
function
code,
it
says
we'll
need
to
obviously
publish
this
code
in
to
the
function
app
and
which
I
have
already
done
over
here.
So
you
can
see
that
the
current
user
function
is
is
listed
and
then
I
can
I
can
start
calling
it
just
to
kind
of
make
sure
that
this
function
is
Haidee,
secured
I
will
try
to
open
it
up
in
the
browser
and
then
I'll
be
redirected
to
a
login
screen,
just
to
kind
of
prove
that
this
indeed
the
function
has
AE
security.
D
Now,
that's
it
in
terms
of
the
zero
side
of
things
on
the
SharePoint
framework
side
of
things.
This
is
is
created,
Chevonne
framework
webpart
with
version.
One
point,
four
point:
one:
that's
the
latest
version
I
haven't
used
any
JavaScript
framework
and
there's
no
react.
There's
no
one
knockout.
This
is
just
a
step.
D
One
framework,
where
part,
with
no
JavaScript
framework,
just
to
kind
of
keep
things
simple
and
not
to
interfere
with
what
we
want
to
show
once
you
create
the
SharePoint
framework
web
part
in
the
package
solution,
Jason
will
have
to
add
this
Web
API
permission
requests
property.
This
is
so
that
SharePoint
knows,
or
rather
the
platform
knows
that
the
SPF
X
solution
is
going
to
request
permissions
on
this
particular
approaches.
D
Tration
and
the
permission
requested
will
be
the
user
impersonations,
which
means
that
the
SharePoint
framework
web
part
will
be
able
to
make
calls
on
behalf
of
the
currency
logged
in
user.
So
this
part
is
pretty
important
and
it
is.
It
was
made
available
as
part
of
the
one
point
four
point:
one
version
of
the
generator
shape
one
form
of
generator
in
terms
of
the
web
part
itself.
As
I
said
earlier.
There's
no
react.
D
There's
no,
no
fancy
cool
stuff;
it
is
just
the
NAD
HTTP
client,
which
is
which
has
been
imported
from
the
Microsoft
HP
HTTP
package
will
create
an
object
of
the
ad
HTTP
client
by
passing
in
the
service
scope
and
the
client
ID
of
the
average
istration.
Once
the
object
is
created,
we
will
use
the
custom,
API
client
or
get
method
to
actually
make
a
call
to
the
URL
of
our
as
your
function.
D
It
is
an
HTTP
triggered
function,
so
we'll
be
able
to
call
it
like
this,
and
air
will
pass
in
the
default
options
in
terms
of
the
configurations
now,
as
we
have
said
that
once
thought,
Jason
is
returned
back
from
from
the
function,
we'll
just
put
it
in
an
HTML
table
and
then
show
it
show
it
to
the
user.
This
is
just
for
demo
purposes,
all
right.
So
after
all,
after
this
stage,
we'll
have
to
do
a
gulp,
build
gall
bundle
and
package
solution.
D
If
you
are
running
it
in
debug
mode,
you'll
have
to
do
a
gulp
serve
in
this
case,
I've
already
packaged
it
up
for
for
production
and
then
deployed
it
to
a
tenant,
so
I've
already
run
so
that
kind
of
gives
me
in
this
SharePoint
folder.
That
gives
me
an
SP
pkg
file,
which
I
will
upload
in
in
the
App
Catalog.
So
once
I
upload,
the
file
in
apke
in
the
App
Catalog
I'll
get
a
kind
of
a
a
pop
up
which
will
kind
of
show
me
what
are
the?
What
is
the
scope
of
the
chip?
D
One
framework
solution
so
since
I've
made
it
a
tenon
scope,
I'll
have
this
checkbox
since
I
have
packaged
it
up
for
production
and
said
that
I
want
to
include
the
client
assets.
All
the
JavaScript
and
CSS
files
will
come
from
the
app
catalog
and
we
also
have
this.
We
also
have
this
text
here
which
says
that
this
kind
of
package
request
special
permissions.
So
please
go
to
the
API
management
page
and
approve
those
as
an
admin.
So
the
new
API
management
page
is
in
the
new
SharePoint
framework.
D
Sorry
SharePoint,
Online
admin
Center
on
the
API
management
and
I
would
see
that
my
app
registration
and
the
permission
I
requested
in
the
package
solution.
This
particular
thing
over
here
is
is
presented
to
me
as
a
pending
approval.
Now
I
will
click
on
it
and
I
will
approve
the
permission
as
an
admin
which
will
then
allow
the
user
to
add
the
web
part
to
the
to
the
page
and
basically
allow
making
it
calls.
D
So
I've
already
done
all
of
that
here
and
then,
as
a
result,
we
can
see
that
as
your
function
is
returning
the
claims
of
the
current
user
and
will
also
switch
to
another
user
just
to
kind
of
prove
that
this
is
all
returning
based
on
the
currently
logged
in
you.
So
this
is
another
user,
and
that
is
returning
the
claims
of
of
his
account
quickly.
I
will
just
have
a
look
at
the
dev
tools.
D
D
So
if
I
just
copy
that
into
and
try
to
decode
it,
you
can
see
that
all
the
values
of
the
current
user
are
sent
along
to
the
call.
So
so
this
way
we
can
have
a
SharePoint
framework
web
part,
which
makes
called
an
SEO
function
and
then
the
context
which
you
get
in
then
SEO
function
is
from
for
the
current
user,
who
made
the
call,
but
this
possibility
opens
up
a
lot
of
opportunities
to
talk
to
third-party
services
to
any
party
api's
on
behalf
of
the
currently
logged
in
user
in
SharePoint.
D
Now,
since
I
am
since
I'm
already
on
this
page,
I
didn't
get
the
pop-up
window,
but
if
I
was
to
open
up
a
new
window,
this
pop-up
would
show
up,
I'll
have
to
enable
the
pop-up,
and
then
the
authentication
would
go
ahead
and
take
place.
So
this
is
not
according
to
me.
This
is
not
the
ideal
way,
but
I
guess
a
work
is
being
done
there
to
kind
of
see
what
can
be
improved
there.
So
that's
that's
the
quick
kind
of
walkthrough
of
what
I
wanted
to
cover.
D
B
So
this
one
here
I'm
just
going
to
jump
onto
things
so,
for
you
had
a
quake
blog
post
on
this
one.
We
will
have
actually
a
webcast
coming
out
on
next
Monday
around
this
topic
as
well,
and
we
are
currently
updating
on
documentation
to
include
exact
details
for
calling
securely
third-party
web
api
using
the
new
one
point:
four
point:
one
version
of
SharePoint
framework
now
and
maybe
at
one
point
to
note
here
and
I-
think
we
have
sir
cake
and
actually
start
sharing
on
various
screen,
but
maybe
to
notice
this
one
done.
B
This
is
really
the
whole
the
krail
of
sharepoint
online
development,
at
least
from
my
perspective,
because
now,
if
you
can
securely
call
an
api
hosted
in
assure
and
and
we
can
access
tokens
and
and
all
of
that,
based
on
the
user,
you
have
all
anything
is
open,
yeah,
the
old
possibilities,
but
sorry
in
sure
is
the
possibilities
for
you
as
well.
So
you
can
easily
access
lob
data
from
on-premises.
You
can
last
a
lo
be
data
from
a
sure
you
can
do
whatever
that's
needed.
B
But
thank
you
borrow
money
for
that.
One
really
really
great
stuff-
and
I
share
function.
No
doubt
is
the
probably
the
easiest
way
to
build
to
custom
eight,
the
icing
in
sharepoint
online,
but
let's,
let's
search
it
to
do
the
final
demo,
section.
Sorry
Patrick
you
let
close
up.
That's
needed
to
drop
I
want
that
one.
B
E
Everyone,
my
name,
is
Sergey,
so
give
I'm
Sharon
developer
boroughs
by
Microsoft.
Ndb
me
I,
want
to
show
you
how
you
can
utilize
Visual
Studio
code
for
tasting
your
first
guy
SharePoint
rested.
I
am
leaving
graphic
there.
I
bet,
you
know
about
postman.
Chrome
extension
postman
is
a
great
tool
actually
for
twisting
wearers
of
Hippias,
including
SharePoint.
E
However,
you
probably
don't
know
that
Google
deprecated
Chrome
apps,
which
means
that
in
the
nearest
future
posting
up
will
stop
bragging
and
you
will
have
to
use
stand-alone
postman
desktop
application.
This
is
near
this
standalone
application.
I
would
say,
has
some
kind
of
unclear
story
about
managing
and
intercepting
cookies
from
Google
Chrome.
It
has
cookie
manager.
However,
it
can't
intercept
cookie
out
of
the
box
from
chrome.
You
have
to
copy
them
manually,
which
is
sometimes
you
know
pretty
inconvenient
anyway.
E
You
might
I
want
to
show
you
how
you
can
utilize
Visual
Studio
code
for
sending
and
for
tasting
your
REST
API
couldn't
share
pointers
today.
For
that
purpose,
you
should
install
an
extension
called
Aris
client.
You
can
see
it
right
there.
E
After
installing
you,
you
should
create
a
file
with
dot,
rest
or
dot,
HTTP
extension
and
I'm
going
to
show
you
three
different
samples,
starting
from
the
easiest
one.
So
I've
prepared
a
few
requests
and
it
is
my
simple
go
first
file
in
order
to
to
sound
sound
the
request,
you
can
write
it
such
a
way,
so
it's
very
simple
just
get
here
on
URL
some
headers
and
that's
it
all.
E
Requests
are
separated
with
this
pretty
fancy
commands
syntax
I'm,
going
to
run
my
first
request,
my
SharePoint
Online
tenant,
let's
drive
and,
of
course,
I
received
Excel
denial,
because
I
haven't
provided
an
authentication
data
right.
How
to
do
that.
It
can
be
done
pretty
quickly.
We
can
open
Google
Chrome,
open
our
dev
tools
and
go
to
application.
Tab
find
cookie
section
select
our
cookies
and
I
can
just
copy
past.
My
fear
of
cooking,
like
this
one
fit
out
equal
to
two.
The
values
in
the
colon
and
I
need
30
of
a
kookn
like
this
one.
E
This
is
special
syntax
for
arrival
in
site
and
authorized
files
and
I'm
going
to
use
this
variable
right
here.
So
I
am
attaching
my
cookie
hideth
to
my
request,
and
this
request
should
be
authenticated.
Now,
let's
have
let's
try
it
and
you
see
received
my
web
information
if
you
want
to
perform
a
post
request.
Of
course
you
have
to
attach
request,
digest
to
your
request
and
you
should
required
at
least
one
in
case.
If
you
are
using
cookie
authentication,
this
can
be
done
also
pretty
easily.
E
Let's
send
post
request
to
context
info
I
received
for
digest.
I
just
cook
in
this
register
into
my
variable
indigestible
and
and
I
can
send
post
request
to
weather
point
and,
for
example,
I'm
updating
my
web
title.
Let's
try,
it
I
receive
no
response.
Let's
refresh
the
page.
I
will
see
my
new
title,
so
this
was
the
first
small
example.
Next
one
involves
authentication
on
the
fly.
E
Actually,
this
feature
was
introduced
recently
by
a
guy
from
Microsoft.
His
name
is
Michael.
When
I
can,
probably
you
guys
know
him,
he
did
a
great
addition.
I
should
and
I
want
to
say
thank
you
to
Michael,
because
he
did
a
great
work
with
his
addition.
You
can
use
ever
Active,
Directory
authentication
in
the
thirsty
or
SharePoint
or
graffiti
is
porridge
with
any
other
of
his
ApS.
For
that
purpose,
you
can
see.
I
have
additional
hidden
here,
called
authorization
and
there's
a
special
special
environmental
variable
called
ADA
token.
E
You
need
to
pass
it
and
you
need
also
to
specify
your
clout
and
using
public
of
his
crowd.
There
Elsa
the
defeated,
still
errors
at
fault
for
Germany,
for
example
China
and
the
third
parameter
is
my
channel
fading.
If
we
click
send
request,
it
works.
Okay.
Let
me
just
quickly
clear
my
cache
clear
for
the
total
cache
and,
let's
click
once
again
now
we're
asking
for
for
the
credentials
and
it
in
a
nutshell.
It
uses
something
called
device
Logan,
so
I
should
continue.
Select
my
logged
in
user.
E
Post
request
works
almost
exactly
the
same
like
in
the
previous
example.
However,
when
this
this
time
you
shouldn't
provide
any
requests
barest
because
you
are
using
v-ray
tokens
and
of
authorization.
So
this
is
how
post
request
looks
like
it
is
pretty
easy.
You
can
send
request
and
we
can
observe
our
newer
title
here,
so
it
is
updated
and
you
can
also
test
your
graph
API.
They
have
very
small
sample
with
graph
here.
E
There
is
one
difference
that
I
am
using
and
this
additional
parameter
called
you
because
previously
I
have
created
access
token
for
my
SharePoint
resource
ID.
However,
this
time
I
need
another
access,
token
for
graffiti
graffiti
and
ref
resource.
That
is
why
I
need
to
issue
a
new
token
with
this
additional
parameter.
So
if
I
click
send
request,
it.
E
E
That's
it
for
this
second
part
and
the
last
part,
the
last
option
I'm
going
to
show
probably
the
most
difficult
in
setup
team.
However,
this
option
a
bit
more
flexible
for
this
option
to
work.
You
should
install
another
extension
called
called
SP.
Rest
client
like
this
one
I,
am
the
author
of
this
extension
and
this
extension,
that's
a
new
feature.
Actually
support
for
SharePoint
to
rest,
client
I've
tried
to
push
a
pull
request
to
the
rest
client
repository.
E
However,
it's
a
period
that
my
changes
introduced,
some
kind
of
architecture,
challenges
which
is
difficult
to
resolve
and
before
the
conversation
with
the
owner,
the
owner,
core-shell
mouth
actually
I
want
to
say
thank
you
to
this
guy
as
well,
because
unity,
great
extension.
So
we
had
a
conversation
and
we
agreed
that
the
for
now,
the
only
way
to
move
forward
is
to
create
a
separate
extension.
If,
if
I
need
to
support
sure
to
plant
inside
res
quiet,
that
is
why
I
have
to
install
a
separate
extension
for
that
for
that
for
that
sample.
E
You
see,
I
have
a
few
variables
pre-configured,
for
example,
and
there
is
a
variable
called
deaftalent
in
this
variable.
You
should
specify
his
peak
of
arrival,
which
is
a
path
to
your
file
JSON
file
with
your
credentials,
data
if
I
open
this
file,
so
you
see
it
contains
client,
ID
and
client
secret
for
authenticating
inside
sharepoint
online.
I
have
also
on
premise
version
which,
which
is
credential
smile
on
premise
credentials.
E
E
You
can
send
your
st
edward's.
However,
you
need
to
change
environment
from
these
videos
to
the
code
to
match
your
sharepoint
site
URL.
For
example,
I
specified
for
dev
tenant
and
using
in
the
apps
tenant,
so
I
should
change
my
environment
to
dev
channel
right,
so
so
current
environment
is
def
channel.
Now
I
can
send
my
request.
E
Hello
received
information
about
current
web
from
from
SharePoint
in
the
apps.
The
same
way
I
can
Vincent
post
requests
and
I
can
also
send
a
question
while
on
parens
SharePoint,
our
own.
That
claims
to
do
so.
I
have
to
switch
my
an
environment
to
one
parens,
and
this
request
see
I
received
information
about
my
friends.
E
Res
gland
has
a
lot
of
different
settings
parameters,
different
things,
a
lot
of
documentation.
So
if
you
you
are
interested
in,
please
check
out
documentation
for
his
grand
for
his
first
client.
One
option
is
different
environmental
variables,
for
example,
given
and
specified
host
URL
parameter
in
your
vehicle
settings
like
I,
did,
for
example,
for
the
attendant
I
have
host
URL
pointed
to
my
SharePoint
Online
instance
for
on-premise.
I
have
host
URL
22,
my
on
premise
instance,
and
by
clicking
send
request
and
by
changing
actively
water
environment.
E
A
Great
stuff,
thank
you
Sergey.
It's
always
I
think
awesome
to
see
the
different
patterns
and
different
techniques
to
approach
these
things
and
to
really
dig
down
in
this
case
into
the
meat
of
the
rest
requests
and
what
might
be
coming
back
so
I'm
gonna,
try
and
jump
back
to
the
slides.
Well,
thank
everybody
for
sticking
with
us
a
little
bit
over
time,
but
I
think
it
was
great
to
get
all
those
demos
into
the
call
this
week.
A
If
you
do
have
wanna
do
a
demo,
please
get
in
touch
for
our
next
meeting,
which
will
be
March
29th.
For
this
call,
the
SharePoint
framework,
JavaScript
special
interest
group,
will
be
March
29th.
The
next
general
development
special
interest
group
will
be
on
March
22nd.
That's
next
Thursday!
So
just
want
to
thank
everybody
for
coming
to
the
call
appreciate
everybody's
involvement,
learn,
reuse
and
share.
Everybody
have
a
great
weekend
and
we'll
talk
soon.
Aye
aye,
aye.