feat(reporters): support custom options #5111
Merged
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.
Description
<file path="...">
attributes AriPerkkio/vitest-sonar-reporter#154There are now multiple different ways how to define reporters in configuration. This is similar shape as
coverage.reporters
has.junit
reporter'sprocess.env.VITEST_JUNIT_CLASSNAME
andprocess.env.VITEST_JUNIT_SUITE_NAME
can now be passed via reporter options:["junit", { classname: "..." suiteName: "..." }]
. In 2.0.0 we should drop support for the environment variables.test.outputFile
can now be passed as reporter option, e.g.["json", { outputFile: "report.json" }]
. I think in 2.0.0 we should drop support fortest.outputFile
completely.Please don't delete this checklist! Before submitting the PR, please make sure you do the following:
pnpm-lock.yaml
unless you introduce a new test example.Tests
pnpm test:ci
.Documentation
pnpm run docs
command.Changesets
feat:
,fix:
,perf:
,docs:
, orchore:
.