fix(@angular/build): json and json-summary as vitest coverage reporters#30545
Merged
alan-agius4 merged 1 commit intoangular:mainfrom Jun 17, 2025
Merged
fix(@angular/build): json and json-summary as vitest coverage reporters#30545alan-agius4 merged 1 commit intoangular:mainfrom
alan-agius4 merged 1 commit intoangular:mainfrom
Conversation
They can be quite handy for analysis tools. See https://github.com/vitest-dev/vitest/blob/93f3200e452874ed4e2d018718bbbde7ebd28590/test/coverage-test/test/configuration-options.test-d.ts#L152 for all the current valid options
alan-agius4
approved these changes
Jun 17, 2025
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
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.
PR Checklist
Please check to confirm your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the new behavior?
They can be quite handy for analysis tools.
See https://github.com/vitest-dev/vitest/blob/93f3200e452874ed4e2d018718bbbde7ebd28590/test/coverage-test/test/configuration-options.test-d.ts#L152 for all the current valid options
Does this PR introduce a breaking change?
Other information