Skip to content
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

Setup custom reporters after default reporters #4053

Merged

Conversation

aaronabramov
Copy link
Contributor

Custom reporter experience is not great right now and it's pretty hard to customize.
Right now even if we pass this to config:

{reporters: ['custom1.js', 'default', 'custom2.js']}

the order will be:

  • default reporters
  • custom reporters
  • coverage/notify reporters

and that makes it hard to customize reporters that interact with coverage data. (coverage data is never available in custom reporters, because CoverageReporter is 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

@cpojer cpojer merged commit aa88faa into jestjs:master Jul 18, 2017
@aaronabramov aaronabramov deleted the custom_reporters_go_after_default_reporters branch July 18, 2017 17:37
tushardhole pushed a commit to tushardhole/jest that referenced this pull request Aug 21, 2017
@github-actions
Copy link

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.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 13, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants