Fix used in entities of the same type are displayed separately in delete warning

[Nazar65]

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes Used in entities of the same type are displayed separately in delete warning adobe-stock-integration#1749

Manual testing scenarios (*)

1. Add an image from media gallery to a category
2. Add another image from media gallery to a category
3. Try to delete both images together from the media gallery
4. See the delete confirmation popup

Counts of asset usages should be aggregated by entity type: Categories(2) - only one Categories item should be displayed in the warning message

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]

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

[engcom-Golf]

@magento run all tests

[Nazar65]

@magento run all tests

[sivaschenko]

Thanks for the pull request @Nazar65 ! Please take a look at my comment

[sivaschenko]

I think it would be better readable if the object will be converted to an array and then rendered using .join(', ') + '.'

[sivaschenko]

Main affected functionality is covered by MFTF tests

[Nazar65]

@magento run all tests

[magento-engcom-team]

Hi @sivaschenko, thank you for the review.
ENGCOM-8004 has been created to process this Pull Request

[engcom-Lima]

✔️ QA Passed

Counts of asset usages is aggregated by entity type

Manual testing scenario

[m2-assistant]

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