►
From YouTube: Architectural Discussions - March 13th, 2019
Description
Coding Standards.
https://github.com/magento/architecture/issues/77
A
A
B
There
so
I'll
start
with
the
first
one
is
national
conflict,
so
it
looks
like
it's
want
to
keep
backward
compatibility
with
all
the
wedding
standards
and
keep
all
their
under
a
magenta
baptists
static.
We
need
to
the
name
of
a
new
coding
standard,
so
I
don't
know
if
it
matters.
What's
the
name
will
be
R
or
maybe
we
can
totally
replace
it.
So
I
need
some
sites
regarded
regarding
this.
Do
we
actually
need
to
keep
all
true
set.
B
A
B
C
B
D
B
B
My
proposal
is
to
earth
pitch
based
on
this
tool,
uses
abstract
syntax
tree
analyze.
Php
code
under
the
project
uses
each
p-parcel
I
added
few
examples.
It
checks
for
class
existence,
existence
of
property
of
smaller
properties,
some
chicks
like
number
of
passed
arguments,
for
example,
its
function
required.
B
B
B
B
B
E
A
A
A
A
B
F
Yeah,
maybe
for
this
reason
we
can
use
a
little
bootstrap
I
post
it
in
the
comments
at
a
proposal.
I
think
the
New
Zealand
guy
has
a
solution
for
that.
There
is
a
little
bit
proposal
or
a
little
boot
strap
adaptor
for
PHP
stand
that
allows
to
check
the
code
without
a
DI
kanpai,
but
I
think
we
must
check
it.
Maybe
it
this
is
a
solution.
Then
we
don't
trust
around
PID
I
come
here.
Magento
di
compile.
B
A
A
A
A
B
B
A
A
A
A
F
G
E
F
F
F
We
have
some
implementation
there.
We
have
a
service
interface
for
that
and
we
have
the
caching
for
size
there.
But
if
we
set
the
size
before
in
some
point
in
our
application
and
the
size
service
or
deciced
service
facet
is
a
static
object
for
application,
then
to
check
the
found
size
is
set
by
two
two
methods
and
for
this
example,
it
can
be
a
false
positive
or
we
we
don't
allow
this
pattern
and
I
propose
to
two
possible
solution.
First,
we
can
check
if
there,
if
block
around
the
assignment,
then
it's
okay
for
cashing
reason.
D
Okay,
sorry,
looking
for
this
court
I
think
you
need
to
use
different
design
for
this
classes
in
and
you
don't
need
to
use,
set
size
method
at
all,
because,
as
I
see
when
you
set
size,
you
don't
you
won't
call
the
service
anymore,
because
you
already
set
the
size
so
probably
need
to
use
some
factory
to
create
the
this
size,
how
it's
called
size
phosphate
with
needed
size,
and
you
probably
don't
need
to
use
that
size.
Public
method
yeah
that
maybe
this
is
more
question
about
different
design
usage,
not
like
static
checks.
F
B
B
F
D
A
A
A
A
A
So
what
we
want
to
all
the
data's
I
understand
is
that
if
you
call
getter
the
visible
or
observable
mentioned
state
does
not
change.
So
if
you
call
gather
them,
you
call
another
matter
method
or
call
getter
again,
nothing,
changes,
correct,
and
in
this
case
this,
if
is
fine
the
outside,
it
doesn't
change,
so
you
will
never
get
size
which
is
equal
to
now.
You
never
see
it
so
so
yeah
I'm
trying
to
understand
you
mentioned
that.
If
there
is
an
if
and
assignment,
then
it
is
a
case
what
will
be
filing
the
test?
A
F
If
you
have
a
call
or
a
method
and
change,
it
is
or
our
static
property.
The
current
check
is
more
like
it's
more
like
which
I
check
in
for
Datak
properties.
If,
if
the
state
has
changed
over
over
a
method
or
is
a
private
or
public
changed
by
a
gap
method,
the
current
implementation
ask:
ok,
is
this
method,
a
gap
method?
Ok
then
run
the
task
for
ok.
Is
there
any
property
change
of
the
class?
This
is
the
current
implementation,
but
this
implementation
far
also
methods
like
this
one
mm-hmm.
D
F
A
F
F
F
Because
you
know
at
some
composure
dependencies
also,
it
adds
a
configuration
file
and
if
you
check
out
the
branch
depending
on
mine
branch
or
on
the
crumb
peach
peopre
a
branch,
then
we
get
a
dependency
in
the
core.
But
we
don't
verify
the
dependency
before
and
the
people
must
remove
krump
from
their
branch
before
the
branch
can
be
merged
in
Moscow
or
in
the
current
development
branch.
It
can
be
a
little
bit
slow
development,
speed
of
some
people.
They
testing
krump.
A
A
F
A
F
F
A
F
F
Yeah
we
can,
we
can
add
us
and
I
I.
Think
I
should
add
some
documentation
there
to
the
to
the
protest.
How
how
can
people
start
using
Trump
for
their
prayer
requests
and
before
are
we
merging
this
pull
request?
We
must
only
remove
one
commit
off
of
the
branch
and
hopefully
it
doesn't
ends
and
marching
how
if
we
are
merging
Trump,
but
it
shouldn't
be,
it
shouldn't
be
fine.
I.
A
What
do
you
agree
on
we'll
be
testing
it?
Maybe
I'll
test
it
without
committing
it
or
I,
don't
know
yeah.
So
I
would
like
to
have
it
because,
as
soon
as
we
committed
it,
it
will
go
to
entire
develop
to
all
developers
to
everybody.
So
we
need
to
test
it
on
a
dedicated
branch
or
maybe
not
commit
as
not
committed
code
or
something
like
that
and
test
and
see
what
are
the
results
and
only
one.
We
are
pretty
sure
we
can
merge
it.
Yeah.
F
Yeah
that
sounds
good.
Okay,
next
step
from
years
have
a
basic
integration
of
krump
in
2.3,
develop
this
krump
all
we
have
2.3
developed,
krump
s
branch
and
then
I
write
the
documentation
how
people
can
use
krump
for
for
their
prove
request,
and
then
we
get
more
more
numbers.
How
how
we
solve
the
problem
of
the
core
team,
or
it's
useful
or
mm-hmm.