►
From YouTube: Adobe Stock Integration public meeting 14th Jan 2020
Description
Adobe Stock Integration public meeting 14th Jan 2020
A
A
That
is
a
big
pool
request
until
on
running
and
provide
comments
for
Dobis
terkoz's
and
finally,
it
was
finalized
and
merged.
It
provides
just
awesome
things:
lots
of
granulated
commands
for
operating
Adobe
stock
assets.
So
right
now
we
don't
only
have
the
repositories
for
assets,
category
creator,
but
the
commands
as
well
and
code
looks
much
better.
So
thanks
for
finalizing
this
Alex,
that
was
great
addition
and.
A
Another
pull
request
that
was
merged
just
today
is
the
fix
for
two
bucks
in
the
first
one,
his
quantity
of
images,
an
account
profile
was
not
updated
when
image
was
a
licensed
right
now,
it's
updated
and
licensed
in
Save
button
he's
not
protected
from
multiple
clicks.
So
basically
the
fix
was
just
update,
the
user
quwata
when
the
image
was
licensed
and
as
for
a
license
and
save
this
issue
was
I
believe
was
fixed
earlier.
It
was
already
fixed
as.
A
C
It
ended
up
that
I
mean
the
issue
ended
up
being
something
that
I
think
we
can
expect
to
happen
from
time
to
time
with
functional
tests.
Is
that
you
can't
use
to
sign
in
had
problems,
though
we
needed
to
change
the
password,
because
those
are
Adobe
account
requirements
needed
to
associate
a
telephone
number
with
the
account,
because,
again,
those
are
so
like
nm
FTF,
unless
we
have
some
magical
stub
of
all
the
third
party
API
as
we
use.
C
These
are
the
kinds
of
problems
we'll
have
to
encounter
every
now
and
then
so
that's
something
to
keep
in
mind
other
than
that
friendly
reminder
that
for
failing,
M
FTF
tests,
if
you
expand
the
after
failure
logs
on
Travis
you'll,
get
links
to
screenshots
at
the
moments
of
failure,
so
something
I
added
in
this
pull
request
is
explicitly
taking
a
screenshot.
Even
when
a
test
passes
when
MFT
EFT
is
signing
into
IMS,
but
I
think
that's
helpful
for
just
continuously
verifying
that
everything
is
okay
with
IMS
tests.
A
A
A
A
I
would
like
to
mention
that
right
now,
as
we
switched
from
as
we
created
the
media
gallery
models
in
in
magenta
core,
and
we
moved
our
components
to
imagine
to
repository,
we
also
have
a
lot
of
pull
requests
related
to
other
bistec
integration
in
the
magenta
to
repository.
So,
as
you
can
see,
we
we
have
six
open.
That
is
not
the
precise
data.
A
Basically,
the
additional
check
was
added
for
the
piece
validation
and
the
pull
request
also
includes
adjustment
tests
for
those
who
are
interested
in
covering
his
just
judgment,
test
component,
our
components.
Adjustment,
as
you
can
take
a
look
on
this-
that's
probably
it
for
the
poor
requests.
What
I
wanted
to
mention
right
now?
We
have
issues
with
the
static
tests.
Our
static
tests
are
failing
because
of
root
Composer
issue.
A
Basically,
we
added
two
new
models
that
are
media
gallery:
UI
and
media
gallery
I
a
P,
I
and
I
haven't
yet
added
them
to
the
blacklist
on
our
integration
on
our
infrastructure
repository,
so
the
static
tests
as
they
were,
based
from
the
beginning
design
for
Magento
core
modules.
They
are
expecting
all
the
modules
in
the
installation
to
be
in
there
to
be
mentioned
in
the
project
root,
Composer
JSON,
that's
right,
but
a
surveilling
and
basically,
we
just
need
to
add,
add
them
to
blacklist
to
fix
these
failures.
A
I
have
created
reporter
questura
infrastructure
and
it
should
be
merged
soon,
just
waiting
on
the
queue
once
it's
done.
The
static
tests
will
be
green
also,
as
we
have
added
the
new
modules
to
the
integration.
There
were
some
failures
of
other
tests,
but
they
were
fixed
by
Alex.
Thank
you
very
much
Alex
for
that.
So
right
now
say
you
should
be
green.
B
A
D
A
D
So
for
that
we
want
the
ability
for
the
business
users
to
specify
parameters
with
which
the
image
rendition
should
be
created
for
the
particular
use
of
the
asset
in
the
content.
So,
like
short
way
of
saying
that
we
don't
resize
the
original
image,
so
the
original
image
stored
in
the
media
gallery
remains
in
high
quality
and
we
create
conditions
based
on
the
parameters
that
user
provides
by
user
interface
and
use
the
image
rendition
in
the
content.
D
So,
basically,
in
all
of
the
places
where
the
media
gallery
is
connected
to
the
to
the
admin
panel,
so
I
still
need
to
confirm
all
that
places.
So
like
the
brief
list
is
the
catalog
image
in
the
category
page
CMS
images
like
CMAs
page
block,
the
name
is
block
that
is
known
as
a
banner
all
of
the
product
content,
no
I'm,
not
sure
if
the
media
gallery
is
connected
to
the
newsletter
template.
D
So
this
is
something
that
need
to
kind
of
validate
and
confirm
what
is
the
full
list,
but
in
all
of
that
areas,
when
user
tries
to
insert
the
image
and
use
the
image
from
the
media
gallery,
users
would
be
able
to
specify
the
image
rendition
parameters
separately
for
the
desktop
and
mobile,
so
that
will
allow
to
kind
of
optimize
the
image
for
each
breakpoint
use.
So
the
initial
parameters
that
we
want
to
start
with
is
the
image
width
and
image
compression.
D
The
user
also
would
be
able
to
select
the
conditions
that
has
been
created
before
to
use
with
the
viewport
and
by
default,
the
image
image
size
should
be
taken
from
their
current
image
size.
So
it's
the
field
shouldn't
be
empty
and
user
can
specify
either
width
as
initial
parameter.
So
in
that
case
the
height
would
be
automatically
calculated
and
there
should
be
also
an
option
to
specify
the
height,
and
in
that
case
the
width
would
be
automatically
calculated
based
on
based
on
the
height
parameter.
D
D
So
as
a
result,
when
user
confirms
the
action
they
would
see
that
the
share
set
is
generated
that
corresponds
to
the
provided
parameters
and
when
the
content
was
the
image
is
saved.
User
would
see
that
different
images
are
displayed
on
different
viewports.
So
this
is
the
initial
scope.
Unfortunately,
I
will
have
mock-ups
to
share
yet,
but
that's
something
that's
coming
any
questions.
A
D
Yes,
that
scold
doesn't
cover,
like
the
scope
of
this
particular
story,
doesn't
cover
the
viewing
the
renditions
in
the
media
gallery
yeah,
but
thanks
for
minding
the
transitions
are
not
the
duplicates
of
the
initial
image.
The
idea
is
that
in
the
media,
gallery
user
would
see
still
the
higher
resolution
image
and
it
would
be
possible
to
see
the
renditions
that
are
associated
with
that.
A
high
quality
image
in
the
media
in
the
new
media
gallery
UI,
but
it
wouldn't
create
a
duplicate
of
the
image.
D
A
D
Call
that
condition
not
the
image
like
not
to
confuse
this
with
two
completely
different
instances,
because
the
image
is
the
one
that
users
see
in
the
media
gallery
as
the
entity
transition
is
just
a
different
parameter
of
the
same
image.
Basically,
though,
it's
like
technically
on
the
file
system,
obvious
that's
different
image,
but
it's
not
the
different
image
for
the
user
and
we
shouldn't
position
that
as
a
different
image.
A
C
A
A
D
No,
so
again,
the
idea
is
that
whatever
image
is
downloaded
from
stock,
we
store
it
in
initial
high
quality.
We
don't
change
that,
so
we
always
have
the
source
of
that
high
quality
image
and,
for
example,
if
you
created
a
rendition
and
use
that
transition
of
that
image
in
the
content-
and
you
changed
your
mind
and
decided
that
you
need
a
better
magician.
B
A
A
A
And
and
decides
which
external
service
could
we
use,
or
should
we
go
with
an
internal
implementation
if
you
know
any
kind
of
any
good
services
that
provide
ability
to
resize
compress
or
even
do
more
stuff
with
images,
just
the
more
of
features
in
the
services
I
think
that
the
better
it
will
be
for
any
possible
future
extensions
or
improvements.
Just
let
us
know.
A
E
No,
no
just
this
one,
because
I
started
the
implementation
on
this
top.
We
discussed
previous
year.
Yes,
and
currently
the
work
is
in
progress
and
I
will
try
to
update
you
there
things
as
soon
as
possible,
because
today
also
picked
some
stuff
for
them.
Mm-Hmm
comment
approach,
pull
request
so
hopefully
this
week,
I
may
have
made
a
great
progress
for
this,
so
I
will
implement
it
in
a
way
and
a
separate
module
which
will
be
easy
to
replace
the
our
other,
the
stock
client.
E
A
Right
now,
we
still
have
a
lot
of
tasks,
some
small
box
from
or
the
functionality
from
the
previous
implement
previous
milestone
of
other
bistec
integration,
and
we
also
have
the
teachers
in
the
backlog
for
the
current
milestone.
So
in
case,
let's
check
them
out
in
case
you
have
any
questions
on
the
issues.
Just
let
me
know
I
will
help
you
to
understand
if
anything
is
not
clear
and
help
you
with
the
basic
approach
to
start
the
fix
or
start
the
implementation
of
the
feature
you
can
find
me
in
slack
as
usual.