Closed rostilos closed 3 weeks ago
Hi @rostilos. Thank you for your report. To speed up processing of this issue, make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, Add a comment to the issue:
@magento give me 2.4-develop instance
- upcoming 2.4.x release@magento I am working on this
Join Magento Community Engineering Slack and ask your questions in #github channel. :warning: According to the Magento Contribution requirements, all issues must go through the Community Contributions Triage process. Community Contributions Triage is a public meeting. :clock10: You can find the schedule on the Magento Community Calendar page. :telephone_receiver: The triage of issues happens in the queue order. If you want to speed up the delivery of your contribution, join the Community Contributions Triage session to discuss the appropriate ticket.
:white_check_mark: Jira issue https://jira.corp.adobe.com/browse/AC-12964 is successfully created for this GitHub issue.
:white_check_mark: Confirmed by @engcom-Bravo. Thank you for verifying the issue.
Issue Available: @engcom-Bravo, You will be automatically unassigned. Contributors/Maintainers can claim this issue to continue. To reclaim and continue work, reassign the ticket to yourself.
Description
During the development ( and debug process ) I caught myself many times not thinking that the functionality of dev:di:info CLI command lacks the ability to display information on di for an arbitrary area ( only GLOBAL ).
Expected behavior
Ability to define area for di information by separate parameter/option when executing a CLI command
Benefits
Improvements to the development experience
Additional information
No response
Release note
No response