►
From YouTube: SPFx JavaScript Special Interest Group - March 2nd 2017
Description
Details on the covered topics from https://techcommunity.microsoft.com/t5/SharePoint-Developer/SharePoint-Patterns-amp-Practices-JavaScript-Special-Interest/m-p/49874
A
Hello
and
welcome
to
the
SharePoint
framework
and
JavaScript
special
interest
group
bi-weekly
call
for
March
second
2017
2017
is
flying
by
for
me.
I,
don't
know
about
all
you
guys
out
there
and
girls
out
there,
but
so
we'll
go
ahead
and
take
a
look
here
at
what
what
this
is
all
about
and
what
we're
doing
for
folks
that
might
be
new
to
the
call
or
catching
up.
A
Somebody
supposed
to
have
a
more
specific
interest
around
JavaScript
development,
the
SharePoint
framework,
client-side
development
in
general,
and
so
what
we've
done
is
started.
These
special
interest
groups
there's
one
now
for
the
power
shell
and
core
component
as
well,
and
you
can
of
course
attend
all
or
some
of
these
meetings.
A
Whatever
fits
your
interest
in
your
schedule,
but
the
goal
is
to
allow
us
to
drill
down
a
little
more
deeply
into
now
the
short
framework
that
we
teach
and
as
well
the
JavaScript
core
component,
we're
developing
alongside
to
help
with
the
sharepoint
development
in
the
SharePoint
framework.
If
you
choose
to
use
it
so
force
not
required,
so
two
great
links
down
there
at
the
bottom,
the
SP
P&P
community
link,
will
get
you
out
to
the
tech
community,
which
is
a
great
location.
A
If
you
have
questions
or
want
to
have
discussions
with
others
in
the
community,
as
well
as
those
of
us
on
the
core
team
and
then
the
bottom
link
dev
office,
calm,
/
sharepoint
is
your
one-stop
shop
for
everything,
sharepoint
development.
So
whether
you
want
to
learn
about
the
new
SharePoint
framework
where
you
want
to
learn
about.
A
Sharepoint
add
in
development
or
even
classic,
you
know
full
trust,
code
development,
there's
resources
there
for
all
those
areas
on
the
devs
office,
column,
/,
SharePoint,
and
that's
of
course,
being
constantly
improved
as
we
go
so
jumping
in
to
our
agenda
42,
a
the
pjs
core
component
will
do
a
quick
update
on
that.
A
little
bit
on
the
SharePoint
framework.
A
You
know
folks
wanting
to
ask
questions
or
make
points
the
SharePoint,
Saturday,
Munich,
Thank,
You
Nigel,
so
awesome
I
thought
it
was
bigger
than
the
Saturday
but
cool.
So
so
I
know
a
lot
of
folks
from
this
call
will
be
at
that
which
is
really
exciting,
really
cool,
so
make
sure
you
connect
with
folks
from
the
community
there
so
first
off
a
quick
update
for
the
javascript
core
component.
Again,
thank
you,
as
always
everybody
to
contribute
and
thank
you
to
everybody
that
provides
feedback
as
well.
A
It's
invaluable
to
us
to
make
everything
to
make
the
library
better
for
everybody's
use
and
then
as
well.
Your
contributions
really
help
to
grow
the
library,
because
obviously
those
of
us
on
the
core
team
can
only
scale
so
much
so
getting
folks
from
the
community
jumping
in
whether
it's
contributing
code
or
answering,
questions
and
issues
are
helping
out.
I
know:
John
Liu
really
helped
out
on
an
issue
with
angular,
because
I'll
admit
I
am
an
angular
newbie.
A
So
that
was
really
helpful,
appreciate
that
from
John
and
appreciate
everybody
else
who
jumps
in
and
helps
out
with
the
questions
as
well.
So
moving
forward.
Some
quick
updates
we're
fixing
issues
as
they
come
in,
so
thank
you
for
reporting
them
appreciate
that
and
I
do
just
want
to
say,
I
appreciate
the
level
of
detail.
Folks
are
including
with
the
issues.
So
that's
great
to
see.
It
really
helps
us
sort
of
narrow
down
what
the
the
problem
is
and
figure
out
how
to
fix.
A
It
so
appreciate
the
details
and
appreciate
the
issues
getting
reported
and
we
are
looking
to
fix
those
just
as
fast
as
we
can.
Our
next
release
is
going
to
be
targeted
for
March
10th,
that's
again
in
line
with
the
rest
of
the
patterns
and
practices
program,
and
we
are
going
to
continue
to
align
to
these
monthly
releases,
so
it'd
be
smaller,
more
regular
releases,
which
I
think
will
help
get
fixes
and
updates
out
there
a
little
more
regularly.
We
did
have
an
issue
come
in,
so
there
was
a
interesting
things.
The
typescript
folks
did.
A
They
submitted
a
breaking
change
in
a
minor
release,
so
typescript
221
introduced
a
breaking
change
with
the
types
the
at
types,
what
fetch,
what
WG
fetch
library
or
reference
whatever
you
want
to
call
it
where
they
decided.
Suddenly
to
introduce
all
the
the
Taipings
for
response
and
fetch
and
request
and
those
those
things
so
you've
got
the
duplicate
definition
error.
So
that
was
interesting.
A
I
appreciate
folks
reporting
that
so
just
wanted
to
highlight
that
a
little
bit
so
we've
updated
the
package.json
in
the
SVP
and
pjs
library
to
bring
in
the
latest
typescript
and
we've
updated
our
typing's
appropriately
and
we'll
have
a
little
bit
more
about
this
in
the
release
blog
post,
but
it's
going
to
mean
either
folks
are
going
to
need
to
update
their
local
typescript
in
their
projects
to
221
or
manually,
install
the
at
types
pipings.
So
will
detail
that
will
detail
those
steps,
but
it
was
one
of
those
it
caught
me
by
surprise.
I!
A
Think
it
caught
a
lot
of
folks
by
surprise.
Judging
by
reading
some
of
the
issues
in
the
various
repos
I've,
also
added
in
the
TS
lint
settings,
the
prefer
const
flag
and
made
all
the
associated
updates
throughout
the
file.
So
that
is
if
a
variable
is
not
ever
reassigned
using
cost
to
declarant,
instead
of
let
so
that's
been
enabled.
So
it's
and
that
should
be
all
working.
A
If
you
pull
the
latest
code,
you
shouldn't
get
any
issues,
but
if
you're
writing
new
code
in
in
our
library
specifically
this
wouldn't
affect,
if
you're
using
this
in
other
libraries,
you
might
need
to
update
and
use
cost
to
get
the
the
linting
to
pass.
We've
also
updated
to
web
pack.
2
I
did
that
last
night.
That
was
I'll,
say
surprisingly
easy.
They
have
a
nice
guide
on
the
web
pack
site
that
you
can
go
through
and
just
kind
of
step
by
step.
A
A
Lastly,
if
you
haven't
seen
it
I
tweeted
it
out
two
days
ago
yesterday
that
so
there's
now
an
article
on
the
official
guidance
on
Deb's
office
accomplished
SharePoint
around
using
the
SVP
and
pjs
library
in
SharePoint
framework.
I
did
my
example
with
knockout,
because
there
weren't
a
lot
of
knockout
examples,
but
it's
the
the
sort
of
guidance
in
there
would
apply
on
whatever
framework
you'd
like
to
use
whether
that's
react
or
no
framework
or
angular.
A
Whatever
same
guidance
would
apply,
but
this
sample
happens
to
be
in
knockout,
so
check
out
that
article
and
it
was
an
Associated
code
sample
in
the
samples
repo
now.
So
you
can
pull
that
down
and
play
with
that
as
well,
so
that
sort
of
is
a
step-by-step
guide
and
a
little
bit
more
detail
than
what
we
have
on
our
wiki
and
finally,
I've
got
in
the
works
and
upcoming
article
on
extending
spp
and
pjs.
That's
one
of
my
sort
of
next
goals.
A
Next
big
goals
is
to
make
it
much
easier
to
extend
the
library
and
sort
of
enhancing
the
extension
points
available
to
folks.
So
if
you
really
need
to
need
to
or
want
to
sort
of
get
into
the
internals
of
the
library
and
kind
of
change,
how
things
behave
a
little
bit
or
the
articles
are
going
to
cover
sort
of
making
your
own
business
objects
wrapped
around
or
using
the
library.
A
So
having
your
own
sort
of
list,
objects
and
web
objects
and
list
item
objects
and
having
custom
methods
and
building
on
top
of
the
spp
and
pjs
library
for
those
business
cases,
which
I
think
the
knockout
j/s
example
has
a
little
bit
of
that
in
it
and
I
think
it's
a
really
powerful
way.
So
you
can
sort
of
bind
a
view
model
based
on
the
spp
and
paige
is
doing
the
data
work
to
your
in
this
case
knock
out
the
same
for
react
and
the
others
and
then
have
all
the
methods
sort
of
wrapped
around.
A
So
you
get
a
nice
easy
integration
path
that
way,
so
that
article
is
upcoming.
So
look
forward
to
that
is
the
article
on
SharePoint
framework
with
knockout
at
v1,
not
RC
0.
So
the
article
that
I
just
was
talking
about
is
with
the
GGA
bits,
so
it
is
applicable
to
v1.
If
you
want
to
call
it
that,
so
it
is
using
the
ga
bits
and
should
work
with
the
ga
stuff.
A
So,
as
always
opportunities
to
participate,
you
can
demo
a
SharePoint
framework
web
part.
Almost
call
would
love
to
see
folks,
more
demos,
more
demos,
more
demos,
demos,
SPT
and
pjs
in
a
project
unrelated
to
the
SharePoint
framework.
Certainly
welcome
that
if
you
can
wrap
the
two
together,
that's
great,
but
even
if
you
just
have
a
new
SharePoint
framework
web
part,
you
want
to
show
off
to
the
community,
really
invite
folks
I.
A
Think
it's
a
great
opportunity
to
kind
of
show
off
the
cool
stuff
folks
are
doing
out
there
in
the
world,
contribute
on
github
either
sympathy
issues
again,
thanks
to
folks,
are
doing
that
or
submitting
code
thanks
again.
Of
course,
the
folks
you
know
who
are
submitting
those
pieces
of
code
and
things
like
that,
and
as
always,
we
appreciate
the
feedback
both
on
the
JavaScript
core
library,
as
well
as
SharePoint
framework.
A
The
feedback
really
helps
drive
and
make
the
product
of
SharePoint
framework
better
and
then
the
library
of
SBP
in
pjs
better
as
well
Ralph's
got
a
question.
Anyone
recall
the
angular
items
out
there
for
angular
2
aight,
I'm
not
sure
I
think
their
samples
out
there
for
both.
I
think
a
lot
of
the
samples
are
just
angular
right
now
and
then
the
angular
2
stuff
is
coming
a
little
bit.
There's
a
little
bit
more
work
to
do
around
the
component
ization.
If
I'm
remembering
correctly
so.
A
Correct
angular,
1
and
angular
2
are
not
the
same
so
right
so
ACS
answering
new
angular
2
doesn't
work
super
great
in
SharePoint
framework
today.
So
when
I
say
angular,
I'm,
probably
talking
about
angular
1
but
again,
I'll
fall
back
on.
My
I
know
very
little
about
angular
position
right
now,
so
that
will
be
my
kind
of
cover
for
that.
So
some
quick
SharePoint
framework
updates
and
you
guys
are
going
to
be
a
little
surprised
at
how
quick
these
are
simply
because
again
faces
in
the
air,
but
did
want
to
point
out.
A
A
I
won't
say
daily,
but
definitely
weekly,
we're
getting
new
guidance
out
there
on
things
as
they
come
up
and
there's
some
new
guidance
coming
out
on
provisioning
things
through
your
SharePoint
framework
web
parts
or
through
your
SharePoint
framework
package
using
the
older
style
like
elements,
XML
kind
of
technique,
so
folks
can
take
a
look
at
that.
That
is
a
two-thirds
finished
article
as
a
few
more
details
to
be
added
there,
but
do
check
those
out
really
encourage
folks,
I
think
there's
some
great
guidance,
some
great
learning
for
those
kind
of
things.
A
Looking
for
samples
again
AKA
ms
SPF
x,
samples,
adding
stuff
there
again
I'd,
say
weekly,
if
not
daily,
but
definitely
weekly,
we're
going
to
new
samples
in
there.
So
you
can
check
out
the
knockout
one.
I
was
just
talking
about
and
others
as
well
of
course,
so
do
check
that
out
and
again,
I
really
want
to
encourage
folks
in
community.
If
you
have
a
cool
sample
contributed
here,
so
others
in
the
community
can
learn
and
then
let
us
know
we'd
be
really
happy
for
you
to
demo
it
on
the
call
here
as
well.
A
So
it's
a
great
opportunity
for
you
to
get
some
visibility
in
the
community
and
really
help
folks
learn
so
we're
just
kind
of
at
the
start
of
the
SharePoint
framework.
I
know
a
lot
of
folks
on
these
calls
have
been
using
it
for
a
while
now,
through
the
various
beta
releases,
the
RC
0
and
now
GA
you're,
going
to
start
to
see
a
bunch
of
new
faces
show
up
a
new
interest
now
that
we're
at
GA,
which
is
always
really
exciting.
A
But
this
is
a
great
chance
for
those
of
you
that
have
been
active
and
learning
about
this
for
a
while
now
to
help
those
who
are
just
showing
up
to
get
up
to
speed
and
learn
and
really
kind
of
give
back
and
help
that
community
grow
around
SharePoint
framework
and,
like
I
said,
would
really
love
for
folks
to
submit
samples
and
demo
I'm
on
the
call
a
great
opportunity
for
us
all
to
learn
from
each
other.
So
the
latest
developments
in
SharePoint
framework
I
know
you
guys
are
really
used.
A
Two
vases
super-dense
slides,
so
I've
just
got
one
line
item
which
I
think
is
really
exciting.
We
hit
general
availability.
If
you
guys
haven't
pulled
down
the
GA
bits.
Please
do
I
I'm,
really
impressed
I
got
to
see
this
pretty
early,
as
did
I
know
some
other
folks
on
the
call,
but
how
far
it's
come
from
what
it
was
a
year
ago
to
now
and
which
makes
me
really
excited
for
what
it's
going
to
continue
to
grow
to
be
over
time,
and
that
again
is
big
credit
to
all
of
you
who
provided
feedback.
A
So
the
issues
list
feedback
through
the
community
so
keep
that
feedback
coming
because
again
we're
listening
and
it
makes
it
better
for
everybody.
So
we
really
love
to
see
that
feedback
so
keep
that
coming,
but
pull
down
the
GA
bits
play
with
the
GA
bits
write
some
samples
submit
some
samples
demo
on
this
call.
Let
us
know
if
something's
broke,
of
course,
but
really
start
to
who
deployment
that
the
general
availability
stuffs
really
neat
did
want
to
touch
briefly.
A
A
Can
you
pull
the
GA
bits
down?
You
can
pull
the
gia
bits
and
every
tenancy
right
now
should
be
updated.
So
nobody
that
should
all
be
done.
That
was
a
little
bit
late
on
the
first
day,
mostly
due
to
time
zones
and
I
got
hit
by
this.
So
it
wasn't
just
certain
folks,
but
that
should
all
be
resolved
and
please
do
GA
bits
and
there's
instructions
as
well
on
the
devs
office,
calm
on
getting
updated
their
on
getting
updated
to
the
ga.
A
So
here's
the
face
of
slide
so
getting
started
with
SharePoint
framework.
We've
got
lots
of
modules:
lots
of
tutorials
lots
of
material
on
github
on
the
docks
site,
so
really
encourage
folks
to
dive
in
there
and
then
encourage
folks
that
have
already
dove
in
again
to
kind
of
send
me
elevator
back
down
as
they
say,
and
help
the
folks
that
are
just
showing
up
and
really
help
guide
folks
that
have
questions
and
get
them
involved
in
the
SharePoint
framework,
because,
as
the
whole
community
grows,
we
you
know,
we
all
benefit
from
that.
A
We
all
learn
from
each
other
and
then
we
all
end
up
with
a
better
thing
to
use
and
develop
on
so
like
I
said
well,
I
put
it
in
for
discussions.
We've
got
a
couple
demos
here
to
go
through
today,
and
so
I
want
to
go
first
and
I
want
to
share
my
desktop
share
that
one
and
wait
for
somebody
to.
Let
me
know
when
you
can
see
that
when
that
comes
through.
A
While
I'm
waiting
there
make
David
a
presenter,
so
he
can
be
ready,
got
it
okay,
great!
So
let's
drop
that
down,
and
so
what
I
wanted
to
talk
about
was
the
Travis
integration
which
folks
may
or
may
not
be
familiar
with
Travis
and
try.
This
is
a
continuous
integration
tool.
It's
one
of
at
least
several
out.
There
I
found
it
very
easy
to
integrate
with
and
I'll
kind
of,
show
you
what
I
did
here
in
a
second
but
did
want
to
show.
A
This
is
the
sort
of
Travis,
dashboard
and
you'll
see
here
that
we've
got
a
lot
of
bill.
I
can
see
a
lot
of
the
microsoft
stuff
just
because
of
Microsoft
but
you'll
be
able
to
see.
You
know,
for
example,
here's
one
for
my
repo
that
passed,
and
so
this
is
showing
you
and
it's
got
this
really
awesome
log
that
shows
you
all
the
tests
that
were
run.
Is
you
some
information
on
things
that
might
have
ran
long
comes
down
here?
A
A
So
the
first
thing
I
want
to
do
is
real,
quick,
I'm
just
going
to
make
a
couple
of
meaningless
update,
so
I
can
submit
a
pull
request
and
sort
of
show
you
guys
this
process
and
then,
as
it's
running,
I'll
walk
you
through
the
configuration
so
I'm
just
going
to
say
this
interface
defines
the
result
of
adding
a
field,
so
super
meaningful
comments.
I
think
you
know
we've
all
written
great
comments
like
that
in
the
past.
But
now
the
important
thing
is,
you
can
see.
A
So
this
is
just
demo
normally
I
would
fill
this
all
out
again,
being
a
good
citizen,
but
I'm
gonna
say
create
a
pull
request,
and
so
what's
going
to
happen
now,
when
I
create
this
pull
request
is
you're
going
to
get.
You
know
the
normal
Microsoft
legal
stuff
happens,
but
now
you're
going
to
see
this.
This
Travis
thing
is
popped
up
here,
and
so
every
time
you
submit
a
pull
request.
A
Now
this
Travis
build
is
going
to
run,
and
so
you
can
click
on
the
details
and
you'll
be
able
to
see
the
details
of
your
build.
So
these
are
actually
running
in
parallel,
they're,
completely
separate
and
so
you're
going
to
see
a
mine
is
set
up
and
it's
going
to
run
all
the
tests
actually
against
SharePoint
the
one
for
your
pull
request
is
just
going
to
run
the
linking
the
building
and
the
packaging.
A
It's
not
going
to
actually
execute
against
sharepoint
and
that's
a
limitation,
not
a
limitation,
but
a
thing
you
can't
do
because
it's
a
be
an
attack
surface.
So
if
and
I'll
show
you
that
in
a
second,
but
so
every
time
you
submit
you'll
see
this
get
updated
here
for
the
pull
request,
and
then
you'll
see
this
when
it
updates,
it
will
show
you
success
or
failure,
and
so
jumping
back
now
that
we've
got
those
running
and
we'll
come
back
to
those
in
a
second.
What
did
we
do
to
set
this
up?
A
Well,
first,
you
go
to
the
Travis
website
and
it's
got
a
getting
started
guide,
which
is
two
or
three
steps,
and
it
involves
enabling
Travis
in
your
repo
and
they
walk
you
through
that
very
simple.
It's
like
adding
any
of
the
other
web
hook
based
integrations
with
get
you
might
have
done
in
the
past
very
similar,
and
then
in
our
repo.
A
You
have
to
set
up
a
dot,
Travis
dot,
yml
file,
and
this
is
the
file
Travis
uses
to
orchestrate
its
builds.
Ours
is
very,
very
simple.
These
Travis
files
can
be
rather
complex.
You
can
do
a
lot
of
things.
It's
a
very
powerful
tool,
we've
just
scratched
the
surface,
with
what
we're
doing,
but
it's
already
I've
seen
an
already
great
value
in
doing
you
know
these
integrations
even
at
this
simple
level.
So
first
you
tell
it
a
language
in
our
case
nodejs,
meaning
or
a
JavaScript
project.
A
You
can
give
it
a
version
so
we're
giving
it
just
six.
What's
one
thing,
that's
really
cool
about
Travis
that
we're
not
doing
currently
but
could
certainly
do
in
the
future.
Is
you
can
create
a
matrix
of
testing,
so
I
could
do
node,
5
6
7?
Then
you
can
have
different
configurations
for
the
various
versions
you
can.
You
know
make
this
whole
matrix
of
testing.
Excuse
me
and
it
will
run
you're
a
bunch
of
separate
builds
for
you
across
your
entire
matrix.
A
A
Travis
will
automatically
run
an
NPM
install
for
you,
so
it'll
load
everything
in
your
package.json.
That's
an
automatic
thing.
We
don't
have
to
script
that,
but
one
thing
we
do
have
to
do
is
because
we're
using
gulp-
and
this
is
right
out
of
the
Travis-
getting
started-
guide
this
before
script,
so
you
can
run
one
or
more
scripts
prior
to
any
of
your
build
operations,
so
we're
installing
gulp
global
globally.
So
we
can
use
the
command
line
for
gulp
because
that's
how
our
tests
can't
run
and
then
you
can
see
here.
A
A
A
We
could
have
used
the
other.
The
standard
gulp
commands
we
use,
but
I
found
it
easier
because
we
had
to
make
some
modifications
instead
of
having
a
bunch
of
if
statements
and
trying
to
configure
things,
I
found
it
and
thought
it
would
be
much
easier
to
just
pull
these
out
to
their
separate
to
a
separate
file
to
be
separate
commands,
because
then
we
can
do
whatever
we
need
to
do
for
Travis.
So
looking
at
this
you'll
see
a
lot
of
similarities
between
our
other
gulp
files.
A
So
you
can
see
our
Travis
pull
request
on
our
Travis
push.
So
you
can
see
here.
We've
got
the
clean
command,
we're
going
to
run
the
Travis
wenting
and
the
difference
between
the
Travis
one
ting
is
well
actually
going
to
throw
an
error,
so
your
build
will
fail
on
Lintz
errors.
So
if
you
just
are
doing
the
build
normally
not
through
Travis
wenting
won't
actually
produce
errors,
you'll
get
warnings.
This
is
actually
going
to
throw
errors
now
for
linting,
because
we
want
the
bill
to
fail.
A
A
So
it's
it's
a
you
can
call
it
a
limitation,
but
really
it's
a
security
feature
of
Travis
that
for
pull
request.
You
can't
get
the
environment
variables,
we've
set
up
and
I'll
show
you
setting
those
up
and
a
second
here
and
then
for
pushes,
which
is
so
when
I
merge
my
pull
requests
in
or
when
I
do
emerge
from
dev
to
master
we're
going
to
run
this
Travis
push,
which
again
is
going
to
do
clean
our
Travis
linting.
It
seems
our
Travis
web
test,
which
is
going
to
have
the
web
tests
enabled
based
on.
A
We'll
still
see
timeouts-
and
this
is
just
I
think-
has
to
do
with
its
running
in
these
little
virtual
containers
in
Travis
and
communicating
with
sharepoint,
and
sometimes
it
just
gets
slow
or
hung
up
for
whatever
reason,
and
we
might
even
see
that
sometimes
it'll
fail,
I,
don't
know
once
every
ten
times
or
so
we'll
get
a
timeout,
so
I've
bumped
it
up
to
45
seconds.
That
seems
high
enough
to
me,
but
you
know
folks
find
that
we're
seeing
too
many
timeouts.
We
can
always
bump
that
up
again.
A
So
those
are
our
Travis
commands
and
that's
our
entire
Travis
file
right
now,
like
I,
said
we're
just
scratching
the
service
of
what
you
can
do
with
Travis.
So
as
as
we
get
more
into
it,
we
will
start
you
know
expanding
this
doing
a
little
bit
more,
but
for
now
we're
already
able
to
run
all
our
tests
and
we're
actually
able
to
run
our
tests
against
sharepoint.
A
So
keep
in
mind,
you
can
see
here
we're
doing
our
setting
the
global
settings,
which
is
what
the
the
testing
stuff
grabs,
the
Dean's
out
of
global
and
we're
getting
those
from
the
process.
So
what
I
wanted
to
show?
You
is
look
at
all
our
checks
have
passed.
So
this
was
my
pool
request.
All
my
checks
have
passed
great.
So
if
they
had
failed,
there'll
be
a
little
link
here
to
go,
see
the
details
and
so
I'm
just
going
to
say,
merge
this
pull
request.
A
A
You
also
see
these
builds
past
and
if
we
look
at
the
SharePoint
build
here's,
it's
installing
all
the
NPM
stuff,
and
if
you
look
at
the
log,
you
can
see
all
the
things
it
did.
In
this
case
we
didn't
run
any
of
the
web
tests,
because
this
was
a
pull
request,
so
it
passed.
But
if
we
look
at
the
one
in
my
repo
it
also
passed,
which
is
always
good
to
see.
A
But
what
we're
doing
is
the
same
stuff,
we're
running
the
wente
in
the
packaging,
but
you
can
see
now
we're
running
the
web
test
and
so
every
once
in
a
while
you'll
get
these
little
notes
when,
when
things
went
a
little
long
and
it'll
show
you
all
the
tests
that
pass
and
I
actually
updated
the
testing
to
give
you
this
for
both
output,
because
I
think
it's
nice
to
see
that,
especially
since
this
is
running
remotely
that
we,
you
know,
can
see.
What's
going
on
on
a
little
bit
more
verbose
manner.
A
You
can
see
everything
past
fantastic,
no
timeouts.
We
have
four
pending
tests
that
haven't
gotten
written
and
our
bill
too
exited
with
zero,
which
means
passing
so
what
I
want
to
show
you?
So
this
is
in
my
personal
repoed.
This
is
my
fork
of
the
jas
core,
and
so
one
of
the
things
you
can
see
if
I
go
to
settings
and
you
can
set
this
up
in
your
own
repo
as
well.
These
are
the
environment
variables.
You
can
add
environment
variables
of
any
name.
You
want,
you
can
give
it
any
value
you
want.
A
You
can
actually
say
if
a
value
will
be
displayed
in
the
build
log,
so
obviously
for
client
ID
secret.
These
things.
We
don't
want
that
and
then
I
can
just
add
that
and
now
that
any
name
would
be
available,
I'm
at
process
env
any
name,
and
so
I
can
add
in
our
case
we
needed,
for.
I
could
add
any
number
of
these
to
configure
the
build
that
I
might
need,
and
then
I
can
come
in
and
delete
these
so
really
powerful,
really
simple.
You
can
also
set
stuff
up.
A
You
can
do
variables
in
the
yml
file
and
encrypt
them
and
and
all
these
sorts
of
things-
and
I
started
to
play
with
that
and
then
found
this
and
thought
well.
This
is
about
a
hundred
times
simpler.
So
really
a
big
fan
of
that
and
you
have
settings
for
building
on
pushes
building
on
pull
requests.
You
can
build
only
if
the
Travis
file
is
present.
Things
like
that
and
then
to
show
you.
So
this
is
in
the
SharePoint
j/s
core.
A
So
this
is
now
also
going
to
run
all
our
web
tests,
because
this
is
a
merge
and
I
want
to
show
you
the
settings
here.
So
I've
got
the
same
client,
ID,
secret
notification,
URL,
etc.
One
thing
there
are
different
values,
obviously
I'm
using
my
personal
site
for
my
repo
and
then
we
have
a
patterns
and
practices
site
for
these
tests
to
run,
but
we've
also
set
up-
and
this
is
a
beta
feature
of
travis
but
a
cron
job,
so
a
timer
job
a
daily
job
to
run.
A
So
you
can
do
this
daily,
weekly
or
monthly.
At
this
point
again,
beta
feature
so
they're
enhancing
this
as
they
go,
but
so
now,
every
day
we're
just
going
to
go
ahead
and
run
the
entire
test
suite
from
the
dev
branch
against
sharepoint
online
and
we're
doing
something
very
similar
with
the
sea
psalm
core
component,
because
this
is
actually
we
found
bugs
that
have
been
introduced
into
sharepoint
online
by
doing
our
daily
testing
or
we
found
changes
to
sharepoint
online
that
aren't
bugs
that
are
changes
that
might
break
something
we're
doing
so.
A
This
will
be
a
nice
daily
check
and
I've
actually
just
scheduled
this
today
for
the
first
time
so
I
think
that's
going
to
be
another
great
feature
of
Travis
for
us,
so
that's
kind
of
our
disintegration.
I
wanted
to
talk
through
that,
like
I,
said
just
take
about
five
and
a
half
minutes
to
run.
If
you
want
to
set
this
up
for
your
own
repo,
like
I
said
you
just
need
to
grant
Travis
access
go
in
and
set
these
environment
variables.
A
And
again,
if
you
look
at
the
blog
post,
I
published
on
this,
we've
got
I've
got
the
names
of
the
environment
variables
in
the
descriptions
and
more
details
on
the
setup
process
there.
If
you'd
like
to
go
through
it
and
one
thing:
if
you
break
the
build
or
if
I
break
the
build,
this
cool
email
comes
out,
telling
you
it's
broken
and
then
you
can
go,
look
at
the
details
and
see
what
happened.
Generally.
A
I'll
tell
you
it's
a
timeout
all
the
failures
I've
seen
past
when
I
was
just
learning
and
setting
things
up
have
been
timeouts
so
right
here,
where
it
says,
cancel
you'll
have
a
little
button
to
restart
the
build.
So
you
can
always
restart
the
build.
If
you
should
need
to
do
that
like
if
you
just
see
timeouts,
if
you
just
restart
it,
it
should
run
fine.
The
second
time
it
just
means
there's
a
hiccup
in
the
network
or
something
took
a
little
too
long.
Something
like
that.
A
A
B
Great
so
as
Patrick
admission,
this
is
really
utilizing.
The
classic
mode
within
SharePoint,
using
Jets
link
will
be
the
focus
I'll
give
you
the
dime
tour
here
in
a
minute
of
everything.
We've
got,
though.
The
point,
though,
really
is
that
we're
utilizing
and
extending
taking
advantage
of
the
API,
the
hooks
that
SharePoint
provides
us
right.
So,
while
the
demos
here
really
are
utilizing
and
taking
advantage
of
items
in
the
classic
mode,
we
know
that
things
are
going
to
come
out
and
be
available
to
us.
B
You
know
a
lot
of
what
we
see
today
should
be
able
to
be
taken
advantage
of
and
utilized
in
that
way,
for
the
modern
experience,
though
so,
hopefully,
don't
look
at
any
of
this
as
a
dying
breed
or
you
know
something
that
won't
be
available
in
the
future
likely
if
you
just
a
lot
of
this
came
from
the
creativity
of
looking
at
the
API
is
the
hooks,
the
the
openings
that
SharePoint
provides
to
us
to
take
advantage
of
building
a
branded
experience.
So,
okay,
so
I'll
give
you
a
little
quick
tour.
B
You
see
rocky
here's
being
used.
I
used
a
non-business
data
typically
when
I
show
demos,
because
it
helps
people
focus
in
on
the
information
and
the
functionality
as
opposed
to
getting
caught
up
with
trying
to
relate
the
data
to
their
data.
No
one
in
their
right
mind
is
going
to
say
and
look
at
rocky
and
say
yeah
that
really
to
my
business
great.
Let
me
focus
on
that.
So
it's
usually
a
fun
topic.
Everything
you
see
here
is
inside
of
responsive
design.
B
So
as
we
get
down
we'll
get
down
to
767
is
our
smallest
mobile
experience
and
that
invokes
a
more
mobile,
friendly
environment.
Everything
is
touch
friendly,
and
now
we
can
see
that
our
our
menu
has
also
been
conformed
to
allow
for
a
better
mobile
experience
and
that
is
actually
driven
by
a
sharepoint
list.
That's
been
performance-tuned,
so
it's
not
actually
pulling
from
the
list
every
single
time,
the
page
loads.
The
list
gets
exported
to
JSON
confuse
me,
so
it
makes
it
very
efficient.
B
Now
the
cool
thing
about
all
that
you'll
see
and
again
just
trying
to
help
you
with
the
understanding
that,
with
some
creativity
we
can
actually
get
a
very
user-friendly
experience
is
this
is
all
done
with
no
master
page,
no
custom
master
page,
I
should
say
so
just
so,
you
know:
there's
no
wizard
behind
the
curtain.
Here's
my
site
right
here-
and
here
we
are
we're.
We're
living
in
the
custom,
are
keeping
the
existing
out-of-the-box
master
page.
B
No,
the
mega
menu
is
not
well
this
version
of
its
not
a
commercial
product.
I
actually
created
it
myself,
so
we
can.
We
can,
you
know,
feel
free
to
ping
me
later.
If
you
have
questions
about
that,
and
I
can
kind
of
walk
you
through
that
and
talk
more
about
it,
but
everything
you're
seeing
is
done
with
with
no
custom
master
page,
it's
all
being
used
in
user
custom
actions,
that's
currently
available
in
the
classic
experience
and
then
we'll
see
what's
available
in
am
on
our
experience.
B
The
area
we're
going
to
focus
on,
though
today
is
the
Quick
Links.
So
this
is
a
usually
a
compelling
story
for
business
users
simply
because
content
authors
want
to
focus
on
contents
and
they
want
to
have
the
best
possible
content
that
they
can
provide.
Usually
that
means
content.
Authors
like
to
utilize
things
like
icons,
thumbnails
images
they
want
to
be
very
visually
focused
in
their
web
application
and
be
able
to
drive
their
clients
and
their
web
consumers
to
be
able
to
utilize
and
enjoy
the
experience.
B
So,
let's
talk
through
what
a
Content
author
would
think
when
they
look
at
something
like
this,
will
they
look
at
that
and
I'll
say:
okay,
there's
a
why
and
and
there's
a
what
or
actually
there's
a
how
and
a
what?
How
am
I
going
to
get
this
information
in
there?
So
they'll
go
a
few
questions
and
I
know
it
because
I've
done
it,
how
am
I
going
to
get
the
images
up
there?
How
am
I
going
to
make
sure
they're
sized
appropriately?
How
am
I
going
to
make
sure
they're
in
the
right
color?
B
How
am
I
going
to
make
sure
they're
stored
appropriately?
How
am
I
going
to
make
sure
the
webpart
consumes
them?
So
you
can
imagine
that,
for
a
Content
author
that
perhaps
has
been
introduced
to
share
pointers
may
be
very
new
to
SharePoint
or
even
one.
That's
got
some
degree
of
experience.
It's
a
lot
of
crippling
questions
that
they
can
be
faced
with
so
before
they
even
get
to,
though
what
am
I
going
to
include
for
my
content.
B
Consumers
they're
crippled
by
the
how
how
am
I
going
to
accomplish
all
this,
and
and
so,
when
you
really
start
building
the
sites
you
want
to
think
about
what
is
it
that
I
can
contribute
to
not
only
the
content
tumors
of
the
site,
but
also
the
content
authors.
Ms
word
jaya.
Sling
comes
in
now.
What
many
people
don't
know?
What
they've
seen
as
jason
link
is
a
powerful
reference
within
a
list
view
web
part.
So
if
you
drop
a
list
view
web
part,
you
can
go
in.
B
Janet's
link
allows
you
to
associate
a
javascript
file
to
your
list
view
web
part,
and
then,
within
that
javascript
file,
you
can
override
the
visual
experience
or
the
the
interface
for
your
list
view.
It
doesn't
have
to
look
like
it
does
out
of
the
box,
but
a
lot
of
people
don't
know
is
that
you
can
actually
associate
a
j/s
link
property
to
an
individual
site
column
and
that
allows
you
to
override
the
experience
of
that
individual
site
column
in
any
list
that
it's
been
added
to
any
content
type
to
override
and
provide
a
different
experience.
B
B
Well,
we
wanted
to
provide
a
better
experience
using
j/s
link
and
again
it
behind
the
scenes
is
really
just
JavaScript,
CSS
and
HTML.
So
if
we
go
look
at
this
particular
column
for
this
I've
got
it
up
right
here,
I've
called
an
iconography
engine,
because
really,
what
we're
doing
is
we're
providing
providing
them
through
a
wizard,
an
engine
that
allows
them
to
choose
iconography.
So
we
see
this
really
behind
the
scenes.
It's
nothing
more
than
a
single
column
of
type
text
that
stores
data,
and
that's
it
nothing
more
complex.
B
There's
no
custom
field
here
going
on.
It
really
is
utilizing
complete
out-of-the-box
functionality
within
this
site
column
and
if
I
come
over
to
the
client
online
browser,
and
we
pull
up
and
look
at
that
particular
link
right
or
at
site
column
right
here,
and
we
look
at
the
jas
link
property.
Well,
okay,
great
now
we
see
much
like
we
do
with
with
the
list
view
web
part.
We
can
reference
the
jas
and
that's
what
we've
done
here.
So
what
does
that
do
for
us?
What's
the
end
result?
B
B
No
one
deletes
those
images
when
the
images
changes
how
what
needs
to
happen,
etc.
You
actually
can
override
the
entire
experience.
So
here's
our
list
right
here
and
you
can
see
something
a
little
different.
We've
got
some
icons
actually
being
played
here
and
we've
got
this
color
box
here.
So
what
does
that
look
like
when
you
go
in
well?
This
is
actually
all
driven
by
that
j
s.
This
is
our
view
form
within
the
actual
experience
within
a
list.
B
So
what
does
it
look
like
if
we
were
to
create
or
edit
an
existing
item
will
go
into
amazon
here
and
I'll
edit
an
item?
And
we
will
see
when
it
loads
something
a
little
different,
so
you
can
see
quickly
if
you
noticed
right
before
the
everything
kind
of
finished
loading.
You
saw
a
little
bit
of
that
a
little
bit
of
that
field.
So
we
saw
it
was
really
behind
the
themes,
just
a
text
box,
but
our
javascript
is
now
taken
over
and
said,
hey.
B
We
want
to
change
the
entire
experience
here
and
we
want
to
now
give
the
user
the
ability
to
select
the
icon
and
do
a
clickable
interface.
So
if
I
wanted
to
change
this
icon,
I
can
come
in
here
again
all
this
is
JavaScript
building
an
application
and
a
bubble
dialogue
that
allows
you
to
cycle
through
a
collection
of
icons
and
choose
an
icon
that
might
be
best
for
the
use
case.
B
B
Go
ahead
and
select
our
icon
up
comes
the
modal
again.
This
is
all
driven
by
the
single
JS
file
will
go
ahead
and
down
here,
and
we
can
go
ahead
and
select
the
windows
logo
and
then
an
additional
j/s
links,
I
column,
as
you
can
see,
here's
the
color
and
while
we're
focused
on
the
iconography
engine,
there
are
ways
in
which
you
can
extend
the
ability
to
do
other
thing.
B
So
again,
this
quick
link,
color,
is
just
a
text
field
in
the
back,
but
we're
over
writing
that
experience
to
now
be
able
to
provide
a
color
and
so
we'll
go
ahead
and
just
select
blue
to
make
it
stand
out
this
particular
interface,
so
the
color
is
actually
out
of
the
box
in
the
SharePoint.
This
is
referencing
it
out
of
the
box
page
within
SharePoint,
on-prem
and
online,
but
it
doesn't
mean
you
have
to
use
this
one.
We've
got
a
more
robust,
color
picker
that
I've
created
that
allows
you
to
have
shortcuts
and
all
that.
B
So
this
is
just
one
example
of
how
you
could
provide
that
experience
and
we'll
hit
OK.
We
see
now
that
we've
got
all
our
settings.
Will
hit
save
it'll,
take
us
back
to
our
primary
list
view
and
we
see
it's
an
added.
Our
icon
shows
up.
Our
color
is
now
there,
and
so
what
we'll
do
is
we'll
go
back
to
the
homepage.
B
I
will
turn
off
the
mobile
experience,
I'll
refresh
the
page,
and
we
should
see
it
showing
up
I
believe
as
the
first
or
last
item
I
think
I've
got
that
sorted,
keep
sending
yep
first
item,
so
now
we
see
it's
showing
up
and
it
from
a
Content
authorship
perspective.
You
can
imagine
the
better
experience
now
that
they're
having
to
go
through
when
they
go
in
and
select
so
now,
they're,
not
wrapped
up
in
the.
How
am
I
going
to
accomplish
this?
B
How
am
I
going
to
accomplish
that
they're,
they're
literally
able
just
enjoy
the
experience
now
by
going
through
an
interface
that
we've
custom-built
for
them,
but
is
much
easier
than
having
to
go
reference
URLs
or
potentially
worry
about
the
assets.
Now
your
question
naturally
next,
maybe
that's
great,
but
we
still
have
to
worry
about
all
those
images
right
and
and
what,
if
they
wanted
another
color?
Well,
you
may
have
noticed
a
cab
I've
got
up
here.
B
B
B
So
if
I
were
to
go
back
here
and
just
as
a
test
case,
I'll
come
over
to
our
elements,
I
will
select
this
guy
and
we'll
come
in
here
and
we'll
say
font
size
because
it
is
a
font,
will
say:
10
pixels
easy
is
now
shrunk,
small,
but
if
I
just
start
increasing
its
going
to
start
creating
a
very
big
you'll
notice,
there's
no
lack
of
quality
as
I
continue
to
increase
it.
It
just
infinitely
scales
and
you're,
not
losing
any
quality.
B
You
see
all
you
don't
see
any
of
that
noise
that
you
see
with
a
typical
image
and
and
so
you're
able
to
use
that
in
different
ways
and
different
web
parts.
It's
not
just
this
webpart.
If
you,
because
zoom
I
created
a
use
for
it
within
the
mega
menu,
in
fact,
so
they're
able
to
associate
icons
to
their
individual
menu
items
if
they
wanted,
and
so
you
can,
you
can
see
the
multi
benefits,
because
it
is
a
jay
s,
link
associated
a
sight
column.
B
That
means
any
list,
you
add
it
to
its
now
there
and
usable
and
and
then
you
just
set
up
your
web
parts
to
consume
that
data
and
apply
it
and
one
other
note,
while
it
is
using
font
awesome,
we
had
a
client.
That
said,
that's
great,
that's
really
cool,
that's
neat,
but
you
know
our
logos,
not
in
the
brand
section.
We
want
our
logo
because
it
is
a
font.
You
can
actually
create
a
custom
font.
B
B
Svg
is
that
we
want
to
use
that
are
part
of
our
brand,
and
so
we
combined
font,
awesome
and
the
custom
SDGs
into
what
we
call
a
custom
font
for
them
and
it's
still
fond
still
gets
cached
still
vector
still
all
the
benefits
that
you
get
from.
The
out-of-the-box
font
awesome
icon,
set
font
set,
but
has
a
custom
font,
so
they
can
do
whatever
they
want.
So
behind
the
scenes,
what
the
code
looks
like
and
I
know
we're
running
short
on
time.
B
Is
you
really
again
just
have
an
individual
J's
file,
so
here's
our
iconography
engine
J's
file
and
when
you
go
in
you,
can
see
I'm
fairly
adamant
about
documentation.
An
organization
I've
got
the
table
of
contents
here
that
kind
of
outlines
how
everything
is
working,
but
when
you
come
down
to
the
meat
and
potatoes
of
it
really
what
you're
doing
is
you're
associating
you're
associating
the
icon
since
I
are
extremely
the
site
column
that
we're
using
and
so
here's
my
excite
column
name.
B
While
we're
really
doing
is,
though,
we're
writing
and
we're
going
in
and
needing
to
identify
whether
or
not
I
cons
been
selected
or
or
put
in
as
a
content,
value
and
so
I'll
do
a
search,
quick
on
that
that
one's
easy
to
kind
of
consumed,
because
the
most
your
view
is
not
doing
much
right.
So
I
dynamically
load
lazy
load
that
CSS.
We
don't
want
to
overload
the
system
if
it's
not
needed.
I
can
see.
B
I've
got
some
development
stuff
here
for
for
demo
purposes,
and
then
we
set
the
the
icon,
wizard
HTML
and
then
I
return
that
and
then
that's
what
sharepoint
goes
in
and
displays
as
our
HTML
as
opposed
to
what's
out
of
the
box,
the
editing
of
it,
though
that's
that's
a
little
different
right.
So
if
we
go
back
up-
and
we
look
at
a
new
item
form
or
an
edit
item
form-
then
obviously
that
means
that
the
user
is
going
to
go
and
potentially
change
that
value.
B
So
if
we
look
at
the
new
item,
forum
will
search
for
that
and
it's
pretty
easy
to
find
or
I
could
have
found
it
via
my
table
of
contents.
Here
we
can
see
we,
we
register
the
callback
for
the
gift
value
right,
so
we've
got
our
form
con
context
and
then
what
we
do
is
being
that
we're
injecting
our
own
HTML
here
to
handle
everything.
Here's
the
display,
/
HTML
and,
of
course,
there's
additional
HTML
here.
That
is,
is
invoked
when
this
information
is
clicked
on
to
bring
up
that
pop
up,
then
we
could.
B
B
When
we
look
at
this
I'll
come
here
I'll
hover
over
this,
you
can
see
this
content
value
is
actually
what
gets
stored
so
when
they
click
on
a
button
or
our
CV,
not
this
content
value
the
actual
name
of
it,
so
in
particular,
amazon
and
store
it
as
sa
amazon
and
so
amazon,
the
actual
name
for
that
icon.
And
so
when
they
come
in
here-
and
I
will
edit
one.
B
The
easiest
way
to
associate
a
jsf
iowa-
that's
loading-
is
actually
via
powershell.
Really,
it's
not
an
interface,
that's
inside
of
sharepoint
right
now,
as
part
of
like
the
typical
interface,
but
there
is
also
some
JS
files
that
you
can
get.
You
can
load
it
in
like
a
script
editor
or
a
content
editor
directly
on
a
page
that
then
lets
you
put
in
your
field.
Name,
your
site,
column
name,
the
path
to
your
jas,
and
so
you
could
create
your
own
wizard
interface
to
actually
create
the
jf
files
within
the
SharePoint
interface.
B
The
easiest
way,
though,
to
answer
your
question
is:
really
power
shall
I
the
PowerShell
scripts
that
just
connects
to
the
local
site
or
the
sharepoint
online
site
asks
for
a
site.
Column
name
asks
for
the
jeaious
link
reference
and,
and
there
you
go,
but
behind
the
scenes
here
what's
actually
being
stored
in
that
value,
is
you
can
see
the
actual
value
associated
to
it?
And
so,
when
each
icon
is
displayed
here?
If
we
look
at
the
same
thing,
you
can
see
that
it
also
has
names
associates.
B
So
here's
our
glass
one
hour,
glass
to
our
class
3
and
so
on
and
so
forth,
and
as
we
scroll
through
each
one
of
these,
then
you
see
they
all
have
their
own
names
and
that's
how
they
get
transcoded,
then
that
information
is
stored
in
a
JSON
file.
So
when
this
gets
loaded,
the
JSON
file
is
what
we
use
as
our
as
our
key
to
the
icon
category
I
see
you
can
create
your
additional
own
custom
icon
categories,
that
categories
I'm
using
there
is
what's
awesome,
has
associated.
B
Then
you
have
a
title
and
the
actual
class
name.
So
here
we
gotta
just
and
we've
got
a
retweet,
etc,
etc,
and
the
color
picture
you
saw
is
really
not
much
different.
It's
set
up
the
same
way,
a
little
bit
more
simplistic,
but
we've
got
our
function,
names
that
get
called
from
the
same
sort
of
thing
on
our
field
name
view
display
edit
new,
and
so
that's
how
it's
driven
in
the
interest
of
time,
I'll
open
up
for
any
questions
again.
B
The
whole
point
is
that
you
know
this
is
a
way
of
looking
at
the
API,
the
hooks,
the
interfaces
that
SharePoint
provides
to
us
and
getting
creative
in
a
way
that
allows
us
to
really
enhance
the
experience
for
not
only
our
content,
consumers
about
our
content,
authors
right,
because
if
our
content
authors
feel
restricted,
then
they're
not
going
to
be
able
to
worry
about
the
what
they're
going
to
be
crippled
by
the.
How
so,
let's
see
have
you
found
a
good
way
to
CD
in
these
across
site
collections?
B
B
Let's
see,
if
possible,
you
could
put
everything
in
the
roots
like
okay,
I
was
helping
answer
that
and
reference
starting
with
root,
but
yeah.
So
so
there
is
ways
to
do
that
if
you
want
to
it's
really
just
a
reference,
so
you
saw
in
the
client
browser
here,
it's
referencing
site
collection.
You
don't
have
to
do
that,
and
so
you
could
change
how
that's
referenced.
This
sticker
case
is
an
individual
site
collection,
and
so
we
just
want
it
to
focus
there
for
consumption
purposes
of
the
J's
file.
B
A
Stuff
David
that
was
really
cool,
really
great,
to
see
and
I.
Think.
As
you
said,
a
lot
of
those
techniques
would
be
applicable
to
SharePoint
framework
projects
or
just
sort
of
client-side
development
in
general.
It's
not
obviously
j/s
link
was
what
was
used
here,
but
there'd
be
other
ways
to
sort
of
get
these
things
out
there.
So
really
cool
would
love
to
see
that
out
there
somewhere.
A
So
folks
can
can
go
check
out
those
samples
that
they're
not
already
public
so
did
want
to
circle
back
a
little
bit
on
the
questions
I
saw
on
what
I
talked
about,
AC
was
asking:
is
the
travesty
I'll
offer
connecting
to
the
container?
No,
I
do
not
believe
so,
though,
that
is
an
oft
requested
feature
from
what
I
saw
Circle
Circle
C
I
is
also
great
Travis.
I
chose
Travis
simply
because
one
it
was
the
first
one,
I
tried
and
it
works
really
well
and
to
Microsoft
has
actually
purchased
additional
build
time
for
Travis.
A
So
we
can
run
a
lot
of
stuff
in
parallel
there.
So
that
drove
the
decision
a
little
bit,
but
there's
a
lot
of
choices
out
there
circle,
there's
others
out
there,
so
I,
don't
mean
to
say:
Travis
is
better
best.
Whatever
pick
what
works
for
you,
they
all
have
different
features.
Different
capabilities
so
check
that
stuff
out
Kenny
asked
still
missing
what
Travis
is
doing
for
us.
Why
do
I
want
to
use
it?
A
This
was
answered
a
little
bit,
but
I
also
just
wanted
to
say
and
kind
of
echoing
the
responses
you
got
in
thread
that,
yes,
it
runs
our
test
for
us
and
what
it
really
does
from
my
point
of
view
is
every
time
someone
submits
the
code
instead
of
me
or
one
of
the
other
core
team
members
having
to
pull
it
down
and
run
all
these
tests
ourselves.
It
automatically
runs
all
these
tests.
It
runs
all
the
linting.
A
It
runs
to
build
the
package
and
make
sure
sort
of
all
those
basic
checks
work
because
sometimes
I
forget
to
do
that,
something
we
get
into
the
actual
dev
branch
that
might
be
broken.
Something
like
that.
So
make
sure
every
time
we're
running
at
least
the
basic
set
of
checks
and
then,
once
you
do
the
merge
running
the
full
test
suite
where
Russell
vascular
of
the
Travis
builds
run,
those
run
in
the
cloud
they
run
in
containers
inside
the
Travis
service,
exactly
how
that
is
set
up.
A
So
this
isn't
me
or
Microsoft
saying
Travis
is
the
best
everyone
should
use
it
like
I
said:
I
tried
it
first,
we
Microsoft
have
bought
some
additional
cycle
time
in
Travis
drove
the
decision
a
little
bit
so
we're
using
it
for
a
lot
of
our
stuff,
but
that's
absolutely
not
to
say
that
you
that's
the
only
choice,
lots
of
choices
out
there
with
lots
of
different
features,
and
you
should
choose
the
one
that
works
best
for
you
and
your
projects.
Travis
is
one
of
those
choices
and
the
choice
we
made.
A
So
it's
not
meant
to
be
an
endorsement
or
sort
of
a
you
know.
This
is
the
better
of
all
the
choices
so
hopefully
answer
those
questions,
unfortunately,
not
a
ton
of
time
for
open
discussion
this
week.
We
will
have
funny
time
on.
Hopefully
the
next
call
for
open
discussion.
Basa
will
be
back
as
well,
so
do
try
out
the
ga
bits
bring
your
questions
to
the
next
call.
A
Next
me
would
be
march
16th
I'm,
going
to
check
on
the
invite,
make
sure
that's
working
is
I,
think
it
works
for
everybody,
but
me
which
is
interesting,
but
so
see
you
guys
on
the
16
thanks
everybody
for
joining
and
let's
keep
the
great
conversations
going
across
the
various
social
channels
have
a
great
weekend
talks
to
everybody.
Thanks.