Show console log messages and errors independently from specdocs in Guard #62
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
netzpirat
added a commit
that referenced
this pull request
May 21, 2012
Show console log messages and errors independently from specdocs in Guard
|
Great addition. Thanks a lot! |
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.
When using your fabulous guard-jasmine gem I was troubled by the fact that console.info messages where only shown when the whole specdoc was put out, making the run very verbose.
In this pull request I changed the runner code and its specs so that setting the :console or :errors option changes the output in Guard independently from the :specdoc option.
Feel free to change, merge or close.