Introduce a summarized output at the end of command execution in meta, showing the count of projects that succeeded, failed, or were skipped.
Motivation
When running commands on multiple projects using meta, users often need a quick summary of the execution status across projects to gauge success and identify potential issues. While the current sequential output is informative, a summarized view would enhance the user experience by offering an immediate overview of the operation's outcome.
Example
Imagine a scenario where a user has 10 projects defined in the .meta file. They run a meta yarn install command. At the end of the command execution, meta could display:
Execution Summary:
9/10 projects finished successfully
1/10 projects had errors
This immediate feedback is invaluable for users, especially in scenarios with a large number of projects, as it prevents scrolling through long logs to determine which projects had issues.
Attachments: (Here, you can drag and drop any mockups or additional supporting documents you might have.)
Once you've reviewed and are satisfied with the content, you can post it to the relevant project's issue or feature request tracker!
š Feature Proposal
Introduce a summarized output at the end of command execution in
meta, showing the count of projects that succeeded, failed, or were skipped.Motivation
When running commands on multiple projects using
meta, users often need a quick summary of the execution status across projects to gauge success and identify potential issues. While the current sequential output is informative, a summarized view would enhance the user experience by offering an immediate overview of the operation's outcome.Example
Imagine a scenario where a user has 10 projects defined in the
.metafile. They run ameta yarn installcommand. At the end of the command execution,metacould display:This immediate feedback is invaluable for users, especially in scenarios with a large number of projects, as it prevents scrolling through long logs to determine which projects had issues.
Attachments: (Here, you can drag and drop any mockups or additional supporting documents you might have.)
Once you've reviewed and are satisfied with the content, you can post it to the relevant project's issue or feature request tracker!