Skip to content

Conversation

@jnizet
Copy link
Contributor

@jnizet jnizet commented Nov 22, 2025

This option allows not migrating the toHaveClass assertion, 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?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #31917

What is the new behavior?

A new browserMode option allows not migrating the toHaveClass assertion, which exists in Vitest in browser mode and thus is best left as is.

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

…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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add option to avoid migrating toHaveClass matcher

1 participant