chore(integration-karma): add @types/jasmine #4485
Merged
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
Aug 26, 2024
wjhsf
approved these changes
Aug 26, 2024
nolanlawson
approved these changes
Aug 26, 2024
|
/nucleus test |
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
I noticed there was no autocompletion or hover information for jasmine's expect, spyOn, etc, which makes it harder for someone unfamiliar with jasmine like myself.
This PR just adds the @type/jasmine dev dependency to @lwc/integration-karma. It doesn't seem to affect tests in other packages, but I recommend giving it a try before merging.
I understand karma is to be replaced at some point, but in the meanwhile it's nice to have this.
Does this pull request introduce a breaking change?
Does this pull request introduce an observable change?
GUS work item