test(module-resolver): fix custom matchers #4952
Merged
+22
−33
Conversation
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
wjhsf
approved these changes
Nov 26, 2024
|
/nucleus test |
nolanlawson
approved these changes
Nov 26, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Details
Turns out these matchers were broken, but went unnoticed because tests were passing.
diffStringsUnifiedwas supposed to be a named import and was undefined here. We don't need it with vitest since we can returnexpectedandactualin the matcher result, so I just removed the '@vitest/utils' dependency altogether.Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item