►
From YouTube: Magento Architectural Discussion -- September 5, 2018
Description
Topics:
- Deprecate JS Component Mixins (@DrewML)
- Demo of remote Magento CLI, as part of modularity work (Anton Kril)
Meeting minutes: https://github.com/magento/architecture/wiki/September-5,-2018
A
A
Cool
all
right,
so
the
one
topic
that
we
had
to
discuss
today
was
the
proposed
deprecation
of
j/s
component
mix-ins.
It's
worth
noting
that
this
is
a
separate
concept
from
requirejs
mix-ins,
which
are
what
most
people
use
to
augment
front-end
functionality
when
they're
writing
a
plug-in
or
a
module.
That's
trying
to
touch
the
client
side
in
this
case,
javascript
component
mix-ins
are
a
similar
but
different
thing.
So
the
first
reason
that
we're
advocating
for
deprecation
of
these
is
that
they
have
an
API
surface.
A
That's
just
gonna
be
confusing
to
most,
especially
because
of
the
fact
that
they're
currently
undocumented,
and
only
used
in
one
place
in
core.
So
an
example
of
the
JavaScript
component
mixin
that
most
of
us
should
be
familiar
with.
Is
you
just
define
a
standard,
AMD
module
and
you
return
a
function
that
takes
what
the
export
was
from
the
original
module
that
you're
you
know
basically
trying
to
intercept,
and
then
you
can
either
return
a
new
object
from
here.
You
can
return
the
existing
one
mutated.
A
You
know,
basically
anything
you
want
there
and
a
j/s
component
mixin.
It
has
a
similar
but
slightly
different
signature
to
it.
So
it's
still
an
AMD
module,
but
it
returns
a
function
that
takes
in
a
config
for
that
particular
J's
component
and
then
the
selector
for
where
it's
gonna
instantiate
itself
in
the
dub.
So
this
is
the
configuration
and
the
selector
that
come
from
B
X
may
join
it
or
the
data
may
join
it
directives
that
are
rendered
from
the
server
side.
A
So
I
did
a
you
know.
A
super
unscientific
survey
of
a
few
people
in
the
major
on
China
and
I
believe
the
general
channel
on
the
community,
slack
and
I
didn't
actually
find
anyone,
including
people
who
do
trainings
on
our
JavaScript
components.
That
was
aware
that
this
feature
there
are
multiple
people
internally
as
well,
who
worked
on
the
creation
of
jazz
components
and
they
weren't
aware
that
this
functionality
existed.
A
So
the
real
reason
we're
advocating
for
its
removal,
though
more
than
just
a
confusing
API
surface
or
a
kind
of
redundant
API,
there's
also
concerns
with
it
too.
Specifically,
we
are
using
it
today.
Only
for
setting
up
the
magnifier
on
products
photos
on
the
products
page
out
of
the
box.
I've
had
a
few
escalations
regarding
there's.
Also
a
pretty
long
kit
I've
issued
about
the
fact
that
product
page
photos
too,
even
when
they're
clap,
even
when
you
have
a
warm
cache
on
the
client
side,
still
takes
several
seconds
from
the
time.
A
The
documents
ready
to
render
there's
a
few
root
causes
to
that
that
I've
documented
separately,
but
one
of
them
has
to
do
with
the
way
these
Jazz
components
sort
of
expose
themselves,
basically
because
the
the
JavaScript
components
that
we
have
on
like
check
out
asynchronously
load
themselves
and
then
render.
We
aren't
actually
aware
of
the
fact
that
this
jazz
component
mixin
exists
or
needs
to
be
fetched
and
executed
until
we've,
officially
UI
component
or
a
jazz
component.
It's
come
back
in
we've
evaluated
it
and
we've
seen
that
it
has
this
additional
configuration.
A
We'd
probably
want
a
little
bit
better
of
an
idea
of
who's
using
this,
but
so
far
with
our
unscientific
research
on
it,
it
seems
like
this
would
be
pretty
low
impact
for
most
people
and
making
this
change.
The
only
other
change
we
would
require
in
court
is
that
we
would
have
to
change
how
the
magnifier
works
with
the
dorama,
but
this
is
a
good
thing.
Excuse.
B
A
A
A
A
C
A
A
A
That
was
one
thing.
I
wanted
to
do
also
because,
like
I
said
it
was
unsigned,
but
the
the
feedback
I
got
from
the
community
so
far
was.
Why
is
that
there
or
we
had
no
idea
that
was
there
so
I'll
check
the
marketplace
for
sure,
but
I
think
it's.
It's
probably
likely
that
if
we
don't
get
feedback
from
anyone
in
the
community,
that's
seen
it
and
we
don't
find
it
in
marketplace,
then
we'll
probably
be
safe
on
them.
A
Pretty
low
risk
removal.
If
we
do
find
an
American
place,
we'll
have
to
document
the
use
cases
that
they're
using
it
for
and
see
if
it
was.
Maybe
they
didn't
know
that
there
is
a
different
way
or
see
if
this
API
surface
actually
is
you
know,
adding
extensibility
that
can't
be
done
in
other
ways,
it's
so
far.
That
doesn't
seem
to
be
the
case.
Make.
C
A
Cool,
so
in
that
case,
feel
free
to
leave
any
additional
feedback,
even
if
you're
just
saying
that
you're,
okay
with
it
egor,
probably
worked
well
just
to
go
in
there
to
leave
your
comments
without
scanning
through
marketplace.
That
way,
it's
not
something
that
we
forget
about
or
something
that
gets
lost.
And
besides
that
we
are
out
of
content
for
today's
meeting.
Did
anyone
else
have
anything
last
minute
that
they
didn't
get
a
chance
to
add
that's
worth
discussing.
D
A
D
D
D
A
Yeah
these
to
them
needs
to
be
merged,
and
besides
that,
there's
they're
still
released
a
few
in
here
that
don't
have
much
feedback
yet
that
we
should
discuss
I,
believe
this
one
pretty
small
yeah,
so
I'm
super
small.
So
everyone
should
be
able
to
look
at
that.
It
might
be
worth
at
least
with
mfcflts
on
it
too.
So
I'll
send
it
over
to
penguins
and
see
if
they
have
any
feedback.
B
D
A
D
D
D
D
If
you
didn't
feel
deploy
in
multiple
instances
of
Magento,
it
becomes
hard
to
manage
it
especially
I.
Have
this
I
believe
that
people
usually
shouldn't
shouldn't
need
access
to
SSH
access
to
magenta
instances
web
application
instances
so
and
from
that
perspective,
in
magenta
tool
is
not
very
convenient
right,
so
just
quickly
demonstrate.
D
So
you
see,
I
have
I,
have
different
ports
like
Magento
admin,
Magento
epilogue
DB
magenta
kept
working
so
check
out
baby
check
out
in
so
those
are
different
instances
of
Magento
and
the
tool
bin
magenta
to
it.
It
assumed
that
an
instance
works
worker
that
magenta
instances
is
local
to
you,
use
on
your
local
machine,
for
example.
If
you
want
to
do
setup
upgrade
you
have
to
go
or
set
up
install.
It
have
to
go
SSH.
That
instance.
B
D
D
It
shows
me
that
I
have
two
instances:
one
catalogue,
one
checkout
and
I
can
yeah
I
can
choose,
which
instance
I
work
with
now
and
then
I
can
load
the
metadata
from
from
that
context,
I
can
add
a
context,
so
I
can
add
different
instances
of
Magento.
That
I
will
be
managing
by
that's
local
and
the
important
thing
key
that
these
come
under.
These
commands
are
part
of
this
to
all
the
other
commands
here
that
you
can
see
they
met.
D
D
So
something
when
something
went
from
here,
but
so,
but
me
so
context.
Sleep
I
have
context
this,
but
so
my
current
context
is
checkout
and
if
I
do
Magento
set
up
set
up
operate,
the
command
is
broken
because
the
instance
is
broken,
but
you
can
see
that
it
executes
come
out
in
command
remote.
So
my
opinion
to
be
very
this
tool
will
be
very
convenient
for
like
when
you
have
to
manage
multiple
instances.
D
A
D
D
D
If
you
work
is
magenta
to
you
know
that
it's
pretty
slow
because
it
takes
so
you
see
that
the
the
jumping
since
we're
doing
some
problems
with
loading
stuff,
I
guess
it's
a
this-
is
a
response
from
the
mode,
but
the
bandit
added
benefit
of
having
this
to
walk
away
that
that
all
commands
are
very
lightweight.
So
you
don't
you
don't.
You
know
that
Symphony
console
command,
Symphony
console
component
is
built
the
way
that
all
commands
or
all
command
classes
are
instantiated.
D
When
you
run
that,
even
if
you
want
to
just
list
commands
it,
it's
instantiates
or
all
classes,
so
it's
very
slow
and
you
can
see
that
this
tool.
The
added
benefit,
is
that
it's
very
fast
because
it
doesn't
accentuate
automatically,
has
proxies
to
the
movements.
So
just
a
quick
update
from
the
thing
that
I've
been
playing
with
it.
D
At
some
point
yes
and
oh
yeah,
I
still
haven't
published
so
there
is,
there
is
removed.
Pull
request
is
proposal
I'm
working
on
the
revised
version
of
the
proposal,
and
yes,
that
is
part
of
the
tool
of
the
tool
that
will
have
to
do
now,
won't
be
a
walk
off
issue.
So
the
idea
is
that
for
it,
for
the
developer
that
works
with
agenda
just
an
agency
as
an
agency
developer
I
have
all
of
this
multiple
magenta
instances.
I
want
to
manage
them.
D
I
want
to
be
secured
all
this
operation,
so
this
tool
allows
me
to
just
install
it
on
my
local
machine,
one
instance
of
the
tool,
and
it
can
work
with
different
versions
of
magenta,
because
it
will
go
and
read
the
metadata
information
from
those
instances
and
based
on
version
side.
You
guys
don't
have
to
have
to
this
tool,
because
I
want
this
to
be
single
to
it.
C
D
Posted
the
link
not
here
to
just
I
just
there,
this
thing
I
yesterday,
it's
it's
not
I,
can't
say
it's
finished,
but
it's
it's
working,
I
actually
use
it
already
for
myself,
so
and
I'll
be
out
committed
to
their
posit
area
of
modularity.
That
I
already
shared
this
at
the
supernal
or
projects
just
sharing
the
technology.
Great.
Thank
you.