Setup custom reporters after default reporters#4053
Merged
cpojer merged 1 commit intojestjs:masterfrom Jul 18, 2017
Merged
Conversation
|
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
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
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.
Custom reporter experience is not great right now and it's pretty hard to customize.
Right now even if we pass this to config:
the order will be:
and that makes it hard to customize reporters that interact with coverage data. (coverage data is never available in custom reporters, because
CoverageReporteris always last in the queue).This requires a better fix (#4052), but for now i want to move custom reporters to the very end, so they're run after all default reporters are done