►
Description
Recording of SPFx and JavaScript development in SharePoint Community Call from 29th of August. Topics include updates from SharePoint engineering on SPFx, latest on PnP JS Core, Office 365 CLI, Reusable SPFx controls and PnP SPFx Yeoman extension.
Detailed covered content from SharePoint Dev Blog at http://aka.ms/spdev-blog.
- Demo - Ramin Ahmadi (Content and Code) – @raminahmadi1986 - Override list experience with a custom web part – hacky way
- Demo - David Warner (Catapult) – @DavidWarnerII - SharePoint Library Components - Simultaneous Parallel development
Code demonstrated by Ramin is available from https://github.com/SharePoint/sp-dev-fx-extensions/tree/master/samples/react-command-form-settings. Please notice that this is NOT recommended patter and was demonstrated for learning purposes.
More details on SharePoint Framework library components is available from https://docs.microsoft.com/en-us/sharepoint/dev/spfx/library-component-overview
You can download an invite to this bi-weekly call from https://aka.ms/spdev-spfx-call.
You can find more details around the open-source and community work from http://aka.ms/sppnp
A
Welcome
everybody:
this
is
SharePoint
framework
and
JavaScript
special
interested.
This
is
the
bi-weekly
as
sync
for
this
community
code,
which
happens,
live
weekly
on
Thursdays
at
7:00
a.m.
Pacific
time,
and
typically,
this
call
is
actually
being
led
by
Patrick
Rodgers,
who
on
who's
unfortunately
had
a
thing
and
this
morning,
so
he
can't
actually
join
and
so
I
needed
to
step
in
not
a
massive
deal,
because
typically
I
would
have
a
six
and
in
this
call
as
well
now
on
the
agenda
of
today.
If
I
can
get
the
slides
moving
there
we
go.
A
We
have
a
quick
engineering
update
ownership
on
frameworks,
I'm
going
to
talk
about
a
few
things
which
seem
to
be
landing
on
my
SharePoint
framework
1.10
and
also
the
the
progress
around
and
that
money
general
will
also
have
updates
on
the
PM
peaches
office,
365
CLI
SPFs,
reusable
controls
and
DMB
yeoman
generator,
so
our
open
source
tooling
helping
you
to
be
more
productive
when
you're
doing
development
in
the
SharePoint
framework
or
in
the
sharepoint
online
world
in
general.
What
if
this
stuff
actually
is
more
for
sharepoint
online
rather
than
SharePoint
20:19,
because
sharepoint
2019?
A
Actually,
it's
quite
old
already,
which
you
might
not
think
like
that,
but
in
the
end
of
microsoft,
world
and
in
the
engineering
world,
it's
almost
one
and
a
half
years
old,
because
the
latest
and
greatest
is
always
on
SharePoint,
Online
and
then
Don
promises.
This
is
following
big
away
behind
of
SharePoint
Online
with
the
releases,
because
we
don't
control
your
server,
so
we
can
update
your
server
without
your
permissions.
So
that's
why
SharePoint
Online?
We
can
update
that's
and
that's
getting
a
new
version
in
every
single
week.
Think
about
that.
A
So
it
is
a
new
version
actually
getting
released
as
we
speak
in
on-premises
as
well
and
point
from
Gary
Shere
Khan
2019
is
agent
ancient
in
their
specs
terms.
That
is
true.
Unfortunately,
it
is
a
logistical
challenge
for
for
keeping
that
also
up-to-date,
and
we
understand
that
there's
a
growing
demand
for
potentially
making
updates
there,
but
let's
not
actually
concentrate
that
on
that
one.
Precisely
on
this
core,
we
can
talk
about
that
one.
Maybe
in
the
Q&A
section
more
now
we
will
have
two
different
call.
A
Demos
I
mean
of
Nadia
from
content
and
coach,
is
here,
he's
actually
showing
a
happy
way
and
to
override
list
experience
with
the
custom
web
part,
and
this
is
something
which
actually
I
intentionally
wanted
to
have
a
demo,
because
I
want
to
have
a
discussion
about
this
approach.
What
is
the
benefit
and
what
is
the
downside
of
that
approach,
because
people
might
be
doing
that
this
already?
We
are
also
looking
into
Native
artists,
box
ways
of
overriding
the
auditor
box,
least-experienced
potentially
with
the
web
part
and
that's
being
that's
work
which
being
led
by
checks.
A
Checks
is
one
of
the
PM's
in
my
team,
and
then
we
have
daily
toner
talking
about
SharePoint
library,
components
and
simultaneous
Perl
development,
often,
and
and
how
you
can
actually
do
that.
That's
a
really,
really
really
really
cool.
Looking
a
demos,
both
so
I'm,
pretty
sure
that
you
will
be
impressed
now.
I
didn't
introduce
myself
by
the
way
when
we
started.
So
my
name
is
like
this:
are
you
one
and
I'm
a
principal
program
manager
in
the
SharePoint
development
platform
team
or
one
try
shape
and
development
platform
team?
A
So
my
team
owns
everything
related
on
SharePoint
development,
API,
documentation,
SharePoint
framework
form
solutions,
feature
framework,
that's
all
on
my
table
as
well
or
our
team's
table,
so
pretty
wide
range
of
responsibilities
I've
been
around
for
a
long
time.
So
I.
If
you
have
any
questions
for
our
farm
solutions,
I
can
help
with
those
as
well.
Please
don't
use
them
anymore
now,
opportunities
to
participate
in
PMPs,
perfect
and
special
interest
group,
and
we
have
a
few
different
ways
of
being
part
of
this
community.
You
can
volunteer
to
do
a
demo.
A
We
aren't
actually
getting
a
lot
of
people
now
signing
up
for
the
demos
based
on
the
samples,
their
staff
meeting
or
based
on
their
own
center
samples
in
a
key
table
or
a
demo
with
demos,
something
which
they
did
for
their
customer
or
their
company,
which
then
unalloyed
to
share
as
a
code,
but
we
can
still
have
a
demo
of
that.
So
people
are
signing
up
for
those
demos.
You
can
definitely
do
demos
around
PHAs
office.
Traces
farcical
is
better
used
for
controls
than
yeoman
generator,
and
those
are
more
than
welcome.
A
All
of
the
demos
are
actually
recorded
as
part
of
this
video
and
they're
also
being
released
as
an
individual
videos
in
the
SharePoint
app
YouTube
channel
and
then
promote
it
with
our
social
media
attack.
So
if
you
want
to
have
more
visibility
for
yourself
or
your
company,
these
are
actually
create
opportunities
for
that.
So,
if
you're
in
VB,
you
need
to
get
more
additional
exposure
or
if
you
want
to
be
an
MVP,
it's
a
brilliant
opportunities
to
actually
gain
some
visibility
in
the
community.
A
You
can
definitely
contribute
and
github
repo
the
issue,
something
for
requests
to
help
with
issues
and
questions.
That's
definitely
also
allowed
as
well,
and
so
you
can
actually
help
other
people
in
the
issues
and
questions
as
well,
because
we
to
be
honest,
we
do
not
scale,
and
this
thing
is
crowing
out
of
hands,
and
so
we
definitely
would
need
help
more
and
more
from
the
community
to
help
each
others
as
well,
and
then
the
main
thing
always
remember.
Please
please,
please
give
us
feedback
if
something
is
missing
from
this
course.
A
If
we're
talking
too
much,
if
they're
talking
too
little,
if
we're
missing
some
irrelevant
things,
let
us
know
we
can
actually
fix
that
if
we
know
what's
actually
program,
so
don't
just
be
a
stranger
and
and
complain
somewhere
without
us.
Knowing
complain
in
a
way
that
we
know
so
we
can
improve
and
also
a
positive
feedback
is
definitely
welcome.
A
We
human
beings,
some
quite
bad
actually
on
that
one,
because
we
tend
to
under
always
react
on
negative
things
or
remember,
to
acknowledge
negative
things,
but
providing
positive
feedback
for
the
people
who
are
contributing,
definitely
welcome
as
well.
Now
we
have
three
different
main
assets
we
talked
about.
There
was
already
a
question
around
the
videos.
All
of
the
community
calls
are
getting
recorded.
They
are
in
the
AKMs
spdf
videos
at
rest,
or
you
can
do
aaww
youtube.com
slash,
sharepoint
EMP.
Either
way
you
will
land
on
the
same
location.
A
So
following
up
on
things
sooner
later,
something
is
gonna,
have
a
look
on
your
issue
and
then
we're
gonna
triage
that
internal
in
engineering
and
then
we're
gonna
address.
Hopefully
that
issue
as
fast
as
possible
also
take
community.
Like
mentioned
by
beau
Cameron.
There
say
a
lot
of
a
lot
of
information
already
in
the
tech
community
around
the
questions
and
answers
as
well.
So
don't
ignore
the
tech
community
locations
now
quick
updates
on
the
SharePoint
framework.
So
a
few
updates
on
this
side
of
the
house
from
the
SharePoint
Engineering.
A
A
This
is
the
latest
version
and
by
the
way,
just
to
clarify
that
one
because
it
seems
to
be
coming
up
all
the
time,
even
though
you
would
be
doing
development
of
SharePoint
2019
install
this
version
and
then,
as
part
of
the
creation
of
your
solution,
you
choose
the
target
environment
to
be
about
twenty
nineteen
plus
forward,
and
that
will
give
you
the
right
solution,
structure
to
write
versions
and
packages
and
everything
else.
And
then,
when
you
package
that
package
or
solution
it
will
work
without
an
issues
in
SharePoint
2019
now
shape.
A
One
point:
nine
point:
nine
one
is
now
out
like
mentioned
like
two
weeks
ago,
so
have
a
look
on
what's
available
library
components
is
now
g8,
so
that's
available,
and
today
we're
going
to
talk
about
what's
in
the
next
version
and
when
is
it
coming
out?
I
did
a
quick
calculation
earlier
today
for
internal
communications
that
we
have
had
already
fifteen
actual
releases,
a
SharePoint
frame
framework.
A
After
the
initial
release
back
in
February
2017,
that
is
actually
quite
big
number
and
we're
moving
more
and
more
to
this
monthly
really
a
cycle,
so
you
would
know
beforehand
when
the
new
version
is
coming
and
what's
coming
as
part
of
that
version
and
that's
gonna
then
increase
the
reliability
and
we
can
improve
our
internal
processes
based
on
that
as
well
now
before
I
go
here.
I
just
need
to
unmount
is
none
Chen's
comment
as
SB
2019
equals
or
is
greater
than
one
point
four
point:
zero,
which
is
true
and
not
true.
A
So
please,
when
you
create
anything
on
SharePoint,
2019,
install
SharePoint
framework,
one
point,
nine
point,
one
or
the
latest
version
and
then
create
the
solution
by
selecting
SharePoint
2019
forward
as
the
option
and
voila
you
will
have
the
right
version.
This
version
is
a
combination
of
multiple
things,
so
saying
that
it's
a
one
point
four
or
one
point
four
point:
one
isn't
technically
precise.
So
that's
why?
Please
use
always
the
latest
version
now
a
few
notes
on
the
usage.
A
If
you're
following
me
in
the
inter
Twitter
as
an
example,
you
notice
that
I
was
kind
of
okay
with
it.
I
was
super
excited
earlier
today,
because
we
poked
a
one,
pretty
unbelievable
limit,
which
you
can
actually
see
in
here,
but
I
can't
give
you
the
exact
number
so
on
the
left
side
use
its
per
user.
You
can
say
that
the
latest
weeks
we've
been
again
skyrocketing,
so
it
obviously
it
did
slowed
down
slightly
during
summer,
which
is
understandable
when
the
summer
is
in
the
northern
hemisphere.
A
A
So
we
we
jump
really
like
20
percent
already
from
the
early
August
or
ten
percent
in
early
August,
but
the
numbers
are
already
insanely
big
and
then
we
still
jump
ten
percent
in
one
month,
which
is
impressive
and
that's
the
left
side
of
the
of
the
of
the
charts
it
Procope
one
line
in
the
top.
It
did
probe
that
line
actually
Tuesday
Wednesday
this
week
already
and
if
the
growth
is
similar
in
future,
we
have
no
idea
where
the
limits
are.
This
is
really
interesting
to
see
how
the
growth
is
continuing.
Now.
A
The
reason
why
we
don't
give
you
an
exact
number
I
always
being
asked
is
that
if
I
would
give
you
a
number
which
is
28
now
you
would
ask
okay,
what
does
that
mean
and
that's
when
it
gets
complicated
and
the
way
we
calculate
usage
in
the
whole
history?
65
is
not
based
on
how
many
users
are
actually
in
a
day
doing
something
or
how
many
things
or
how
many
people
or
how
many
application?
How
many
tenants
something
is
happening,
there's
a
slightly
more
complicated
way,
how
we
calculate
that
as
a
standard
way.
A
Cross-Office
rate
is
defined
and
that's
the
balance
out,
let's
say,
exceptions
and
all
of
that
stuff.
So,
even
though
you
would
get
a
number
which
is
like
48
to
you,
it
wouldn't
tell
you
anything
and
that's
why
we
don't
want
to
actually
give
that
number
away
and
we
rather
show
you
a
chart
and
percentage
growth,
because
that
gives
you
an
indication
where
we
are
so.
But
it's
been
a
massive
right
and
it
seems
to
be,
and
I
was
quite
rocketing
again,
which
is
really
interesting.
A
Now
shipment
developer
wrote
a
few
things
which
are
updated
on
this
line
today,
so
SharePoint
1.9
came
out
in
August
the
next
version.
It's
one
point
ten.
It
is
now
coming
on
plan
to
come
out
on
September
and
again
everything
is
subject
to
change,
but
it's
good
that
you
have
some
visibility
on
things,
we're
looking
into
getting
to
one
point,
ten,
a
really
important
feature
of
which
is
and
the
capability
of
allocating
SharePoint
framework
extension
areas
during
the
UI
loading.
A
So
that
means
that
if
you
are
using
a
header
or
a
footer
or
in
future
other
elements
in
the
in
the
UI
they're,
not
jumping
or
moving
the
UI
UI
after
hour
as
part
of
the
loading.
So
basically
you
can
allocate
a
blocks
in
the
header
area,
which
is.
This
is
an
area
which
I'm
going
to
render
as
a
final
step
on
the
page,
rendering
and
it's
going
to
be
50
pixels
and
that
it's
going
to
be
allocated
there.
A
Evan
so
basically
say
hey
whenever
there's
a
a
new
items
or
changes
and
modifications
in
that
list
we
know-
and
so
I
can
rerender
myself
or
react
on
those
new
things
in
the
listing.
Libraries
on
the
on
that
side
or
another
sides
of
the
hospital
and
that
capability
can
now
go
to
GA.
Now
that
a
bi
capability
is
the
underlying
API
is
also
available.
A
So
that's
really
cool
as
well,
because
now,
quite
often
people
have
an
intranet
or
whatever
Bates
hanging
on
their
screen,
but
you
can
react
the
changes
behind
the
scenes
automatically,
so
you
can
really
easily
subscribe
to
day
sevens.
There
have
been
a
way
to
do
that
in
the
past
as
well,
but
that
typically
has
required
and
as
your
function
or
a
quite
complicated
implementation,
which
require
say
a
external
processor
is
running,
and
now
we're
heading
to
this,
where
you
can
really
easily
do
that
using
Tennessee
open
framework.
A
Now
all
that
topics
bubbling
under
office
audience,
which
open
frameworks
still
getting
done,
it
is
moving.
We
do
have
a
relatively
big
conference
coming
up
later
this
year,
which
we
might
or
might
not
know
something,
but
obviously
we'll
start
with
the
preview.
In
all
of
these
things,
content
security
policy
is
for
Chris
and
see
some
doesn't
standard.
There
is
movement
on
this
one.
A
We
are
in
progress
of
fixing
our
internal
build
processes
and
that's
gonna
then
enable
that
to
get
to
the
previous
preview
status
first
and
then
do
the
GA
store
story,
for
she
opens
the
framework
solution
that
is
getting
movement
as
well.
So
we're
really
running
to
trying
to
make
that
happen
as
well.
Additional
content
extensions
from
Warren
pages.
We
talked
about
that
on
in
SBC,
so
there
will
be
navigation
overrides
and
navigation.
A
The
loop
book
templates
are
really
around
making
cool-looking
demo
sites
available
for
you,
so
basically
making
sure
that
whatever
cool-looking
demo
sites
we
used
in
ignite
or
in
sessions
as
Microsoft
and
I'm
marketing,
that
kind
of
cool-looking
sites
are
available
for
you
as
well.
So
that's
going
to
help
on
and
then
you
to
maybe
even
start
your
internet
based
on
those
sites,
so
really
cool
stuff.
A
Now
Emma's
graph
user
insights,
the
following
sites
followed
sites,
API
is
coming
so
the
still
there
is
a
additional
set
of
insights
coming
and
now,
if
it's
specific
for
some
other
areas
on
Microsoft
graph,
I
do
not
know
because
I'm
from
a
onedrive
SharePoint
side
of
the
house,
but
I
know
that
followed
sites
is
moving
from
a
better
perspective
and
that
should
be
out
relatively
soon
as
well.
A
new
place
holders
are
coming.
I
can't
really
disclose
all
of
the
details
on
that,
but
in
the
SBAC
we
talked
about
navigation
overriding.
A
We
talked
about
navigation
note
overriding
using
an
extensions
and
those
are
being
looked
at
again
promised
an
ETA
for
those
either
BMP
TAS
quickly
in
here,
like
said,
Patrick,
isn't
unfortunately
Nicole
one
point
three
point:
five
was
released
in
August
16th,
mainly
issue
fixes
and
some
features
the
version
2.0
is
being
worked
on,
and
this
is
a
open
source
initiative
as
well.
So
right
now,
Julie
Turner
from
some
rocks
is
contributing
Simon
ourian
from
other
point
and
David
Warner
uncuttable
are
helping
around
the
coordination
of
that
work.
A
So
if
you're
interested
on
contributing
as
part
of
the
PMP
jsv
to
release
and
absolutely
reach
out
to
these
persons
or
Patrick
Rodgers,
but
it
is
progressing
and
looking
really
promising
as
well.
All
the
365
CLI
daresay
a
new
beta
version.
The
version
2.0
beta
available,
which
is
list
including
three
new
capabilities
listing
organizational
asset,
libraries,
retrieving
myself
craft
skin
extensions
and
enabling
and
disabling
flows
so
office.
A
365
CLI
is
a
command-line
tool
which
can
be
used
in
any
operating
system
in
the
world,
so
basically
Linux
or
Mac,
OS
or
Windows,
and
so
and
that's
really
the
key
story
why
it
exists.
It
started
as
a
project
by
Moloch
because
he
was
unable
to
connect
dearness
in
the
Apple
machine
without
starting
at
the
end,
which
had
a
windows
and
then
a
Windows
PowerShell,
but
CLI
has
been
extending
quite
significantly
after
that,
so
it
is
might
being
used
also
for,
for
example,
giving
you
insights
on
what
are
the
steps
to
upgrade
your
solution?
A
If
you
move
from
a
SharePoint
framework
version
previous
version
to
the
latest
version
to
see
a
like
they'll,
give
you
the
steps
to
make
that
happen,
so
really
really
really
great
tool
now
components,
not
a
massive
amount
here
progress.
We
do
have
a
quite
a
few
pending
community
PRS,
it's
been
a
vacation
period
for
Elio
who's.
Actually,
the
pro
project
lead
open-source
project
lead
for
this
one,
but
looking
into
getting
back
on
track
on
on
addressing
those
four
requests
and
making
everything
available
and
moving
forward.
So
that
should
happen
by
the
next
community
core.
A
You
just
check
and
drop
basically
or
use
the
code
to
get
the
control
into
your
web
part
and
move
it
just
magically
works
with
part
titles
and
I
placeholders,
and
everything
that
automatically
available
for
you
so
really
cool
stuff,
VFX
community
yeoman
generator,
which
is
the
generator
which
extend
storage
box,
yeoman
generator,
but
extends
not
with
the
new
options
and
capabilities
like
a
angular
and
as
part
of
the
1.9
release.
It
is
now
supporting
angular,
6
and
verse
7
and
that's
actually
pretty
cool.
A
It
also
has
a
native
typescript
support
for
2.9
3.0
3.1
3.2,
a
2
3
4
and
3
5,
so
you
can
actually
select
that's
part
of
the
yeoman
scaffolding,
which
version
do
you
wanna
target
and
the
tool
will
get
every
single
setting
in
right.
So
you
can
just
concentrate
on
development.
The
native
part
of
the
work
so
yeoman
generate
does
not
do
that.
It
doesn't
have
an
angular
support.
It
doesn't
have
a
view,
support
as
an
example,
so
really
really
really
not
create
extension,
and
it
is
using
the
dotter
to
box
under
the
hood.
A
So
it
extends
that
so
there's
a
no
risk
of
using
this.
Rather
than
2
out
of
the
box
1,
which
is
coming
from
the
Microsoft
engineer
so
and
it
looks
something
to
check
out
as
well,
but
that's
it
from
my
side
pretty
much
online,
what
I
was
planning
to
have
so
20
minutes
of
discussions
and
updating
it
up
where
we
are
heading
from
an
engineering
side
and
also
a
quick
update
on
the
open
source
projects
Ramin,
you
are
hopefully
in
the
call
right
we
didn't
double
check
on
before.
A
We
are
yes,
awesome,
you're
there,
so
I
think
it's
time
to
jump
on
your
screen
and
do
two
demos,
and
then
we
can
talk
about.
What's
the
challenge
of
the
of
the
demo,
what
you're
doing
as
well
and
I
want
to
call
out
before
Raman
actually
starts
this.
This
is
not
what
we
recommend
to
be
done
in
production,
but
I
think
it's
a
worthwhile
technology
and
a
pattern
to
talk
about
so
take
it
away
and-
and
let's
definitely
talk
about
what
we're
saying
in
the
screen
afterwards.
Thank.
B
You
sure
so
my
name
is
Romina
MIDI,
hello,
everybody
I'm
working
at
continent
code,
and
you
can
follow
me
on
Twitter,
github
or
my
black
and,
as
you
know,
the
idea
of
developing
custom
modern
form
is
one
of
the
top
three
user,
worse
ideas,
and
hopefully
we
will
be
able
to
have
them
in
the
near
future
and,
as
Risa
said,
is
not
recommended.
With
a
way
of
doing
this,
it
was
you
know,
I
was
really
curious.
B
How
I
can
you
know
have
something
similar,
so
I
can
redirect
more
forms
to
different
pages
and
basically
have
custom
forms
for
different
content
types.
So
the
only
way
to
achieve
that
was
you
know
using
a
hacky
way
that
that
I'll
use
jQuery
to
just
you
know,
having
custom
custom
code
and
pointing
them
to
on
click
function
of
some
elements
that
you
will
see
in
the
code.
B
So,
if
I
want
to
show
you
how
it
works,
this
is
the
lease
I
created,
and
this
is
the
common
view
sets
button
that
I
have
here
for
defining
our
custom
forms.
If
I
click
on
that,
it
shows
that
this
panel,
that
you
can
define
your
custom
forms
before
that
I'm
going
to
show
you
the
pages
that
I
created.
B
So
this
is
a
display
display
form
page
that
I
used
this
webpart
reactive
form
that
you
can
download
it
from
the
repository
it's
already
available,
and
also
we
have
similar
functionality
for
this
page
at
the
Edit
form
and
I
also
use
a
power
apps
web
part.
So
I
added
to
this
new
page
that
going
to
be
our
new
form.
B
So
here
you
can
select
your
content
type.
For
example,
web
part
I'm,
going
to
for
this
valet
form,
I
enable
it
first
and
I'm
going
to
use
this
URL
I'm
going
to
say
new
tab,
and
also
there
are
some
tokens
available,
so
you
can
pass
it
as
a
query
string
parameters,
for
example,
I'm
going
to
say,
item
ID
equal
to
one
of
this
token,
which
will
be
item
ID,
and
you
can
save
this
I'm
going
to
have
similar
configuration
for
the
Edit
forms.
B
B
B
B
B
B
B
B
We
click
on
one
of
these
items
that
has
a
webpart
content
type
I
click
on
edit.
It
just
redirect
form-
and
here
you
can
see
that
item
ID
passed.
It
is
page
at
the
query
string
and
these
are
the
fields
that
is
being
filled
in
the
in
this
paper
and
also,
if
I
click
on
each
item,
you're
going
to
open
the
display
form
in
a
in
a
really
new
new
page,
but
it
doesn't
affect
the
other
content
arts,
for
example.
We
didn't
touch
the
extension
content
type.
B
B
That
I
want
to
show
you
the
first
one
is
the
assets
that
I
have
here.
This
is
a
leased
instance
that
going
to
keep
all
the
settings
for
each
lease,
so
you
can
use
these
commented
comment.
Visits
in
you
know
different
lease
and
keep
all
the
settings
for
that
list
and
when
you
add
this
app
to
a
site
collection
going
to
be
created
automatically
this
list
and
also
we
have
this
Settings
panel.
B
So
this
is
a
fabric
UI
panels
that
is
responsible
for
adding
or
updating
these
configurations
to
that
list
that
I
mentioned
before,
and
we
also
have
a
list
service
class
that
uses,
pin
PJs
to
do
the
updates
or
adding
the
items
or
getting
the
content
Ives
from
the
list
to
you.
So
you
can,
you
know,
select
them
from
the
panel,
and
here
is
the
code
that
I
just
mentioned
before
and,
as
you
know,
as
I
mentioned
before
and
also
whistle
mentioned,
this
is
a
really
hacky
way.
B
So,
as
you
can
see,
I
just
use
jQuery
to
find
Killick
event
to
each
button,
for
example
ID
to
open
or
new
buttons.
So
we
can
redirect
redirect
them
to
the
pages
that
we
define
in
the
settings
panel.
So
here
in
the
redirect,
we
just
check
if
it's
it
needs
to
be
open
in
a
new
page
or
just
the
current
page
current
window.
A
A
And
basically,
what
running
then
did
here
is
that
he
implemented
a
in
extension,
which
we
can
use
in
a
list
level
to
configure
where,
where
the
user
is
freed,
that
again,
if
you
click
on
the
item
or
a
edit
an
item,
and
then
a
new
page
is
where
we
have
a
web
part
which
is
reacting
on
those
things
what's
happening
now
the
challenge
of
actually
making
this.
This
way
it
does
work,
but
it's
not
currently
that
it
will
work
tomorrow
and
it's
the
reason
for
that.
A
A
So
you
basically
and
modify
the
Dom
structure
of
the
page,
but
the
challenge
of
doing
that
is
really
the
fact
that
when
we
change
or
release
a
new
version
of
the
list
and
libraries
and
we
haven't
actually
given
our
developers
and
customers
and
partners,
an
agreement
that
our
UI
would
be
an
API,
because
it
is
because
we
cannot
guarantee
that
the
Dom
structure
and
the
dome
path
which
is
used
in
a
jQuery
for
matching
the
edit
button
or
as
an
example,
would
be
exactly
the
same
in
the
new
version
or
to
listen.
Libraries.
A
And
we
can't
eliminate
that
at
this
point
and
that's
why
the
sample
also
is
saying
clearly
on
the
on
the
readme
that
you
should
not
do
this
in
production.
Now,
that's
and
again
that
we
used
to
do
that
in
a
classic
SharePoint.
You
know
by
modifying
the
the
let's
say:
sub,
create
sub
site
creation
or
links
and
all
of
that
stuff.
And
yes,
there
are
solutions
in
the
production
for
doing
that.
But
the
challenge
of
that
on
doing
this.
A
It
is
really
the
fact
that
we
don't
know
if
it's
going
to
work
tomorrow
for
SharePoint
framework
extensions,
which
are
the
header
and
footer,
and
the
ListView
command
sets
and
x10
filled
with
customizers.
We
actually
currently
that
we
countless
of
the
UI
modifications
what
we
do.
Those
extensions
will
work
and
this
shows
a
requirement
for
us
to
actually
implement
a
custom
list
and
custom
view.
Custom,
editing,
experience
also
for
lists
and
like
tremendous
showing
as
well
do
you
have
Roman
by
the
way
the
the
user
was
entries
number.
A
B
A
Yes,
yes,
okay,
so
you
can
easily
find
it
using
Bing
or
Google
by
using
it
to
title
so.
But
this
is
now
number
three
in
the
users
interest,
and
this
is
really
around
the
fact
that,
yes,
you
can
use
power,
apps
and
again
as
flow
to
modify
up
our
apps
to
modify
the
user
experience.
But
the
challenge
of
doing
that
is
that
it's
again
a
new
development
environment
and
then
it
has
licensing
implications.
A
If
you
don't
like
those
things,
you
would
like
to
just
override
the
least-experienced
by
providing
a
bit
part
which
will
take
care
of
the
editing
and
displaying
and
and
new
form,
and
so
be
looking
into
that
it
is
actually
highly.
It
seems
to
be
that
it's
quite
likely
that
we
will
make
that
happen,
but
in
the
way
that
you
override
the
hold
list
experience
so
not
bits
and
pieces
of
the
least-experienced
out
at
the
box
one
rather,
you
truly
are
able
to
have
a
bit
part.
We
just
say
that
hey.
A
This
is
a
taking
ownership
of
this
list
and
then
the
web
part
will
have
an
indication
is
an
edit
on
your
display
functionality.
That
sounds
probably
what
it
should
be
and
I'm
looking
forward
on
on
on
making
that
happen
sooner
or
later
again,
I
can't
provide
any
any
ETA
on
the
insides
when
and
maybe
I
can't
even
promise
to
remove
make
that
happen,
but
it
is
being
discussed
all
the
time
perfect
couch,
but
until
10
still,
if
possible,
don't
do
what
Roman
is
doing
in
this
demo.
A
But
then
again,
if
your
customer,
this
is
one
of
those
things
where
when
I
was
a
consultant
and
then
you
need
to
figure
out
and
you
need
to
get
clever
if
your
customer
is
saying
that
well,
if
I
can't
make
this
happen,
I
will
go
to
another
provider
and
I
will
go
to
another
platform.
Well,
that's
not
also
what
we
want.
So,
yes,
it's
a
hacky
way.
A
Definitely
not
a
recommended
way,
a
definite
no-no,
room
term,
long,
a
way
how
it
should
be
done,
but
maybe
every
now
and
then
we
need
to
make
compromises
the
world.
Unfortunately,
it's
not
black
and
white.
So
again,
not
recommending
making
this
happen
should
not
do
this
in
production,
but
we
can't
poke
you
for
doing
this
from
the
production.
If
that
is
so,
that's
one
of
the
reasons
why
we
need
to
provide
a
similar
capability
out
of
the
box
as
well,
cute
and
I-
think
that's
it
forum
in
from
your
side.
A
A
C
Okay,
all
right,
thanks
for
let
me
demo
today.
My
name
is
David
Warner
I'm,
an
MVP
work
for
catapult
systems,
do
a
lot
of
logging
and
blogging
and
love
working
with
community
so
reach
out.
If
you
have
any
questions
or
just
want
to
collaborate
today,
I
was
going
to
demo
on
SharePoint
library,
components,
specifically
a
technique
that
I
call
simultaneous
parallel
development.
C
So
what
our
library
components?
It
is
a
SharePoint
framework
solution,
as
you
can
see
here
that
allows
us
to
include
all
kinds
of
functionality
and
it's
stuff
that
might
otherwise
be
included
in
the
web
part
or
an
external
resource,
and
our
web
parts
can
then
connect
to
it
or
our
extensions
can
connect
to
it,
and
it
will
only
load
once
on
a
page
right.
C
So
what
exactly
is
simultaneous
parallel
development
and
how
can
it
be
a
so
obviously
you
gulps
serve
when
you're
doing
SPF
X
development.
That
does
not
change
here.
You
will
do
that
with
both
your
library
component
and
your
web
part
of
your
extension,
but
they
both
will,
by
default
spin
up
a
server
with
localhost
four
three,
two
one,
so
there's
a
collision
that
could
happen
there.
So
we
want
to
ensure
there's
no
local
host
port
collisions
between
your
solutions
and
then,
of
course,
the
connection
to
our
library
component
is
based
on
the
NPM
link
right.
C
So
when
we
change
the
port
for
our
library
component,
you
may
be
thinking
wait
a
second.
How
is
the
workbench
or
any
other
component
going
to
find
it?
We're
used
to
working
through
that
four
three,
two
one
connection,
but
it's
the
NPM
link
in
the
magic
pine
that
that
makes
all
this
work
and
allows
us
to
change
that
port
and
everything
still
function.
As
expected,
we'll
see
a
demo
of
that,
of
course,
and
all
include
some
links
if
you're
not
familiar
with
NPM
link
that
will
help
you
understand
it
a
little
bit
more
later.
C
The
benefit,
of
course,
is
that
the
task
runner
watches
both
and
automatically
rebuilds
everything
as
we
save,
which
is
fantastic.
Because
are
we
really
going
to
go
to
everything
in
a
library
component
and
know
that
it's
perfectly
developed
and
then
switch
over
to
our
web
part
and
only
ever
work
in
our
web
part
from
that
point
forward?
Probably
not
we're
gonna
iterate
back
and
forth.
Make
changes,
maybe
correct
some
mistakes
we
might
have
made
so
it's
natural
to
want
to
go
between
the
both
that
go
between
both
at
the
same
time.
C
So,
let's
see
what
that
looks
like
in
a
demo.
So
let
me
set
the
stage
here:
I've
got
vs
code
on
the
left
and
I've
already
got
it
open
to
a
folder.
That
includes
both
excuse
me,
a
library
component
and
a
web
part
now
I've
already
scaffolded
these
out.
So
we're
not
going
to
waste
time
doing
that
and
I've
already
done
the
NPM
link
to
connect
the
library
component
to
our
global
node
modules,
as
well
as
the
NPM
link
on
our
web
part
to
connect
it
so
to
the
connect
it
to
the
library
component.
C
So
the
first
thing
we
want
to
do
is
go
ahead
and
gulp
serve
on
our
web
part,
and
so
we're
not
going
to
use
a
browser
right.
This
second
I've
already
got
one
up
that
we
can
reference
later
and
we
see
that
spins
up
we're
doing
our
web
pack
and
it
should
load
pretty
quickly
and
there
we
go
we're
ready
to
go
so
now.
C
Let's
do
the
same
thing
on
our
library
component,
but
this
time,
what
we're
gonna
see
instead
of
the
nice
Green
local
port
opened,
is
we're
going
to
see
some
some
red
alerts
right.
If
we
scroll
back
up
address
is
already
in
use
of
course.
Naturally,
that's
because
our
web
part
is
utilizing
it
and
we
want
it.
That's
how
we
interface
with
SharePoint
through
our
web
part
or
extension,
so
we'll
go
ahead
and
kill
that
an
entry
is
that'll,
still
work,
but
nobody
likes
red
errors
and
who
knows
what
else
might
go
wrong.
C
We
want
it
to
be
functional
completely,
so
we're
gonna
go
ahead
and
cancel
out
of
that
and
we're
gonna
go
into
our
library
component,
specifically
into
config
and
serve
JSON.
Now
this
is
the
part
that
we
want
to
change
right
there.
It's
using
that
port,
as
we
all
know
it
to
be
four
three
two
one
and
so
we'll
just
change
that
to
anything.
Really
that
we
know
is
not
going
to
conflict
with.
Maybe
something
else
running
on
our
server
or
on
our
machine.
C
So
I'm
just
gonna
go
ahead
and
save
that
as
all
fives
and
now
we'll
go
ahead
and
we
will
re-engage
gulp
serve
with
no
browser
and
we
should
see
it
we're
working
successfully.
We
see
green
great,
it's
been
spun
up,
everything
is
working
and
we
have
our
reload.
So
now,
let's
see
how
this
works
for
us
in
practicality,
when
we're
doing
development,
we'll
go
in
and
look
at
the
source
of
our
library
component.
C
First
simple
out
of
the
box,
it
comes
pre
defined
or
pre
created
with
a
name
just
returns
the
name,
and
so,
if
we
go
into
our
web
part,
we
open
that
up
again,
as
I
mentioned,
I
already
included
it
and
imported
it
ran
the
NPM
link
and
I've
already
created
the
instance
of
it.
So
if
I
come
down
here
and
do
library
component
instance
dot,
we
see
that
name
right
there.
We
see
it's
available
to
us
right,
but
as
we're
going
through
and
making
changes,
let's
go
back
to
our
library
component
and
I'm.
C
Gonna
go
ahead
and
add
another
function
here,
and
this
function
is
just
some
predefined
content
that
we'll
take
a
look
at
in
a
moment.
Grant
just
returns
some
HTML
that
we
want
to
use
and
I've
click
Save,
and
now
you
can
see
the
task.
Runner
has
reloaded,
it's
very
quick
happens
very
fast,
and
so
now,
when
we
go
back
to
our
web
part,
I
can
go
ahead,
and
now
we
see
our
another
method
is
there.
Pnp
Parker
is
now
there
for
us.
That
was
what
the
function
name
was
called
right.
C
So
we
see
that
right,
right
there
and
so
now,
instantaneously
didn't
have
to
rego,
didn't
have
to
reserve,
didn't
have
to
rebuild
the
library
component.
It
automatically
saw
that
I
made
the
change
it
re
web
packed
and
re
bundled
and
everything
is
good.
So
now
we
can
do
that
and
we,
as
I
said
we
see
that
showing
up
immediately
I
also
didn't
have
to
resave
inside
of
my
web
part
at
all.
It
just
showed
up,
and
it
was
aware,
so
that's
awesome.
C
So
now
let's
go
ahead
and
let's
see
what
that
looks
like
as
we
want
to
actually
display
it
in
our
webparts.
So
this
is
just
a
standard
out-of-the-box
web
part
with
content
that
we
all
are
familiar
with
so
I'm
gonna
go
ahead
and
replace
that
with
just
a
reference
to
that
particular
control,
because
then
that
function,
because
we
want
to
go
ahead
and
display
that
HTML,
so
I'm
gonna
go
ahead
and
save
that
we
see
that
has
now
kicked
off
the
gulp
task
runner
here
over
here,
and
it's
done
so
now.
C
Let's
go
ahead
and
take
a
look
at
what
the
results
are.
So
I'll
refresh
my
page
here,
I'm
working
within
a
tenant
on
my
online
workbench
and
if
I
come
here
and
just
do
a
search
on
library,
we
see
there's
my
library
component
and
when
I
load
it
Oh
what
the
what
SharePoint
developer
by
day
superhero
by
night
Parker.
Now
I'm
not
saying
Parker
is
Batman,
but
I've
never
seen
him
and
Batman
in
the
room
at
the
same
time.
C
So
you
know
you
have
to
be
the
judge,
but
a
cool
way
here
to
develop
your
library
components
at
the
same
time,
you're
working
with
your
webparts
or
extensions
and
by
the
way,
as
you
see,
sticker,
2
coming
soon
I'm
getting
some
of
these
made.
If
you
like
them,
then
feel
free
to,
let
me
know
and
I
can
send
some
out
or
since
I'm
at
some
events,
but
it's
a
really
cool
way.
Now,
where
can
you
get
help
for
library
components?
C
C
The
whole
way
explain
some
of
that:
NPM
link
magic,
that
I
was
referencing
and
then
also
down
below
there's
some
more
SharePoint
library
component
champions
I've
been
doing
a
lot
of
evangelizing
on
this
I
really
love
library,
components,
but
Alex,
Sergey
and
Bardhaman
are
all
awesome
guys
in
the
community
that
are
also
doing
a
lot
with
library
components
so
definitely
check
them
out
and
we
can
do
stuff
together.
So
I
just
saw
a
question
from
Andrew
Cure's
to
get
an
answer
to
what
is
so
different
about
a
library
component
from
NPM
package.
C
Okay,
so
the
NPM
package
or
the
NPM
package
is
J's.
Bundle
is
hosted
in
a
CDN
other
than
it's
hosted
in
SharePoint.
Well,
it's
probably
a
longer
story
than
just
a
quick
answer.
When
you
do
an
NPM
import
into
that,
it's
going
to
I'm,
not
sure
what
you
mean,
but
when
you
say
it's
hosted
in
another
I
know
hosted
outside
of
SharePoint,
but
when
you
do
an
import.
Obviously
it's
going
to
import
that
package
into
your
solution.
D
C
C
D
Guess
I'm
just
I'm
keep
asking
the
question
and
I
haven't
gotten
someone
to
really
say
like
you
know,
but
nothing
against
library,
components
I'm
just
curious
like.
Why
do
we
have
a
SharePoint
ism
for
something
that
is
already
something
that
can
be
solved
because
if
I
owned,
the
NPM
package
and
I
published
the
JavaScript
bundle
into
my
own
CDN
or
if
I
can
publish
it
over
to
the
office?
365
CDN
I,
still
own
everything,
and
so
to
me
it's
I
just
curious.
What
what
is
the?
What
is
the
where's?
D
The
value
at
over
SharePoint
I
get
all
the
thing
about
that
you
can
put
it
in
different
places,
but
it's
if
it's
just.
If
it's
a
SharePoint
specific
thing,
you
only
can
use
an
inside
of
SharePoint
where
you
can,
where
who's
an
NPM
package,
you
can
get
the
exact
same
benefit
and
use
it
in
any
kind
of
a
web-based
project.
Sure
yeah.
C
C
Some
of
the
other
things
that
you
can
include
into
it
is
is
not
just
functionality
but
things
like
SPG's
or
fonts,
icon,
fonts
or
images
and
I
guess
that
makes
it
nice
to
have
it
one
nice
neat
little
package.
So
theoretically,
you
could
include
an
impact
impotant,
maybe
not
necessarily
externally,
I've,
just
imported
them,
so
they're
inside
the
library
component,
but
I
personally,
like
the
control
there
and
it's
all
within
the
guise
of
SharePoint.
D
I
wasn't
trying
to
challenge
you.
I
was
just
trying.
Oh
yeah
yeah.
My
point
of
the
thing
was
just
to
make
just
to
see
there's
multiple
ways
to,
as
they
say,
to
skin
the
same
cat
inside
the
frenzy.
Is
there
some
people
choose
one
way,
but
which
is
another
way,
and
by
asking
the
question
and
just
trying
to
get
someone
to
pin
down
the
here's,
the
technical
reason
of
why
you
would
choose
X
over
Y.
That's
all
I
would.
A
I
would
say
that
there's
no
real
technical
reason,
so
how
would
I
put
this
in
a
completely
transparent
way?
The
reason
why
we
ship
to
library
components
also
for
third
party,
is
that
we
started
using
those
internally
at
some
point.
Why
do
we
use
them
internally?
Is
that
we
have
a
pretty
massive
code
base,
the
SharePoint
applications
we
create
applications
which
is
a
consequence
available
which
is
not
available
third-party,
but
they're
huge.
Our
solution
is
massive.
A
That's
why
we
developed
the
rush
components
which
were
common
mode
and
some
of
the
calls,
and
but
one
of
the
benefits
of
using
the
library
components
is
that
we
can
actually
version
everything
in
a
in
a
one
solution
and
again
matter
of
opinion
matter
of
AAA
approach,
and
the
key
point
to
understand
like
AC
was
saying
as
well:
it
there's
no
right
or
wrong.
People
can
don't
come
to
these
things
and
say,
but
what
is
the
right
trick?
What
is
the
recommended
approach?
A
Well,
it's
it's
really
up
to
you
and
we
use
five
very
components
in
our
development
heavily
as
out-of-the-box
SharePoint
is
being
extended
or
then
admit
you
guys
are
being
extended
and
is
that
the
right
thing
to
do
debatable,
but
it
is
more
bundled
as
a
one
large
package
rather
than
then
versioning
things
separately
again.
It
might
be
that
you
want
a
version
things
separately,
anyone
a
version
things
separately
in
your
city
and
and
then
you
want
to
probably
choose
an
alternative
route,
there's
no
right
or
wrong.
A
There's
multiple
different
options
and
one
of
the
things
where
they
say
said,
which
is
a
good
thing
to
remember
library
components
is
a
shipment
ISM.
It
is
share
one
specific
thing:
library
component
as
such:
it's
not
being
used
outside
of
ship.
So
it's
something
which
we
have
introduced
as
part
of
our
development
cycle.
So
again
debatable
whatever
feels
the
most
natural
for
your
developers
and
for
your
development
team
I
would
recommend
using
that
whatever
it
is
so.
C
Yeah,
sometimes
it
just
comes
down
to
a
matter
of
preference
right.
What
what
fits
better
into
your
organization's
development
model
and
patterns
and
practices?
No
pun
intended
that
works
for
each
person,
so
kind
of
Tomatoes
model,
both
both
ways,
work
and
both
ways-
probably
work
well,
but
you
know,
preferences,
I,
guess,
yeah.
D
A
A
Yeah,
it
is
an
important
thing
to
have
an
open
discussion
and
really
understand
the
different
options
and
having
resources
shared
in
the
chat
window,
so
people
can
make
their
own
educated.
That's
a
decision
on
what
model
they
actually
want
to
use.
So
super
important
thing
as
well:
Koot
we
do
have
no
I
mean
it's
there
was
there
any
any
other
things.
There
was
a
question
related
on
list
webparts
out
of
the
apartment.
It
will
be
supporting
connections,
dynamic
data
connections.
A
If
it's
not
doing
that
right
now,
I'm,
not
sure
if
it's
doing
that,
but
apparently
it
isn't,
it
is
definitely
in
the
development.
There
has
been
some
delays
related
on
the
list
and
library
experience,
because
they
we're
getting
a
lot
of
feedback
that
we
need
to
improve
that,
and
then
that
means
that
we
will
need
to
actually
think
the
route
implementation
rather
than
concentrate
just
on
the
wet
part
and
potentially
redesign
and
share
some
of
the
components,
and
that
has
slightly
delayed
some
of
the
functionalities
to
be
available.
A
Any
feature
to
create
a
list
based
on
a
list
is
great.
When
we
will
have
the
same
fun
document
libraries
I
do
not
have
an
ETA
on
that
I
think
it's
actually
coming.
It
is
slightly
more
complicated
thing,
though,
to
implement-
and
it
is
a
separate
implantation
behind
of
the
sensor.
I
can't
be
sure
when
it's
coming
so
I
can't
give
an
ETA.
A
Cute
point
from
Bill
Ayers
good
sign
of
this
communities
that
we
can
have
this
kind
of
discussion
without
people
going
in
the
defense.
Yes,
as
a
ex
consultant
as
a
let's
say,
recovering
consultant
one
of
the
things
what
everybody
needs
to
remember.
Things
are
not
black
and
white,
there's
so
many
shades
of
gray
on
these
things
that
it
is
a
super
important
thing
to
remember:
there's
no
such
thing
as
best
practices,
every
single
man's
practice
depends
and
its
objective.
That's
the
thing
it
depends
on
the
team.
It
depends
on.
The
company
depends
on
the
objective.
A
It
depends
on
your
skill
level
and
understanding.
What
is
the
best
practice.
Two
very
important
thing
is
contest.
Fun
is
perfect:
incremental
takes
not
only
the
files
that
are
changed.
Something
takes
longer
to
build
solution
containing
all
the
word.
Persistent
issues,
I
think
it's
actually
that's
my
understanding,
but
I
can
actually
confirm
that
and
really
the
build
times
are
deep,
highly
dependent
on
their
own.
A
The
solution
structure
now,
like
I,
said
we
are
building
the
the
native
out-of-the-box
SharePoint
using
SharePoint
framework
as
well,
which,
by
the
way,
is
a
good
reminder
for
you
that,
yes,
this
is
a
safe
thing
to
bet
on,
because
the
whole
SharePoint
is
being
built
using
exactly
the
same
tooling
and
exactly
the
same
technology.
So
in
our
case
the
really
the
solution
is
huge
and
we
are
all
the
time
now
trying
to
optimize
the
development
experience,
because
it
delays
and
slows
down
our
internal
development
as
well.
A
If
there's
a
long,
build
times
on
the
solutions
so
which
is
a
good
thing
for
everybody
in
the
community
as
well,
so
everybody
benefits
anyway.
Anyone
are
for
hurricanes,
yeah
I,
think
what
you
know
that
progress.
So
it's
it's
was
it.
It
was
something
starting
with
the
letter
of
D.
So
it's
the
fourth
storm
which
got
a
name
as
it's
gonna,
be
a
long
autumn.
A
D
A
A
Cute
any
any
other
questions
we
can
talk
about
ACS
preparedness
for
hurricanes.
Absolutely
we
don't,
luckily
have
those
in
Scandinavia,
so
it
gets
insanely
cold
in
here,
though,
any
other
questions
ignite
session
catalog
was,
by
the
way
released.
We
will
have
a
shape
and
framework
sessions
in
ignites.
Ac
is
having
few
sessions.
We
have
your
engineering
sessions.
We
also
have
our
community
PMP
session,
where
we
demonstrate
all
of
the
latest
and
greatest.
A
In
the
end,
all
the
source
side
of
the
house
as
well,
and
we
have
pretty
cool
stuff
queued
up
for
ignite
time,
is
running
out
with
disability,
but
we'll
definitely
have
if
nothing
else,
insanely
good
smoke
and
mirrors
demos,
and
then
it's
gonna
be
truly
functioning
slightly
later.
That's
how
it
works.
A
You
don't
want
to
actually
know
I
should
actually
do
it
like
five
years
after
SPC
2018.
How
did
we
do
certain
demos
explanation
at
some
point,
because
it's
it's?
It
is
every
now
and
then
it's
smoke
and
mirrors
now,
but
luckily
all
of
the
stuff.
What
if
we
devote
our
then
fully
functioning
slightly
later?
So
that's
absolutely
point.
B
A
Talked
about
the
site
designs:
yes,
there
can
you
show
us
their
sessions
in
the
next
call.
Yes,
I'll
definitely
go
through
the
specifics
and
share
about
development
sessions
in
the
upcoming
goals.
That's
a
good
reminder.
I
should
actually
prep
that
in
here
the
schedule
is
not
yet
available,
but
the
session
names
are
already
available
as
sessions.
Firstly,
our
planning
to
release
Shepard
Fairey,
2.0
1.91,
so
1.91
is
already
out.
1.10
is
going
to
go
out
in
September.
We
we
did
have
a
slide
around
that
one
earlier
today.
A
The
shipment
framework
2.0,
is
not
really
well
we'll
see.
If
that's
going
to
happen
or
are
we
gonna
name
rename
some
of
the
framework
areas
and
and
how
do
we
align
to
this
larger
thinking
around
what
we
want
to
do
it
with
office
365
in
future?
For
now
you
can
expect-
and
that
will
have
one
point
ten
in
September
and
then
one
point
11
in
October
and
then
one
point
12
in
November.
A
That
would
be
the
logical
thing
to
happen,
but
basically
that's
that's
gonna
happen
from
now
and
then,
if
there's
going
to
be
additional
announcements
that
also
going
to
be
done
in
ignite,
so
I
can't
disclose
anything
special.
Now,
it's
a
reusable
control,
beaker
being
considered
I
think
we
actually
have
something
in
the
pipeline,
even
as
a
poor
request,
if
I
remember
from
Hugo
Bernier
related
on
the
image
picker,
our
file
selection
I'm
not
sure
quite
sure
where
it
is
one
of
the
challenges.
What
we're
having
it.
Some
of
these
controls
and
some
of
the
demos.
A
What
we're
seeing
also
in
the
community
are
using
controls
and
functionalities
which
we
as
a
Microsoft.
We
don't
want
people
to
use
outside
of
our
first
party
webparts
until
we
have
actually
been
designed,
then
to
be
used
outside
of
first
party
webparts,
so
we're
still
trying
to
figure
out.
How
do
we
do
that
for
certain
functionality
is
I?
A
What
we're
having
in
engineering
on
on,
for
example,
our
team
pushing
heavily
on
other
teams
releasing
these
controls
as
reusable
controls,
but
then
for
them
it
would
be
an
additional
burden
to
actually
do
that
because
then,
if
you
start
using
those
controls,
then
its
are
thinking
backward,
compatible
version,
which
is
an
additional
overhead
for
them
to
implement
their
first
party
webparts.
So
it's
an
interesting.
Let's
say
how
would
I
put
an
interesting
ballgame
to
figure
out
what
are
the
things?
A
What
we
want
third
party
to
use,
what
are
the
things
which
are
aimed
for
first
party
and
what
are
the
how
much
we
can
actually
do
those
differences,
because
we
don't
wouldn't
like
to
have
those
differences,
but
still
so
I
think
that's
it.
Any
can
pre
create
AB
catalog
site
collections
whenever
a
new
tenant
is
created,
we've
been
debating
with
that
for
a
long
time
by
the
way
and
good
questions
won't
go
them.
A
It
seems
to
be
that
will
give
you
an
API
to
make
that
happen,
but
we're
not
looking
into
recreating
that
beforehand,
because
it
would
have
a
storage
impact
and
the
individual
impact
in
the
one
side.
Tenant
is
quite
small,
but
when
we
talk
about
hundreds
of
millions
of
tenants
and
then
sums
up
to
be
quite
a
huge
storage
impact,
so
all
of
that
has
a
overall
cost
impact
in
our
operations
and
then
that's
reason
why
we
need
to
think
through
in
scale
as
well,
but
anyway,
that's
it
for
this
time.
A
So
thank
you,
everybody
for
joining.
Thank
you,
Raman.
Thank
you,
David
for
the
great
discussion.
Thank
you
AC
for
the
great
discussion
as
well.
It's
good
to
have
those
discussions
and
also
ask
those
hard
questions,
because
that's
how
we
learn
by
going
through
those
hard
questions
together
as
a
community.
That's
a
really
really
valuable
thing,
even
though
that
wasn't
too
hard.
I
know
that
AC
has
much
harder
questions
on
his
backlog
as
well,
and
but
thank
you,
everybody
for
joining.
A
Thank
you,
everybody
for
being
active
on
the
chat
window,
great
to
see
that
we
are
getting
back
online.
The
chat
this
is
super
active
all
the
time
we're
helping
each
other
and
a
lot
of
people
in
the
call
about
dissipating
here
and
we
have
crowing
activities
in
Catan
and
the
use
it
is
is
really
off
the
roof.
So
thank
you,
everybody
for
making
that
happen
as
well,
but
we'll
come
back.