Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added GetAssetIdByContentFieldInterface and implementations #29058

Merged

Conversation

gabrieldagama
Copy link
Contributor

@gabrieldagama gabrieldagama commented Jul 9, 2020

Description (*)

Added GetAssetIdByContentFieldInterface and its implementation on MediaContent modules, that will allow Adobe Stock Integration to extend MediaGallery filter functionality.

Integration tests to be added.

Related Pull Requests

https://github.com/magento/partners-magento2-infrastructure/pull/10

Fixed Issues (if relevant)

  1. Fixes Introduce Store view filter adobe-stock-integration#1463
  2. Fixes Introduce Enabled filter adobe-stock-integration#1464

Manual testing scenarios (*)

  1. ...
  2. ...

Questions or comments

Contribution checklist (*)

  • Pull request has a meaningful description of its purpose
  • All commits are accompanied by meaningful commit messages
  • All new or changed code is covered with unit/integration tests (if applicable)
  • All automated tests passed successfully (all builds are green)

@m2-assistant
Copy link

m2-assistant bot commented Jul 9, 2020

Hi @gabrieldagama. Thank you for your contribution
Here is some useful tips how you can test your changes using Magento test environment.
Add the comment under your pull request to deploy test or vanilla Magento instance:

  • @magento give me test instance - deploy test instance based on PR changes
  • @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

  • @magento run all tests - run or re-run all required tests against the PR changes
  • @magento run <test-build(s)> - run or re-run specific test build(s)
    For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names. Allowed build names are:

  1. Database Compare
  2. Functional Tests CE
  3. Functional Tests EE,
  4. Functional Tests B2B
  5. Integration Tests
  6. Magento Health Index
  7. Sample Data Tests CE
  8. Sample Data Tests EE
  9. Sample Data Tests B2B
  10. Static Tests
  11. Unit Tests
  12. WebAPI Tests

You can find more information about the builds here

ℹ️ Please run only needed test builds instead of all when developing. Please run all test builds before sending your PR for review.

For more details, please, review the Magento Contributor Guide documentation.

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR @gabrieldagama ! Looks nice! Please see my comments

@ghost ghost moved this from Pending Review to Changes Requested in Pull Requests Dashboard Jul 9, 2020
@ghost ghost assigned sivaschenko Jul 9, 2020
@gabrieldagama gabrieldagama changed the title [WIP] Added GetAssetIdByContentFieldInterface and implementations Added GetAssetIdByContentFieldInterface and implementations Jul 10, 2020
@gabrieldagama gabrieldagama marked this pull request as ready for review July 10, 2020 15:00
@gabrieldagama
Copy link
Contributor Author

@magento run all tests

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updates @gabrieldagama ! Looks nice! Please checkout my review comments

Copy link
Member

@sivaschenko sivaschenko left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for updates @gabrieldagama ! Please see my review comments

throw new InvalidArgumentException(__('The field argument is invalid.'));
}
$ids = [];
/** @var GetAssetIdsByContentFieldInterface $fieldHandlers */
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

unnecessary annotation (the type is already declared on property)

Copy link
Contributor Author

@gabrieldagama gabrieldagama Jul 17, 2020

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I will actually update the property, that is not correct, it is a multidimensional array, instead of an array of GetAssetIdsByContentFieldInterface.

Comment on lines 72 to 75
)->where(
'entity_id IN (?)',
$categoryIds
);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we simplify the algorithm and abovid additional query to retrieve the category ids?

Suggested change
)->where(
'entity_id IN (?)',
$categoryIds
);
)->where(
'path like ?',
$storeGroup->getRootCategoryId() . '%'
);

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice catch, I guess it looks way better now, thanks!

@ghost ghost assigned gabrieldagama Jul 17, 2020
@gabrieldagama
Copy link
Contributor Author

@magento run all tests

@gabrieldagama
Copy link
Contributor Author

@magento run all tests

@gabrieldagama gabrieldagama added Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Jul 17, 2020
@ghost ghost moved this from Changes Requested to Ready for Testing in Pull Requests Dashboard Jul 20, 2020
@magento-engcom-team
Copy link
Contributor

Hi @sivaschenko, thank you for the review.
ENGCOM-7858 has been created to process this Pull Request
✳️ @sivaschenko, could you please add one of the following labels to the Pull Request?

Label Description
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests
Auto-Tests: Not Covered Changes in Pull Request requires coverage by auto-tests
Auto-Tests: Not Required Changes in Pull Request does not require coverage by auto-tests

@sivaschenko sivaschenko added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Jul 20, 2020
@gabrieldagama
Copy link
Contributor Author

@magento run all tests

@sivaschenko
Copy link
Member

This PR introduces a service that is covered by integration tests, QA activities are not necessary

@sivaschenko sivaschenko moved this from Ready for Testing to Testing in Progress in Pull Requests Dashboard Jul 20, 2020
@sivaschenko sivaschenko moved this from Testing in Progress to Extended Testing (optional) in Pull Requests Dashboard Jul 20, 2020
@sivaschenko sivaschenko moved this from Extended Testing (optional) to Merge in Progress in Pull Requests Dashboard Jul 20, 2020
@magento-engcom-team magento-engcom-team merged commit 3787390 into magento:2.4-develop Jul 21, 2020
@m2-assistant
Copy link

m2-assistant bot commented Jul 21, 2020

Hi @gabrieldagama, thank you for your contribution!
Please, complete Contribution Survey, it will take less than a minute.
Your feedback will help us to improve contribution process.

@ghost ghost moved this from Merge in Progress to Recently Merged in Pull Requests Dashboard Jul 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Auto-Tests: Covered All changes in Pull Request is covered by auto-tests Component: MediaContent Component: MediaContentApi Component: MediaContentCatalog Component: MediaContentCms Priority: P2 A defect with this priority could have functionality issues which are not to expectations. Progress: accept Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Pull Requests Dashboard
  
Recently Merged
Development

Successfully merging this pull request may close these issues.

Introduce Enabled filter Introduce Store view filter
3 participants