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

Apply review suggestion to the media modules #29396

Merged
merged 1 commit into from
Aug 8, 2020
Merged

Apply review suggestion to the media modules #29396

merged 1 commit into from
Aug 8, 2020

Conversation

sivaschenko
Copy link
Member

Description (*)

Removed Magento\MediaContentSynchronizationApi\Api\SynchronizerInterface
Removed try-catch block from \Magento\MediaGalleryMetadata\Model\File\ExtractMetadata::extractMetadata
Removed GetContentHashInterface
Removed DI configuration of Magento\MediaGalleryUi\Ui\Component\Listing\Filters\Options\UsedIn

Fixed Issues (if relevant)

  1. Fixes Apply review suggestion to the media modules adobe-stock-integration#1725

Preconditions

  1. Enable Enhanced Media Gallery in Stores -> Configuration -> System -> Advanced
  2. Several images are added from media gallery to Page, Product, Category, Block entities

Testing (*)

  1. Should be verified in two instances of media gallery: Content -> Media Gallery, Media Gallery opened from any wysiwyg
  2. Verify Used in filter functionality
  3. Verify Uploading the save image under a different name, saving image from AdobeStock twice (possible after removing the db record from adobe_stock_asset table) and applying Duplicates filter
  4. Verify media-content:sync command

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 Aug 5, 2020

Hi @sivaschenko. 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.

⚠️ According to the Magento Contribution requirements, all Pull Requests must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting.

🕙 You can find the schedule on the Magento Community Calendar page.

📞 The triage of Pull Requests happens in the queue order. If you want to speed up the delivery of your contribution, please join the Community Contributions Triage session to discuss the appropriate ticket.

🎥 You can find the recording of the previous Community Contributions Triage on the Magento Youtube Channel

✏️ Feel free to post questions/proposals/feedback related to the Community Contributions Triage process to the corresponding Slack Channel

@sivaschenko
Copy link
Member Author

@magento run all tests

@sivaschenko sivaschenko added Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Severity: S2 Major restrictions or short-term circumventions are required until a fix is available. labels Aug 5, 2020
Copy link
Contributor

@gabrieldagama gabrieldagama left a comment

Choose a reason for hiding this comment

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

Hi @sivaschenko, thanks for the pull request. The changes are approved.

@ghost ghost assigned gabrieldagama Aug 5, 2020
@sivaschenko sivaschenko added the Auto-Tests: Covered All changes in Pull Request is covered by auto-tests label Aug 5, 2020
@chalov-anton chalov-anton self-assigned this Aug 5, 2020
@sivaschenko
Copy link
Member Author

Changed functionality areas are covered by MFTF tests

@chalov-anton
Copy link
Contributor

✔️ QA Passed

Tested the following functionality:

  • Added images from media gallery to Page, Product, Category, Block entities
  • opened Media Gallery from Content -> Media Gallery
  • opened Media Gallery from any wysiwyg
  • work of Used in filter functionality
  • uploading the save image under a different name
  • saving image from AdobeStock twice
  • work of 'Show Duplicates' filter
  • media-content synchronization

All the changes are covered with Manual Testing Scenarios

@chalov-anton chalov-anton added the QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope label Aug 5, 2020
@sivaschenko
Copy link
Member Author

@magento run Unit Tests

@m2-assistant
Copy link

m2-assistant bot commented Aug 8, 2020

Hi @sivaschenko, 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.

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: MediaContentSynchronizationApi Component: MediaContentSynchronizationCatalog Component: MediaContentSynchronizationCms Component: MediaGalleryMetadata Component: MediaGallerySynchronization Component: MediaGallerySynchronizationApi Component: MediaGalleryUi Priority: P1 Once P0 defects have been fixed, a defect having this priority is the next candidate for fixing. Progress: accept Project: ASI QA: Added to Regression Scope Scenario was analysed and added to Regression Testing Scope Release Line: 2.4 Severity: S2 Major restrictions or short-term circumventions are required until a fix is available.
Projects
Archived in project
Development

Successfully merging this pull request may close these issues.

Apply review suggestion to the media modules
4 participants