feat(@schematics/angular): add browserMode option to jasmine-vitest schematic#31920
Merged
Merged
Conversation
…chematic This option allows not migrating the `toHaveClass` assertion, which exists in Vitest in browser mode and thus is best left as is. fix angular#31917
angular-robot
Bot
added
detected: feature
alan-agius4
added
the
action: review
clydin
approved these changes
Nov 24, 2025
clydin
added
action: merge
Member
|
This PR was merged into the repository. The changes were merged into the following branches:
|
|
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.
3 participants
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.
This option allows not migrating the
toHaveClassassertion, which exists in Vitest in browser mode and thus is best left as is.fix #31917
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 current behavior?
Issue Number: #31917
What is the new behavior?
A new
browserModeoption allows not migrating thetoHaveClassassertion, which exists in Vitest in browser mode and thus is best left as is.Does this PR introduce a breaking change?
Other information