Open tylers-username opened 5 years ago
Hi @tylerssn. Thank you for your report. To help us process this issue please make sure that you provided the following information:
Please make sure that the issue is reproducible on the vanilla Magento instance following Steps to reproduce. To deploy vanilla Magento instance on our environment, please, add a comment to the issue:
@magento-engcom-team give me 2.3-develop instance
- upcoming 2.3.x release
For more details, please, review the Magento Contributor Assistant documentation.
@tylerssn do you confirm that you was able to reproduce the issue on vanilla Magento instance following steps to reproduce?
Hi @tylerssn This is a good idea, but technically this is not an issue but feature request. Would you like to create Pull Request with this feature?
@okorshenko - I selected "Feature" when opening the ticket. Strange that it automated the Issue tag.
That's ok, I just want to understand if you would like to work on it or we should move it Features backlog
@okorshenko - I am open to working on this and creating a PR but it will require a number of modules to be updated and a "standard" to be put in place to ensure all future CLI commands adhere to this rule. I'd like community and engineer feedback before moving forward.
Based on the discussion in the thread and label feature request
the issue has been transferred to Magento Feature Request public repo.
Description (*)
As a developer, I'd like to see progress output for any step of a Magento Cli command that can potentially run longer than one minute.
Expected behavior (*)
A standard should be in place requiring any command to output progress for a method that will take longer than one minute to execute.
For example:
bin/magento setup:upgrade
@Installing data...
should update progress after each module data install that has completed. In the circumstance that sample data is being deployed, this can take a very long time to complete.Benefits
Knowing that the command is not stuck
Additional information
Nothing else to add.