test: use strictEqual in plugin-kit where possible
#278
Conversation
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
Member
Author
|
The Bun CI failure on Windows will be resolved once #277 is merged. |
1 task
aladdin-add
deleted the
test-use-strictequal-in-plugin-kit-where-possible
branch
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.
Prerequisites checklist
What is the purpose of this pull request?
This PR is follow-up to eslint/css#167 (comment), and eslint/json#109 (comment).
In this PR, I've used
strictEqualinplugin-kitwhere possible.What changes did you make? (Give an overview)
In this PR, I've used
strictEqualinplugin-kitwhere possible.Related Issues
Ref: eslint/css#167 (comment), and eslint/json#109 (comment)
Is there anything you'd like reviewers to focus on?
N/A