You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This file contains 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
This PR adds support for the --coverage and --ui flags in the @analogjs/vitest-angular builder CLI. Users can now dynamically enable these options without manually configuring them in angular.json.
Example usage:
ng test --coverage # Display test coverage
ng test --ui # Enable UI mode
This simplifies testing workflows by reducing unnecessary angular.json complexity.
Does this PR introduce a breaking change?
Yes
No
Other information
[optional] What gif best describes this PR or how it makes you feel?
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
Closes #1520
What is the new behavior?
This PR adds support for the
--coverage
and--ui
flags in the@analogjs/vitest-angular
builder CLI. Users can now dynamically enable these options without manually configuring them inangular.json
.Example usage:
This simplifies testing workflows by reducing unnecessary
angular.json
complexity.Does this PR introduce a breaking change?
Other information
[optional] What gif best describes this PR or how it makes you feel?