Initialize reporters early in the process #4480
Closed
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.
addresses #4471
DefaultReporter
that will print extra data in verbose mode. (i want to mergeSummaryReproter
back too at some point)globalConfig
anymore (globalConfig = Object.freeze(Object.assign({}, globalConfig, {verbose: true}));
) i hope that was the last place.test_scheduler.js
and now fully encapsulated inreporter_dispatcher.js
globalConfig
in jest clia few bad things:
NotifyReporter
. We have a sketchy implementation that passes an extra function to all reporters that reruns the build. This function has to be passed during runtime, which means it can't be a custom option for a single reporter.verbose
all over the place just because we don't know whether we run verbose until we get the number of test we're going to run. Which means we either mutate the immutable config (bad) or pass an extra option all over the place (still bad, but not as bad)in the next PR i want to add a few extra reporter events. specifically
configInitialized
,contextsReady
, andprojectRunsComplete