fix(@angular/cli): disable progress when running Karma directly outside TTY #8925
Conversation
This file contains hidden or 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
…de TTY Fixes a shortcoming of angular#8501. Apply same logic for setting --progress flag when running Karma directly (as opposed to running it using `ng test` command). Fixes angular#8148
devoto13
force-pushed
the
karma-tty-progress
branch
from
8249573 to
d3b1f7f
Compare
filipesilva
approved these changes
Dec 18, 2017
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Fixes a shortcoming of #8501. Apply same logic for setting --progress
flag when running Karma directly (as opposed to running it using
ng testcommand).Fixes #8148
See #8148 (comment) for more context.
Tested manually using: