►
Description
Magento Contribution Day, Kharkiv
C
D
Now
I
can
start
so
since
I
was
not
contributing
for
a
long
time.
I
started
to
for
I
think
quite
easy
task,
which
is
about
adding
some
more
integration
tests
for
the
new
sidetrack
of
MSI,
the
pic
from
store,
I,
know,
I,
don't
know
whether
I
can
call
it
sidetracked.
So,
however,
so
first
of
all
it's
about
the
social
selection
algorithm
for
which
is
postcode
based
and
therefore
I
created
a
few
additional
fixtures.
D
First
of
one,
one
of
them
was
inventory,
given
name.
So
this
is
because,
in
the
normal
way,
Magento
proves
all
this
data
from
Google
apparently,
and
therefore
we
need
Google
API
key.
So
in
order
to
simulate
this
I
provide
a
few
addresses
for
Germany,
Italy,
France
and
us
in
our
database
as
a
fixture,
so
that
I
can
test
everything
and
I
create
an
additional
fixture
for
sources,
because
our
current
sources
does
not
have
addresses
in
there
because
they
are
optional.
D
D
So
after
doing
this
stuff,
the
test
was
quite
easy
and
the
tests
provide
me
also
an
issue
so
I
detected
a
fountain
issue,
which
is
there,
which
I
also
fixed
with
this
pool
request.
So
the
distances
was
not
ordered
currently
in
the
right
way
and
also
an
open
question
which
we
need
to
clarify
afterwards,
because
currently
this
algorithm
also
not
ignore
disabled
sources.
Probably
it's
something
we
need
to
add
there
Oh
so.
D
Sources,
there's
one
disabled,
ter
and
currently
I
got
this
results
in
this
sort
order
and
it
seems
to
be
correct
so
far,
but
probably
because
they
are
not
shown
in
the
front
end,
so
they
are
filtered
somewhere
else,
but
probably
in
order
to
improve
the
performance
of
this
algorithm
should
also
be
disabled.
But
already
here
you
know
very.
B
Well,
what
I
propose
to
do
right
now,
so
I
propose
to
mark
this
test
incomplete
in
the
particular
part
where
you
dealing
with
disabled
sources
and
create
the
dedicated
task
on
MSI
github
to
say
that
this
box,
because
probably
you
your
test
so
show
us
about
so
that
say
that
this
box
should
be
fixed
at
and
and
as
soon
as
it's
going
to
be
fixed
that
there's
going
to
be
uncommented
so
that
it
should
pass.
So
we
really
do
like.
D
D
B
A
E
You
see
my
screen
phone
get
up
now:
yeah,
okay,
cool
yeah
small
fix,
but
it
was
a
really
strange
back
or
behavior
before
the
park
was
founded
by
the
UAE.
We
had
a
problem
with
calculation
there.
If
you,
the
problem
was,
if
you
have
nine
orders,
nine
small
orders
and
the
last
order
can
be
placed,
but
it
should
be
enough
in
stock
and
first
part
was
your
discussion
with
Igor
hey
how
we
can
solve
this
floating
problem
and
we
end
with
PC
compare
and
today
what
I
do
I
implement
the
test
case?
E
What
I
posted
there
is
a
screenshot
from
today.
It
like
this
was
thought
implementation
with.
If
the
error
and
the
new
implementation
with
the
correct
behavior
here,
I
fara
Phi
the
park
and
fixed
back
with
a
new
implementation.
This
is
what
I
do
today:
it's
not
big,
but
it
takes
some
horse
to
find
out.
B
F
A
F
F
Test
just
to
start
I
work,
so
I
created
these
tests
to
make
sure
if
I
can
find
it
yeah.
It
should
be
this
one
created
this
test
to
make
sure
that
my
basically
was
backward
compatible
with
parents.
Vation
then
I
change
the
implementation
by
simply
reading
all
the
information
I
need
from
the
de
based
and
computing,
then
them
in
a
single
in
a
single
cycle
and
plus
I,
also
added
a
couple
of
missing
tasks
for
the
source.
B
H
A
A
I
Okay,
so
now
I'm
going
to
tell
about
I
think
the
most
casual
full
request,
which
happened
today,
because
I
just
few
days
ago,
I
had
detected
that,
in
order
repository,
you
can
add,
cannot
use
joining
of
extension
and
tributes
and
just
today,
I
discovered
that
it
was
actually
fix
it,
but
fix
it
in
any
other
way.
Version
except
2.3
Magento.
So
today,
I
have
created
a
forward
port
to
fix
this
issue
with
extension
attributes
for
order
entity
also
in
203
budget.
C
A
I
B
A
C
J
H
J
Fixed
contain
fix
related
to
much
ender
finger,
object,
manager,
complete
config
file,
it's
related
because
we
have
our
air
place.
Instead,
our
air
place
recursive.
So
in
this
case,
when
magenta
tried
to
not
both
compete
in
general
and
administer
ml
inch,
demo
you'll
replace
general
config
method,
structure
and
I
had
two
tests.
One
test
check
if
we
merge
token
fix
the
same
class
name,
it's
related
to
global
scope,
and
that
means
code.
It's
about
my
mark
fix
in
the
second
test
case.
J
It's
about
another
bug
issues
when
we
have
two
configs
on
the
same
class,
but
one
class
has
slashed
that
the
trust
should
be
corrected
and
the
second
complete
FS
/.
So
much
indeed,
margin
need
twice,
and
in
this
case
they
replace
overwrite.
The
second
change
replace
the
car.
The
thing
is,
you
say
something.
A
B
J
G
The
previous
I
had
comment
on
previous
comment
on
previous
bug
fix,
so
this
behavior
was
as
divined
it
by
design
with
an
area.
Config
is
merged
and
between
areas
config
is
replaced
and
we
had
many
discussions
about
it
and
the
reason
why
it
has
done
so
to
allow
to
remove
it
was
because,
if
you,
if
you
do
match
there,
is
no
possible
possibility,
if
you
do
array
replace
the
cursor,
it
was
I.
G
Think
if
I
remember
correctly,
the
problem
was
that
you
wouldn't
be
able
to
remove
some
keys
from
a
race
if
something
is
configured
in
global.
So
there
is
a
slight
conceptual
difference
between
area
inheritance
and
the
area
sequence
so
admonition
out
conceptually
the
does
not
does
not
inherit
from
global.
It
replaces
a
global.
So
that's
what
that's
why
it
was
done.
G
J
To
what
you're
talking,
because
we
can
do
because
it's
replaced
on
the
nest
and
data,
it's
not
replaced
all
as
a
data
from
global
scope,
so
you
shoot
twice
in
favor
in
same
way,
so
we
should
on
first
level
we
have
extends
from
the
global
scope,
but
when
we
tried
to
put
something
in
pull
object
to
pull
my
service
inside
foreign,
for
example,
that
I
provided
for
dreams,
I
can
do
it
in
my
scope,
for
example,
for
admin
one
for
front-end.
Another
solution,
yeah.
G
G
E
G
Two
files
of
two
different
modules
in
a
single
area,
but
when
an
area
replaces
an
admonition,
Mallory
replaces
global
config.
The
decision
was
made
to
replace
whole
value
and
the
reason
I
said
to
support
the
scenario
of
removing
values
from
array.
I'm,
not
sure
how
how
how
popular
that
scenario
is
I,
don't
have
strong
opinions
on
any
of
the
options
here,
but
what
I'm
saying
is
that
the
decision
needs
a
bit
wider
discussion
and
if,
if
you
guys,
if
that's
something
you
guys
want
to
do,
let's
do
that.
No
problem
it
just.
G
I'm
sorry
I'm,
sorry
for
for
that
and
I'm
I'm,
saying
I'm,
not
saying:
let's
reject
this
pull
request,
what
I'm
trying
to
say,
let's
not
reject
this
pull
request,
let's
keep
it.
Let's
do
and
it's
actually
it's
a
very
good
thing
that
that
this
question
was
raised
again
because
probably
someone
contributed
someone
reported
discussion,
github
and
it
was
through.
Actually
that
wasn't
didn't
participate
in
the
trash.
G
But
what
I'm
saying
is
that
conceptually
we
discussed
a
couple
times,
I
don't
have
strong
opinion
either
way
works
to
me
that
then,
then,
what's
important
for
me
that
it
should
be
convenient
and
intuitive
and
ergonomic
for
developers
for
community.
So
if
Y,
the
discussion
comes
to
conclusion
that
this
should
be
changed.
Let's
change
it.
My
only
my
only
interest
here
that
the
decision
it's
a
bit
wider
discussion.
So
what
I'm
saying?
Let's
in
addition
to
this
pull
request,
can
you
clear
a
proposal
that
would
be
and
proposal
for
people
to
take
participate
in
discussion?
G
We
can
do
a
poll
or
you,
someone
can
do
a
poll.
Alex
lalume
can
do
a
poll
on
on
Twitter
or
eager
managua,
and
let
just
just
let
just
make
it
a
bit
wider
discussion,
because
there
was
wider
discussion
couple
years
ago,
I
think,
like
two
years
ago
there
was
discussion
about
this
question
and
the
decision
was
made
to
keep
it
like
this.
If
you
want
to
change
it,
let's
change
it
to
just
you:
okay,
I'm,
repeating
myself,
make
sense.
C
A
K
K
K
K
A
K
A
A
K
K
K
A
B
A
Not
really
I
mean
this
functionality
basically
is
not
used
very
much
it
to
itself.
So
there
is
an
implementation
for
that,
but
in
this
case
that's
more
data
which
user
needs
to
check
that
the
data
that
he
sent
I
mean
that's
not
like
required
to
check
it.
It's
only
up
to
you
use
cases
or
business
cases.
If
you
want
to
do
it,
then
you
can
do
it
yet.
That's
basically
only
the
information,
yeah
and.
A
Cool,
thank
you.
Basically,
the
yeah
I
would
not
say
the
very
small
I
would
like
today
that
not
so
many
people
basically
know
what
they
think
impetus
and
doing
the
small
stuff
people
just
learning
the
project.
That's
that's
really
really
cool
and
now
I'll
go
to
the
last
one.
Last
for
here
at
the
stopper.
You
also
into
a
couple
of
change,
basically
I
guess,
which
will
represent
boss
sport,
but
only
one
yeah,
both.
C
H
H
After
yep,
so
first
of
all,
the
test
was
also
was
was
a
small
request
and
it's
related
to
changing
our
ACL
rules.
We
use
the
ACL
of
magenta
import-export
and
right
now
we
decided
that
we
will
use
our
own
import
service
resource
and
yeah
I
also
changed
it.
The
vibe
Web
API
X
naught
for
all
our
weapon
endpoints.
So
in
the
next
pull
request
is
about
our
new
endpoint
sorry
for
interruption.
B
I
I
just
thought,
based
on
your
screen,
where
you
have
like
set
uie
ego
or
Mina
hello,
something
like
that.
Yeah
you'll
see
it
later,
just
I
I,
just
I.
Don't
have
one
idea,
which
came
to
my
mind
that
we
don't
have
a
verification
that
they
well-qualified
UUID,
provided
so
that
UUID
supposed
to
be
128
bits
and
it's
supposed
to
to
correspond
some
format.
And
if
now
we
are
eligible
to
set
any
string.
So
this
is
potentially
not
you.
You
AE.
H
Basically,
okay,
yeah
yeah,
it's
a
good
point,
but
right
now
we
just
created
like
like
an
interfaces
with
without
implementation
validation.
This
yeah,
we
even
didn't,
have
a
reason.
It
didn't
have
a
resource
model,
so
yeah
we'll
take
into
account.
Thank
you
for
your
comment,
yeah
so,
and
we
have
a
new
new
end
point
and
that
we
will
start
our
import,
an
interface
for
this
and
we
use
the
neural
source
and
yeah
implementation.
H
H
Iger,
sorry
that
I'm
using
your
private
date,
I,
don't
know
I,
don't
have
a
bit
copyright
for
a
girl
named
okay
yeah,
so
we
have,
but
I
also
wanted
to
mention
that
we
have
here
best
import,
config,
object
that
have
several
in
profile
UID
because
ever
and
another
properties-
and
we
have
here
another
interface
for
for
them-
for
forcing
yeah
for
it
and
yeah.
You
just
get
arson
setters
and
in
the
constants.
Oh,
that's
it
that's!
What
I
did
today
I.
A
A
A
A
A
The
issue
wait:
why
there's
a
label
then
for
the
issues?
Okay,
I'm
confused,
but
if
it's,
if
it's
an
issue
so
yeah,
that's
a
that's
an
issues
and
that's
a
poor
request.
You
know
that's
a
mixed
one.
If
you
filter
by
level
you
get
a
nice
one,
then
you
get
n.
We
still.
We
have
only
one
pool
request
for
today:
well
edit
the
probe
to
the
cartons
request:
key
is
0
or
less
than
0.
A
A
But
okay,
yes,
we
will
a
bit
later
I'm,
just
thinking
Aryan.
We
can't
add
to
the
shopping,
cart
and
my
amount
less
than
zero
and
yeah,
and
there
is
also
a
test
written
for
that
which
is
also
quite
nice,
so
deaths
then
from
poor
request
for
this
contribution
day.
That's
all
did
anybody
count?
How
many
of
that
did?
He
have
three
six.
A
B
So
if
it
like,
if
you
the
most
important
for
us,
that
the
that
this
kind
of
event
to
be
joyful
for
you
and
just
don't
hesitate
to
tell
us
more
like
because
if
it
if
it
makes
sense
to
run
more
often,
this
kind
of
events-
maybe
maybe
we
know
like
the
community
engineering-
will
not
go
anywhere
and
guys
from
like,
like
Alex
like
Ricardo
and
Vadim
will
be,
will
be
hosting
all
that
events
instead
of
us.
So.