Prevent progress bar from starting if file already exists #30
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
tiagofilipe12
force-pushed
the
progress-bar
branch
2 times, most recently
from
3cfa511
to
3cd411b
Compare
tiagofilipe12
force-pushed
the
progress-bar
branch
from
3cd411b
to
0ed9dd4
Compare
bmpvieira
approved these changes
Apr 20, 2017
There was a problem hiding this comment.
Looks good thanks! Long term, we might want to change how we deal with errors and info. #29 (comment)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change only affects --pretty option, and prevents progress bar from starting when file already exists, which rendered an odd 0% progress when output already exists in file system. Makes more sense if we raise an error message and do not start progress bar at all.