-
-
Notifications
You must be signed in to change notification settings - Fork 15
Add progress bar to the run command #441
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
Conversation
@@ -10,10 +10,10 @@ | |||
|
|||
final class RenderCommand | |||
{ | |||
/** @param DocumentNode[] $documents */ | |||
/** @param iterable<DocumentNode> $documents */ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
iterate
returns a generator, but looking at the rest of a project, the fact that getDocuments()
is an array is never used.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it should be fine then
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me
Maybe we should add commandline flag to hide the progress bar. Like --no-progress. As progress bars can break the console output when this is very verbose. ? |
You're right, I'll work on that 👍 |
This adds a progress bar based on how many documents are being processed. This is not always possible depending on the capabilities of the current OutputInterface interface implementation, which it is conditionally created. For instance, when running tests, you get a BufferedOutput, which does not have the section capability.
@jaapio done 🙂 |
Thanks you rock! |
This adds a progress bar based on how many documents are being processed.
This is not always possible depending on the capabilities of the current
OutputInterface
interface implementation, which it is conditionally created.For instance, when running tests, you get a
BufferedOutput
, which does not have the section capability.Closes #297